Multi-cloud is one of the most over-sold ideas in enterprise IT. The marketing pitch is compelling: avoid vendor lock-in, negotiate better pricing, pick the best service from each provider. The operational reality is: you have now tripled your infrastructure complexity, fragmented your team's expertise, and made your security posture significantly harder to audit.
When Multi-Cloud Is Genuinely Justified
There are real scenarios where multi-cloud makes sense. Mergers and acquisitions often result in different business units running different clouds — standardising immediately is sometimes impossible. Regulatory requirements in certain jurisdictions mandate data residency on specific providers. Some best-in-class services are genuinely provider-specific: Google BigQuery for petabyte-scale analytics, Azure Active Directory for enterprise identity, AWS for the broadest ecosystem of healthcare-specific services. If you need all three simultaneously, multi-cloud is not a choice — it is a necessity.
The Hidden Costs
Organisations consistently underestimate multi-cloud costs. Engineers must maintain proficiency across multiple CLIs, SDKs, IAM models, and billing systems. Tooling like Terraform helps abstract infrastructure but does not eliminate the need to understand provider-specific behaviours. Data egress fees between clouds are non-trivial at scale. Observability becomes more complex when your metrics, logs, and traces are spread across CloudWatch, Azure Monitor, and Google Cloud Monitoring simultaneously.
The goal is not to avoid vendor lock-in at all costs. The goal is to build software that delivers value. Sometimes those two objectives are in direct conflict.
A Pragmatic Framework
Before committing to multi-cloud, answer three questions honestly: (1) Which specific business requirement cannot be met by a single cloud provider? (2) Do we have the team capacity to operate and secure two or more clouds simultaneously? (3) Have we modelled the total cost of ownership including tooling, training, and operational overhead? If the answer to any of these is uncertain, start with a primary cloud provider and a clear, documented process for when a second provider would be justified.
