Order from every major cloud, AWS, Azure, Google Cloud and Oracle Cloud, with your approvals and change process built in. See the cost before you order, then compare actual spend with what was ordered. Standard ServiceNow Discovery finds every resource, so your CMDB stays up to date.
Every major cloud at the same level, plus VMware vSphere for private cloud. Easy to extend: new clouds, resource types and day-2 automation plug in without changing the core.
Most companies now run more than one cloud, and each one comes with its own console, its own request route and its own idea of who's allowed to do what. Nobody has one view of what's running, who asked for it, what state it's in or what it costs.
OneCloudify gives you that view in ServiceNow. Every deployment, resource, request and cost across all your clouds and accounts sits in one place, filtered by cloud, account, region, environment, owner group or customer. Requesters see it in their own language, because OneCloudify uses the platform's translation tables. It's built on the ServiceNow platform, uses it as it is and ships its own catalog category, topics and records instead of touching yours. All your data stays in your own instance.
People order from the portal they already use, such as Employee Center. They pick a cloud account, a size and an owner group on a short form, with their own networks in pick lists and the monthly price in view. OneCloudify works out exactly what will be built, checks it, asks for approval and a change where your rules say so, builds it, records it in the CMDB and tells them it's ready.
Afterwards each deployment offers the actions that fit it, per server or for the whole deployment, now or at a time they pick. Operators get the same actions in the workspace, and integrations get them through the REST API.
Each action runs the way your team already works. Power actions call the cloud's own CLI, Azure DevOps Pipelines is built in, and Ansible, GitHub Actions, GitLab CI or your own automation plug in as a day-2 executor.
ServiceNow keeps the request, the approval, the change and the record, and all your data stays in your own instance. The build runs with whichever Terraform edition you use: Terraform Community Edition, HCP Terraform or Terraform Enterprise.
Rules run before anyone is asked to approve, so a compliant development server goes straight through and a risky change stops with a reason. How OneCloudify governs without slowing people down.
Before. OneCloudify keeps a price book of the clouds' published list prices, loaded in the background for the regions you use, so the order form never waits on a cloud API. The estimate shows one line per resource, including the charges that are easy to miss, such as public IP addresses, operating system disks and cluster fees. Before approval the exact resources are priced again, and approvers see that figure.
After. Once a deployment runs, OneCloudify reads its cost from the cloud's own cost data, matched by the tag it puts on every resource. Each deployment gets a cost card, each requester sees their spend in My cloud, and everyone sees amounts in their own currency.
Ordered versus actual. Cost and usage shows month to date and forecast, spend by cloud, the estimate next to what was spent, hours saved by schedules, saving opportunities, unusual spend and tag coverage. How cost works.
Works with or without domain separation. Single company customers never see any of it. OneCloudify for MSPs.
See it on your own clouds. A short demo with your accounts, your approval rules and your CMDB.
Request a demoAll your data stays in your own ServiceNow instance, and every resource is recorded in the CMDB the right way: through the Identification and Reconciliation Engine, in the right CI class, related to its region and under reconciliation rules that respect what other sources own. Where you run ITOM Discovery, a targeted discovery confirms it straight after the build. On removal every configuration item is retired, so nothing is left behind.
One trail per deployment or run: who ordered it with which inputs, which policies passed or were overridden, who approved, which change covered it and what was done in the cloud. Print it or export CSV or JSON. Secret values never appear in it.
Point OneCloudify at a folder in GitHub, GitLab, Azure DevOps or Bitbucket and it creates a catalog item per template, with questions, sections and pick lists. It looks after the state, and a template change becomes a pull request your team reviews. How it works.
OneCloudify supports every Terraform edition, so your infrastructure code stays the source of truth whichever one you run.
The setup assistant opens each form already filled in and ticks steps off when it sees them done. Where a step used to mean several records, it's now one click or one pasted token. Manual steps are kept to the ones the platform or your network needs.
ServiceNow is preparing Cloud Provisioning and Governance and Cloud Services Catalog for deprecation. OneCloudify keeps everything in ServiceNow: the same catalog, approvals and Change, the same CMDB, and your templates as they are. It has no runtime dependency on either product.
The importer starts with a dry run that only writes a report. You then bring across everything or one part at a time, all switched off until you turn it on. Replay runs past CPG decisions through the imported policies, running stacks are adopted with their state, and CPG keeps running until the last one has moved. Read how the move works, or see our CPG and CSC replacement service.
OneCloudify is a hybrid cloud provisioning and governance solution built on the ServiceNow platform. It gives you one place to order, track and manage cloud services across every major cloud, AWS, Azure, Google Cloud and Oracle Cloud, plus VMware vSphere for private cloud, with requesters working in the Employee Center they already use. Every order and every change after it runs under the approvals, change requests and policies you already use in ServiceNow, the cost is shown before and after, and every resource is recorded in the CMDB. It's easy to extend, so new clouds, resource types and automation plug in without changing the core.
AWS, Microsoft Azure, Google Cloud and Oracle Cloud at the same level, with the same features on each, plus VMware vSphere for private cloud. Containers are covered too: AKS, EKS, GKE, OKE, Amazon ECS and Azure Container Instances, with actions that fit them, such as scaling a node pool or upgrading Kubernetes.
Yes, and that's how it's built. Cloud providers, resource types, day-2 executors, step types, runners, credential sources, state backends, cost and price sources, policy checks and setup checks are all extension points. An extension is a script include in your own scope registered on a platform extension point, or a configuration row, so it survives upgrades and never means editing OneCloudify itself. The setup assistant lists what's registered.
Start, stop and restart servers, resize them, add or expand disks, open or close ports, set business hours schedules, extend a lease, update to a newer version of the template and remove the deployment. Each action follows the approval and change rules the process owner sets. Power actions call each cloud's own CLI. You can add your own actions as a Flow Designer subflow or an Azure DevOps pipeline, which is built in, and Ansible, GitHub Actions, GitLab CI or your own automation plug in as a day-2 executor. Actions get the server's IP address, CI name, Terraform outputs and other record values straight from the records, so requesters type only what's really a choice. Start and stop can also run through your own pipeline with one setting on the cloud account. After any of these actions OneCloudify reads the servers it touched from the cloud, updates their CIs and says on the request page what changed.
The order form shows a monthly estimate at list prices as the requester picks a size, from a price book OneCloudify keeps up to date in the background, so ordering never waits on a cloud API. The plan is priced again before approval. Once a deployment runs, OneCloudify reads its actual cost from the cloud's own cost data and shows it on the deployment, in My cloud and in the Cost and usage dashboards, in each person's own currency.
Yes. Policies written in Rego run in Open Policy Agent before anyone is asked to approve. A rule can stop the request, warn, or stop it until an administrator overrides it with a reason that is kept on the record. Price limits hold an order above a monthly amount for approval, and nobody can approve their own request.
Yes. Each customer gets its own cloud accounts, catalogue and view, with or without domain separation. Price plans, contracted prices and price limits put the customer's price on the order form and the approval, the month is rated against the real cloud bill and reconciled, and the result exports to your invoicing system. Emails, Teams and Slack messages are branded per customer. Single company customers never see any of this.
It works with or without it. All your data stays in your own ServiceNow instance, and every resource OneCloudify builds is recorded in the CMDB the way CMDB best practice expects: through the Identification and Reconciliation Engine, in the right CI class, under reconciliation rules that respect the attributes other sources own. Where you run Discovery, OneCloudify starts a targeted discovery after each build and after each day-2 action, so the resources are confirmed by the platform as well.
OneCloudify's own engine on your ServiceNow instance runs every order and every change, step by step. For the build it works with the Terraform you already run: Terraform Community Edition (the open source CLI), HCP Terraform (formerly Terraform Cloud), Terraform Enterprise or OpenTofu. Runs happen on a MID Server (Linux or Windows), on a Linux host over SSH, or in your own HCP Terraform or Terraform Enterprise. Day-2 actions call each cloud's own CLI, run an Azure DevOps pipeline, which reports back through a result file OneCloudify polls, or hand over to the automation you plug in. Templates come from GitHub, GitLab, Azure DevOps or Bitbucket, and OneCloudify creates the catalog items and looks after the state for you.
Yes. The portal pages, the order form with its cost estimate, the messages that say why something can't be ordered yet or what went wrong, the request tracker, emails and chat messages follow the language each person picked in ServiceNow. OneCloudify uses the platform's own translation tables, so you add a language the way you translate the rest of your instance, and anything not yet translated shows in English. A managed service provider can give each customer its own wording.
In the platform's own credential store, or in HashiCorp Vault. They are read on the MID Server at run time for that run only, and never written to logs, command lines or instance tables.
The setup assistant asks six questions, then shows only the steps your answers need, opens each platform form already filled in and ticks steps off when it sees them done. The host preparation script and the cloud bootstrap scripts download from the assistant with their SHA-256 checksums. To connect your Git hosting or Azure DevOps Pipelines you paste a token, and OneCloudify stores it encrypted, creates the connection and tests it. For a first order with no repository or cloud yet, one click adds the OneCloudify samples and another creates a lab account. Most of the time goes on collecting credentials.
Not standard ones. OneCloudify uses the platform's Standard change model by default, so a standard change is raised, run and closed on its own, with the run on record. Only a normal change waits for its approvals and Implement, the way your change process already works.
We actively support the current ServiceNow family release and the two before it. The Store listing and the release notes name the families for each OneCloudify release.
No. OneCloudify is built on core ServiceNow platform capabilities: Employee Center and the Service Catalog, Flow Designer, the MID Server, the CMDB and IRE, and Change. It doesn't call CPG, Cloud Services Catalog or the Cloud API at run time. For customers who run CPG today, OneCloudify includes an importer that brings accounts, policies, scripts, templates and running stacks across.
A short demo on your own instance setup: your clouds, your approval rules and your CMDB. Or write to us at info@intelibliss.com.
