Multi-cloud is one of those topics where the strong opinions arrive faster than the data. Half the industry thinks it's the only sensible strategy; the other half thinks it's enterprise vanity. The honest answer is more boring.
When it earns its keep
Multi-cloud is justified, in our experience, in three cases:
- Regulatory residency you can't satisfy in one provider's regions.
- A specific managed service in another cloud that meaningfully changes the product (BigQuery, Cloud Run, certain ML offerings).
- Customer-driven — you sell to enterprises with hard preferences and they pay enough to justify the complexity.
Notice what's not on that list: disaster recovery, negotiation leverage, vendor lock-in fear. Those are arguments people use to justify multi-cloud after they've already decided to do it. None of them survive contact with the actual operational cost.
What it actually costs
Running production workloads across two clouds is, conservatively, 1.8× the operational overhead of one. You doubled the IAM model, the network model, the observability layer, the deploy paths, and the on-call surface. Your team's depth of knowledge in each cloud is now half.
Multi-cloud is justified when you have a reason. 'In case' is not a reason.
The three honest questions
Before signing off on a multi-cloud strategy, we run three questions past the team:
- What specifically does the second cloud do that the first can't? Be concrete.
- Are you actually willing to pay the staffing premium to operate it well? Half-cloud is worse than single-cloud.
- Could the same outcome be achieved with multi-region inside one provider, plus a contractual data-portability clause?
If question three gets a 'yes', we usually recommend that path. It's the single biggest under-considered option in this conversation. Most fears that drive multi-cloud are addressable with multi-region plus contractual guarantees, at a fraction of the operational cost.
When we do it anyway
Roughly a third of our engagements end up multi-cloud. In every one of those, the second cloud answers question one with something specific and unambiguous. The team understands the cost. The estate is built with one cloud as the centre of gravity and the second as the deliberate, justified exception.