Cloud bills that once felt like growth metrics now feel like leaky taps. Steady, predictable workloads — the ones that never needed infinite scale — are coming home to owned hardware or smaller hosts.
This isn’t a mass divorce from hyperscalers. It’s a rebalancing. Bursting and global reach stay in the cloud; batch monsters and sleepy databases get cheaper seats.
Engineers warn against nostalgia. On-prem means patching, hiring, and capital planning again. The wins appear when teams measure unit economics honestly instead of chasing architecture fashion.
Call it cloud maturity. The slogan era ended; the spreadsheet era returned.
Cloud repatriation is a rebalancing act, not a breakup speech.
- Keep bursty global apps where elasticity pays.
- Bring home steady batch jobs with boring utilisation.
- Recount unit economics after every architecture fashion cycle.
- Budget for the people who patch what you bring back.
The slogan era ended. The spreadsheet era is doing useful work again.
None of this arrives as a clean discontinuity. It shows up as slightly different meetings, slightly different checklists, and a few people who quietly stop doing the old workaround because the new path finally hurts less.
Seen up close, the pattern is less about breakthrough theatre and more about quieter competence: fewer surprises, clearer owners, and tools that survive contact with Tuesday afternoon.