Cloud Sovereignty Is an Architecture Problem: Patterns for Modern Platform Teams

Most teams discover cloud sovereignty requirements after the architecture is already built. By then, the cost of fixing it — rearchitecting data flows, re-platforming workloads, renegotiating vendor dependencies — is enormous. Sovereignty isn’t just about compliance. It’s about control: over your data, your workloads, your identities, and your ability to move when you need to. And in a world of AI services, managed platforms, and cross-border data flows, that control doesn’t happen by accident — it has to be designed in from the start. This session presents practical architecture patterns for teams building sovereign cloud platforms. You’ll learn how to design for workload portability without sacrificing developer experience, enforce data localisation boundaries using policy-as-code, build identity federation that works across jurisdictions, and create golden paths that encode regulatory requirements as defaults — not afterthoughts. Whether you’re navigating India’s DPDP Act, EU data residency, or enterprise sovereignty mandates, the architecture decisions are the same. This talk shows you how to make them.