Architecting Beyond Hyperscalers: Sovereign Clouds and IaC Portability

A panel of cloud architecture and economics practitioners convened by Pulumi highlighted critical strategies for organizations evaluating infrastructure independence from US hyperscalers, driven by compliance mandates such as NIS2 and escalating cloud expenditures. The discussion brought together Think Ahead Technologies co-founder Waldemar Kindler, Hopsworks CEO Jim Dowling, and cloud economist Sarbjeet Johal to address practical data sovereignty, multi-cloud economics, and migration realities. For DevOps leaders, the key insight centers on avoiding provider-proprietary managed APIs. As detailed in the operational review, building platforms on Kubernetes and decoupling infrastructure from vendor-specific constructs enables swift workload repatriation or re-hosting across regional providers like OVHcloud and Hetzner. For example, Hopsworks demonstrated that adhering to container-native abstractions allowed them to migrate both development infrastructure and core SaaS platforms off AWS, achieving a verified 62% reduction in infrastructure operating costs without undergoing multi-year codebase rewrites. This shift fits into a broader macro trend across DevOps and platform engineering: the transition away from monolithic vendor lock-in toward agentic, code-driven portability. Historically, multi-cloud migrations were deemed impractical due to the massive operational overhead of rewriting templates and managing disparate configuration schemes. However, modern Infrastructure as Code platforms and agentic orchestration engines significantly lower this threshold by providing unified state management, declarative context models, and cross-provider configuration abstractions. In practice, engineering teams should not execute reactive, wholesale cloud migrations without clear regulatory or financial catalysts. Practitioners should instead audit current architectures to isolate proprietary service dependencies from core application logic. By establishing standardized Infrastructure as Code pipelines and running containerized workloads on portable orchestration layers, teams preserve the operational leverage needed to pivot across geographic regions and alternative cloud providers whenever compliance dictates or economic margins require it.