Data residency used to be a checkbox. Now it’s a negotiation about who can unlock which rack under which law. Sovereign cloud regions — local operators, local keys, familiar APIs — are multiplying in response.
Buyers get something closer to public-cloud convenience with sharper jurisdictional boundaries. Providers get a market that won’t accept “trust us, it’s encrypted” alone.
Trade-offs remain: feature lag versus flagship regions, tighter support circles, higher prices. For health and public sector workloads, those trade-offs often beat uncertainty.
The cloud isn’t one place anymore. It’s a map — and borders are back on it.
Sovereign cloud regions multiply because “encrypted somewhere” stopped satisfying counsel.
- Map which workloads truly need local keys and courts.
- Accept feature lag as a regulated-industry cost.
- Test restore drills under the sovereign operator’s process.
- Price the certainty, not only the compute.
The cloud became a map again. Borders are back on it for a reason.
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.