For ten years, “cloud-first by default” was the safe answer. In 2026 the AI bill made a lot of leaders ask a question I’d almost never heard out loud: what would it actually cost us to leave?
The uncomfortable part isn’t the answer. It’s that most companies had never drawn the number on a page — because the cloud was priced so they’d never have a reason to test the door.
The story#
Three pressures landed in the same eighteen months and turned “cloud cost” from a back-office line item into a board-level topic.
The AI bill came due. Generative AI made the meter spin at a speed nobody budgeted for — a single complex task can burn ten to fifty times the compute of an ordinary request, and “agentic” workflows far more. One 2026 survey found 40% of enterprises overspent their planned cloud AI budget; another estimated the expensive AI chips (GPUs) run at roughly 5% utilization on average — the equivalent of leasing a parking garage to store one car. None of these are audited financials, but the direction isn’t in dispute: the bill got big enough that finance noticed.
The repatriation wave got real — but it’s smaller than the headlines. Repatriation just means moving a workload from a public cloud back to your own servers. A Barclays CIO survey put a record ~83% of tech leaders planning to move some workloads back; IDC found ~80% expecting to repatriate some compute or storage within a year. The number the headlines skip: only about 8% are moving entire workloads off the cloud. This is not an exodus — it’s selective re-balancing, companies finally putting each workload on trial.
The exit tax is two charges, and only one is on your invoice. Providers charge you very little to put data in, and a meaningful amount to take it out. That outbound charge is called egress (the fee to move your data off the platform — roughly eight to twelve cents per gigabyte after a small free allowance). But egress is the small part. The bigger toll is architectural lock-in: when you build on a provider’s proprietary managed services, leaving means rewiring every room before anything works in the new place. That engineering time is the real cost of leaving, and no invoice line shows it to you in advance.
The deadline quietly resetting the leverage. The EU’s Data Act (in force since January 11, 2024) requires cloud providers operating in the EU to remove the charges tied to switching — including exit egress — by January 12, 2027. Ahead of the law, Google waived exit egress in January 2024, AWS followed on March 5, and Azure on March 13. When vendors voluntarily drop a fee they defended for a decade, that’s the clearest admission that the fee was a barrier to leaving.
Hot take#
Stop treating “cloud-first” as a default and start re-pricing each workload the way you’d re-shop insurance instead of letting it auto-renew. Two things make that easier than it was a year ago.
First, the leverage is already yours. Those free-exit programs are narrower than the headlines suggested — they generally apply when you’re fully leaving or switching, not running two clouds side by side — and if you’re US-only the law doesn’t cover you. But you inherit the programs the law forced into existence. The free-exit offer exists globally now because of a European deadline. You just have to know to ask.
Second, the inventory you owe your auditor is the same one that gives you leverage. Pricing your exit is a vendor-and-asset-management exercise — the same discipline the NIST Cybersecurity Framework calls out under supply-chain risk. Concentration on one provider’s proprietary services is a risk whether or not you ever exercise the exit. And before you move a workload to cut its bill, ask whether the spend is producing value or just looking like productivity — the late-May “tokenmaxxing” backlash (Meta and Amazon reportedly pulled internal leaderboards ranking employees by tokens burned) is a reminder you often save more by governing the spend than by relocating it.
Three moves for Monday — none of them a migration:
- Pull your egress number — just that one line. Find the data-transfer-out charge on last month’s bill and learn whether your exit tax is a rounding error or a real barrier. Twenty minutes, free, and most leaders have never looked at it in isolation.
- Call your provider and ask about free egress on exit. Every major cloud now has the program. Even with no plans to move, knowing the exit is cheaper than you thought changes every future negotiation.
- Make a one-page list of your “landlord” dependencies. The proprietary services you’d have to rebuild if you left — built in an hour with your most senior engineer and your finance lead in the room.
Curated links#
Companion long-form — The Cloud You Can’t Afford to Leave — and the January Deadline That Changes the Math — walks the full exit-tax math and the size-by-size playbook: /blog/cloud-you-cant-afford-to-leave
Building the vendor-and-asset inventory this issue keeps pointing at? That’s exactly what the NIST CSF 2.0 Readiness Toolkit is structured around — the inventory you build for compliance is the one that gives you exit leverage. You don’t build it twice.
— Charles Redding, Founder, DLegendDigital