Cloud computing should make businesses more focused on their business, not more focused on their cloud.
That distinction has gotten lost.
A company that has moved its operations to the public cloud and then deployed significant engineering capacity to manage that environment has not simplified anything.
It has traded one operational cost for another.
CEO of Nexcess.
Around 2012, moving to public cloud was genuinely good advice. It meant elastic scale on demand, no capital expenditure, and you only paid for what you used.
For most workloads, it was a meaningful step forward and the migration wave that followed made complete sense.
Things have changed.
The 2026 Flexera State of the Cloud report puts the current picture plainly: 73% of organizations say cloud has increased their operational complexity. And 31% of cloud spend, according to Finout, is being wasted.
There is a gulf between the promise of the public cloud and the reality, and that gulf is worth understanding.
Hyperscalers don't own outcomes
A useful analogy here is Home Depot. Asking a hyperscaler to run your business environment is a bit like asking Home Depot to build an extension on your house. They will sell you every part you could possibly need, deliver it to your door, and give you more selection than you can use.
But this analogy has a limit. Home Depot has moved well beyond lumber, and hyperscalers have done the same. You can buy managed services across the entire stack from them today, and their marketplaces run to tens of thousands of products. There is a lot you could put together from a hyperscaler.
But their commercial interests are not aligned with keeping things simple. When profit is tied to consumption, complexity is not a problem the model is built to solve. Every service you add is revenue for them. Every integration you maintain keeps you in the ecosystem. The model rewards sprawl, not efficiency.
The egress fees that make data migration elsewhere economically painful are the clearest expression of this. They ensure that even businesses that recognize the complexity problem find it expensive to do much about it. Simplicity, for the major cloud vendors, is a commercial risk.
When 78% of organizations say they are moving toward multi-cloud specifically to reduce single-vendor dependency, that is a market telling you the model stopped working for them.
The overspend problem
The overspend is just a part of the problem. Another cost is what happens to the people running these environments. When engineering teams spend their time integrating primitives and keeping a complex stack functional, they are not building products or moving the business forward. The cloud was supposed to create capacity, but for a lot of businesses it has consumed it instead.
Adding compliance needs on top compounds this. Around 43% of mid-market companies fail their first audit. The reason is rarely that the regulations are unclear. Maintaining audit-ready posture inside a general-purpose cloud environment is a continuous manual effort, and public cloud platforms give you the tools but leave the work to you. That burden lands on internal teams who are already stretched managing everything else the environment demands.
Cloud that helps businesses focus on outcome rather than maintenance requires an environment where the operational weight sits with the provider. Compliance should be managed as an architectural property rather than a continuous configuration task.
Performance should be maintained at the infrastructure level rather than something you tune around. Bills should be predictable because the model is built that way. These should not be premium features reserved for enterprises with unlimited budgets.
AI is making this more urgent. Around 98% of AI pilots currently fail to reach production. The reason is fairly straightforward: pilots run in isolated environments, and when it is time to move into production, the storage, networking, compliance posture, and compute requirements that real workloads demand are not in place.
If a business can operate on a managed, purpose-built cloud platform, it is significantly better positioned to take AI from pilot to production, because the underlying architecture is already there. They do not need to solve for an infrastructure problem before capturing the business benefit.
Simplicity is not a concession
The businesses pulling ahead have reframed how they think about cloud complexity. Complexity is not a sign of sophistication; it is an operational cost. Every hour an internal team spends managing it is an hour not spent on the actual work.
If your engineering team is spending a meaningful portion of its time keeping the cloud environment functional, the cloud is not working for you. That is not a problem inherent to cloud. It is a question of whether your provider's model is designed around your success or their consumption.
The 97% of mid-market organizations saying they need to move workloads away from hyperscale are already answering that question for themselves.
We've reviewed and rated the best business cloud storage.
This article was produced as part of TechRadar Pro Perspectives, our channel to feature the best and brightest minds in the technology industry today.
The views expressed here are those of the author and are not necessarily those of TechRadarPro or Future plc. If you are interested in contributing find out more here: https://www.techradar.com/pro/perspectives-how-to-submit