Kubermatic branding element

Digital Sovereignty Guide, Part 1: What It Is and How to Achieve It

Dictionary entry for the word sovereignty

If enterprise IT had a word of the year for 2026, it would be sovereignty.

In April, the European Commission awarded up to €180 million in sovereign cloud contracts and published a framework that scores providers on how sovereign they really are. In June, a US export-control directive forced Anthropic to suspend its most advanced AI models for every customer worldwide; access returned 19 days later for Fable 5, Mythos 5 was limited to a set of US organizations only. And Gartner expects more than 75% of enterprises outside the US to have a digital sovereignty strategy by 2030.

The lesson applies to every company, on every continent: if a decision you don’t control can switch off something you depend on, you have a dependency, not a supplier. At Kubermatic, we help organizations take that control back with infrastructure platforms built on open-source technology. These are the questions we hear most, answered plainly.

What is digital sovereignty?

Digital sovereignty is the ability to control your data, infrastructure and software, and to decide which laws they are subject to. In a sovereign setup, no foreign government or provider can access your systems, change the rules or switch them off without your consent.

In practice, it has three layers: data (where your data lives and which law governs it), operations (who runs the infrastructure, control plane and encryption keys) and technology (whether you can move or replace what you depend on).

Most organizations are strong on the first layer and weak on the other two.

What is the difference between data residency and real data sovereignty?

Data residency is about where your data is stored. Data sovereignty is about who has legal authority and operational control over it. The two are related, but they are not the same.

  • Data residency: Where is your data stored?
  • Data sovereignty: Who controls the infrastructure, who can access the data, who manages user identities and permissions, who holds the encryption keys, and which country’s laws apply?

Consider this example: A German company uses Microsoft Azure or AWS and chooses a data center in Germany. Its data is physically stored in Germany, meeting its data residency requirements.

However, the cloud infrastructure is operated by a global provider. Depending on the setup, parts of the management infrastructure, access systems or key management may still be controlled from outside Germany. The provider may also be subject to foreign laws.

This means that while the data is stored in Germany, the company may not have full control over the infrastructure and systems used to manage it.

And this is precisely the difference between data residency and data sovereignty: data residency ensures that data stays in a specific location; data sovereignty ensures that the data, infrastructure and systems used to manage it remain under the appropriate legal and operational control.

Many solutions marketed as “sovereign” keep data local but rely on control planes, identity systems or key management operated elsewhere. The data is local, but the control isn’t. This became visible in October 2025, when an AWS outage in Virginia also took down services running in Europe, because their identity systems depended on that US region.

That is why Kubermatic’s approach starts with the management layer, not just the storage location. Read more in Control Your Data Sovereignty.

How do I achieve real digital sovereignty?

Real digital sovereignty comes from how your technology is designed and operated. You need control over five things: where your data is stored, who operates the infrastructure, who can access it, who holds the encryption keys, and whether you can move to another provider.

A practical checklist:

  • Keep data local: Store data, backups and metadata in your chosen jurisdiction.
  • Control the management layer: Run control planes, identity and key management in that same jurisdiction.
  • Own your encryption keys: Decide who can access and use them.
  • Avoid lock-in: Build on open-source technologies and open standards, so you can switch providers or run your own infrastructure.
  • Plan for independence: Make sure critical systems keep running if a provider becomes unavailable.

Complete independence is rarely realistic overnight, because software supply chains are global. The pragmatic goal is resilience: remove single points of dependency step by step, starting with your most critical systems. We explain this approach in The New Era of Resilience in the Cloud, and why so many European companies are rethinking their cloud providers in Is Europe Breaking Up with US Cloud Giants?

To measure your progress, use the European Commission’s Cloud Sovereignty Framework. It scores sovereignty across eight objectives, from legal jurisdiction to supply chain, so you can see which layer is your weakest.

Kubermatic’s platform approach follows these principles: you control the management layer with KKP, keep your keys in KubeSG, and build on open-source technologies such as Kubernetes and KubeVirt. For the architecture behind it, see Control Your Data Sovereignty and the CNCF’s From Data Residency to Digital Sovereignty.

What happens to my business if a cloud provider cuts off access?

If a cloud provider suddenly stops providing a service your business depends on, the consequences can be immediate: critical applications may become unavailable, employees may lose access to essential tools, customer services may be disrupted, and business operations may come to a halt.

The impact depends on how deeply your business relies on that provider and whether you have an alternative ready. And this is not just a theoretical risk.

In June 2026, US export-control restrictions forced Anthropic to temporarily suspend access to its Claude Fable 5 and Claude Mythos 5 models for all customers worldwide. Even though the restriction affected specific AI models rather than Anthropic’s entire service, it demonstrated how quickly government decisions can affect access to technology used by businesses.

The risk isn’t always political, either. Following Broadcom’s acquisition of VMware, changes to licensing, product bundles and pricing left many customers facing significantly higher costs and difficult migration decisions. See VMware: The Death of an Industry Standard.

So, how do you protect your business? By making sure you have an exit strategy before you need one.

This means:

  • Avoid relying on a single provider for critical infrastructure.
  • Choose open technologies that allow you to move workloads between environments.
  • Keep control of your data, infrastructure and encryption keys.
  • Have alternative infrastructure available for critical workloads.
  • Regularly test your ability to migrate and continue operating independently.

For organizations running virtual machines, Kubermatic Virtualization (KubeV) provides an alternative to proprietary virtualization platforms by running virtual machines alongside containers on Kubernetes.

Ultimately, ask yourself: If your provider stopped serving you tomorrow, could your business continue operating?

If the answer is no, you have a dependency that represents a real business continuity risk. And it is one worth addressing before it becomes a crisis.

How do I reduce my dependency on a single cloud provider?

You don’t have to leave your current cloud provider to reduce your dependency on it. Build a second platform you control, so critical workloads have somewhere else to run if your primary provider becomes unavailable, changes its pricing or terms, or no longer meets your requirements.

This is the Second Platform Strategy: keep using hyperscalers such as AWS, Azure and Google Cloud where they make sense, and maintain an independent platform as your exit route. Four steps put it into practice:

  1. Standardize on Kubernetes. It runs the same way on public clouds, private clouds, on-premises and at the edge, so workloads can move between them with limited changes.
  2. Choose open-source technologies and open standards. Avoid tying critical applications to proprietary services that are hard to replace.
  3. Manage everything from a platform you control. Operate clusters across providers from one management layer, and decide where it runs and who can access it.
  4. Start with your most critical workloads. Begin where regulatory or business risk is highest, and test that you can actually run them on the second platform.

Kubermatic Kubernetes Platform (KKP) is built for this. It manages Kubernetes clusters across AWS, Azure, Google Cloud, regional clouds and your own data centers from a single management platform you can host yourself. If your dependency is on VMware rather than a cloud provider, Kubermatic Virtualization (KubeV) runs your existing virtual machines alongside containers on Kubernetes, giving you a path beyond VMware without rebuilding every application.

Which Kubernetes platform should I choose if data sovereignty is a priority?

Choose a Kubernetes platform you can operate yourself, on infrastructure you control, from a vendor whose legal jurisdiction and ownership you understand and accept.

The platform matters more than many organizations realize. Whoever controls the Kubernetes management layer can influence how clusters and workloads are created, configured and operated, regardless of where the data itself is stored. That makes control over the platform an important part of digital sovereignty.

Here are five things to consider, and how Kubermatic Kubernetes Platform (KKP) addresses them:

  • Where the control plane runs. Many managed Kubernetes services operate the control plane on your behalf, limiting your control over the management layer. Look for a platform you can host and operate yourself. KKP separates the management layer from the clusters running your workloads, allowing you to run it in your own data center or sovereign private cloud.
  • Whether it works offline. Defense, public-sector organizations and critical infrastructure operators may need fully disconnected, or air-gapped, environments. KKP can operate in fully air-gapped environments.
  • How portable workloads are. Kubernetes provides a consistent foundation for deploying and managing containerized applications across different environments. However, portability also depends on application architecture and dependencies on services such as storage, networking and databases. KKP is Certified Kubernetes and built on open-source CNCF technologies.
  • Where it can run. Digital sovereignty often requires a mix of your own hardware, regional cloud providers and hyperscalers. KKP manages clusters across bare metal, vSphere, Nutanix, OpenStack, AWS, Azure, Google Cloud, Open Telekom Cloud, Hetzner and edge environments from one platform.
  • Who the vendor is and who can access your systems. Check where the vendor is headquartered, who owns the company, which legal entities provide support, who can access your environment and who controls your encryption keys. Kubermatic is headquartered in Germany. Kubermatic SecureGuard helps keep secrets and keys in a system you host and control.

Kubermatic is the only Germany-headquartered vendor included in the 2026 Gartner® Magic Quadrant™ for Container Management.

To see how these principles come together in practice, explore Control Your Data Sovereignty.

How can I achieve data sovereignty with Kubernetes?

To achieve data sovereignty with Kubernetes, run Kubernetes on infrastructure under your jurisdiction, operate the control plane yourself, and keep secrets and keys in a self-hosted system. Kubernetes helps because the same open standard runs everywhere, so you are not tied to one provider.

A sovereign Kubernetes stack usually has four parts:

  • Cluster management you operate, such as KKP
  • Secrets and key management you host, such as KubeSG
  • Virtualization for existing VMs, such as KubeV
  • AI infrastructure on your own GPUs, such as Kubermatic AI

If your team needs help along the way, Kubermatic also offers professional services, training and managed services.

How do I build a sovereign cloud?

To build a sovereign cloud, start with infrastructure you control, add an open-source platform layer, and keep operations, identity and keys under your own jurisdiction. A typical path looks like this:

  1. Define your requirements: which data, which regulations and frameworks (such as GDPR, NIS2 or DORA in Europe, or FedRAMP and HIPAA in the US) and which level of independence.
  2. Choose the infrastructure: your own data centers, a local colocation partner, or a sovereign cloud provider.
  3. Build the platform layer: Kubernetes for containers, Kubermatic Virtualization for virtual machines on the same infrastructure, and KubeSG for secrets and keys, all built on open-source technologies such as Kubernetes, KubeVirt and OpenBao.
  4. Automate operations: KKP handles cluster lifecycle, upgrades and multi-tenancy, so a small team can run the platform reliably.

Swisscom built its sovereign Kubernetes Service this way, replacing its VMware-based platform: KKP on bare metal with KubeVirt and Kube-OVN, across two regions and three availability zones, with all infrastructure, operations and support in Switzerland. The CNCF published it as a reference architecture. Read Swisscom’s story.

How can I run my infrastructure without any foreign provider having access?

To run your infrastructure without any foreign provider having access, operate the full stack yourself, including the control plane, identity and encryption keys, and run critical environments air-gapped where needed. Then no external party can access your systems or switch them off.

That means:

  • Self-hosting the management layer instead of relying on a foreign-managed service. Kubermatic Kubernetes Platform (KKP) can run in your own environment, even fully air-gapped.
  • Keeping keys and credentials in a system you operate, such as Kubermatic SecureGuard.
  • Removing uncontrolled remote support access, and requiring any external access to be approved, time-limited and audited.
  • Running fully offline where strict security or regulatory requirements demand it.
  • Using open-source software you can inspect, maintain and operate independently, and assessing your remaining dependencies on external vendors.

Where to start

Very few organizations can, or need to, become fully independent overnight. What matters is knowing where your dependencies are, and deciding which ones you are willing to accept.

Start with your most critical systems. Make them portable, keep them under your jurisdiction, and hold your own keys. Every step makes your business more resilient, whatever happens in Washington, Brussels or anywhere else.

Want to talk through your sovereignty strategy? Talk to an expert.

Further reading

Abubakar Siddiq Ango

Abubakar Siddiq Ango

Senior Developer Advocate

Kubermatic Recognized in the 2026 Gartner® Magic Quadrant™ and Critical Capabilities for Container Management

Access the Report

Empower Your Business with Cloud Native Labs Consulting Services, Accelerators and Trainings

Discover More