Cloud Lock-In Is Loosening. Your Bill Is Still Growing. A Playbook for Small Teams.
Two things are true about the cloud in mid 2026, and they pull in opposite directions.
Leaving a cloud provider has never been easier. AWS, Azure, and Google Cloud have all dropped egress fees for customers who exit, pushed by the EU Data Act. Now the European Commission is reportedly preparing to classify AWS and Azure as gatekeepers under the Digital Markets Act, which would harden those switching rights into binding obligations.
At the same time, bills keep climbing. An Azul survey found 88 percent of CFOs say their cloud spend is rising, and industry studies keep estimating that around a third of cloud spend is simply wasted on idle and oversized resources. With global cloud spending headed past a trillion dollars this year, that is a lot of money buying nothing.
For a small or mid-sized business, this combination is actually good news. The exit door is opening just as the incentive to use it grows. Here is how to think about it without overreacting.
Lock-in was always a pricing strategy
Egress fees never reflected real network costs. They existed to make leaving expensive, which let providers price everything else with confidence. Regulators noticed. The practical effect for you is negotiating leverage. Even if you never move, the credible option to move changes the conversation with your provider and with the reseller who manages your account.
So before your next renewal, get a written estimate of what a migration would cost and take. You do not need to act on it. You need it to exist.
The repatriation stories are real, and mostly not about you
You have probably seen the headlines. 37signals moved off AWS and projects more than 7 million dollars in savings over five years. Surveys claim most enterprises plan to repatriate at least some workloads, and case studies report infrastructure savings of 30 to 60 percent.
Those numbers are real, but they belong to companies with steady, predictable workloads and an ops team to run hardware. If you are a 20-person company, the salary of one infrastructure engineer erases most of what you would save. For most SMEs, the answer is not leaving the cloud. It is stopping the waste inside it.
Where the waste actually hides in small companies
You do not need a FinOps platform to find most of it. Three places cover the bulk.
Oversized instances. Most SME workloads run comfortably on half the compute they were provisioned with. Check actual utilization for a week, then resize.
Environments that never sleep. Dev and staging systems running nights and weekends can be a quarter of a bill. Schedule them off.
Orphaned resources. Unattached storage volumes, old snapshots, idle load balancers, forgotten static IPs. These accumulate silently. A monthly 30-minute sweep pays for itself many times over.
One more that is newer: AI API costs. If you have added LLM features, watch cost per call. Inference spend is now the fastest-growing line on many bills, and caching or switching to a smaller model often cuts it dramatically without users noticing.
The takeaway
Treat July’s regulatory news as a prompt, not a panic. Ask your provider what leaving would cost, use the answer as leverage, and spend one afternoon this month on the three waste checks above. Most SMEs we look at can cut 20 to 30 percent of their bill without moving anything.
If you want a second pair of eyes on your cloud bill before your next renewal, that review is one of the most requested things we do at Beaverminds.