Update, October 2026: IMGO was built on ServiceNow Cloud Provisioning and Governance, which ServiceNow has since marked for deprecation. Its successor is OneCloud, a new application with no dependency on CPG or Cloud Services Catalog. The approach to moving is in our CPG deprecation article.
Most organisations we work with run more than one cloud. Sometimes that’s a deliberate choice, to use the strongest service from each provider and avoid lock-in. Often it’s the result of acquisitions, team preferences or a project that started on one platform and never moved. Either way, the hard part isn’t the clouds themselves. It’s governing and orchestrating them as a single estate.
IMGO, the Intelibliss Multi-cloud Governance and Orchestrator, was built to do that on the ServiceNow platform. Its successor is OneCloud, a new application without the CPG dependency, but the problems it addresses haven’t changed.
What governance has to cover
Governance is the set of controls that keep a multi-cloud estate safe, compliant and affordable. In practice that means:
- Cost control: knowing what each account, project and team is spending, and stopping surprises.
- Security and compliance: consistent policies across providers, and evidence that they’re being applied.
- Resource management: a clear inventory of what exists, who owns it and whether it’s still needed.
- Policy enforcement: tagging standards, approved regions and sizes, and guardrails on who can provision what.
- Visibility and monitoring across every provider from one place.
- Identity and access management that doesn’t require a separate admin model per cloud.
- Automation of the routine work, so policy is applied by the platform rather than by a checklist.
- A service catalogue, so users request what they need in standard shapes.
- Audit trails and reporting for both internal governance and external auditors.
- Disaster recovery and business continuity planning that spans providers.
What orchestration has to cover
Orchestration is about making the estate do useful work without someone logging into three consoles:
- Workload mobility between providers and between on-premise and cloud.
- Hybrid deployment patterns that treat private and public resources consistently.
- Service integration, so provisioning a VM also registers it in the CMDB, monitoring and backup.
- Workflow automation with approvals, change records and quota checks built in.
- Scalability and load balancing driven by policy rather than manual intervention.
- Data management across providers.
- DevOps integration, so pipelines can request infrastructure through the same governed path.
- Cost optimisation, with rightsizing and cleanup recommendations acted on, not just reported.
How IMGO approaches it
IMGO is built entirely on the ServiceNow ITOM product line: Cloud Provisioning and Governance, Cloud Cost Optimisation, Cloud Service Catalog and Tag Governance. Users get one interface for discovering, requesting, approving and managing resources across AWS, Azure, Google Cloud, Oracle Cloud and IBM Cloud, with KPI dashboards for the people who have to answer for cost and compliance.
Two results stand out from our deployments. Customers have reported around 30% time savings in governance work once the KPI dashboards replaced manual reporting. And our Quick Start approach has brought multi-cloud enterprises onto the platform in 4 to 6 weeks rather than the quarters a ground-up build typically takes.
A customer example
Customer: a European ERP company.
The challenge. IT infrastructure was spread across several clouds. Provisioning workflows were growing more complex with every new platform, and there was no single place to manage the estate end to end.
What we delivered with IMGO:
- A dedicated portal for provisioning cloud resources, with the controls to manage those resources after they exist.
- Discovery of any cloud resource added to the estate, whichever provider it sits on.
- A single interface for approvals, regardless of the type of task being approved.
The results:
- One interface to manage cloud resources, without needing to work in each provider’s console.
- Discovery and management of every cloud resource from one place.
- Hybrid infrastructure managed through workflows the IT team already knew from ServiceNow.
- Better control over the estate through consistent approvals and the change process.
Technologies used: ServiceNow ITOM, Cloud Provisioning and Governance (CPG), Cloud Cost Optimisation (CCO), Cloud Service Catalog (CSC) and Tag Governance.
If your cloud estate has grown faster than your ability to govern it, this is the kind of consolidation we’d suggest starting with: one catalogue, one approval path, one inventory, all on a platform your operations team already runs.
