Single cloud vs multi-cloud
Multi-cloud is two or more production control planes. It is not a backup screenshot of another provider’s console. The extra cost is identity, networking, skills and incident ownership, not only compute list price.
Last verified: · Written and technically verified by Ankit Mehta
How the products actually differ
A single-cloud design uses one account or subscription hierarchy, one IAM system and one hub network. A multi-cloud design must federate identity, decide where data lives, and write who pages when a dependency spans providers. Official docs describe each provider’s federation products; they do not claim that running two clouds is automatically more reliable.
| Topic | Single cloud | Multi-cloud |
|---|---|---|
| Identity | One IdP to one cloud IAM | Workforce/workload federation into each cloud |
| Network | One hub-and-spoke or TGW | Interconnect plus duplicate private DNS |
| Failure domain | Provider + region + AZ | Two providers only if data and failover are tested |
| Cost allocation | One CUR or Cost Management export | Two invoices, two tag models |
Decision table
Factual differences are in the table above. The rows below are recommendations for a named situation.
| When | Choose |
|---|---|
| One production control plane already serves the workload and no residency rule forces a second | Single cloud. Invest in regional HA and a tested backup, not a second IAM system. |
| An acquisition, a China/residency rule, or a SKU that only exists on another provider is already in production | Multi-cloud for that seam only. Federate identity and write who owns incidents that span both. |
When neither option is appropriate
“We have an account on both” is not multi-cloud, and a second provider is not a substitute for an untested single-cloud failover. If you cannot name the data plane and the incident owner, choose neither framing and write the actual constraint first.
Limitations
- Engineering recommendation: stay on one provider unless residency, an acquisition, or a specific SKU forces the second. That is judgment.
- Active-active data planes across clouds are a separate project from “we have an account on both.”