← Back to overview
Why Not One Provider

"Sovereign cloud" is a label.
Sovereignty is a governance model property.

Several major providers now offer "sovereign cloud" options. The question isn't whether the label is genuine. The question is whether any provider — however EU-aligned — can transfer sovereignty to your organisation simply by offering it.

IT Strategy · Architecture · Procurement

Sovereignty can't be delivered by a provider — only maintained by the organisation.

Sovereignty means the ability to define, enforce, and evidence your own governance model — including the ability to exit a provider relationship without catastrophic disruption. A provider offering "sovereignty" as a product feature is offering something structurally different from the sovereignty it claims to deliver.

If your governance model depends on that provider's control plane, their sovereign offering doesn't give you sovereignty over your infrastructure — it gives you sovereignty within their infrastructure. Those are different things.

The organisation that controls its governance layer controls its infrastructure. The organisation that delegates its governance layer to a provider controls very little.

What "sovereign cloud" typically means in practice

Most sovereign cloud offerings include: EU data centre locations, EU-incorporated operating entities, restrictions on non-EU staff access, and local data portability guarantees. These are meaningful steps. They are not sovereignty.

What they typically don't provide: an independent governance layer you control, a clear exit path that doesn't require rebuilding your operational model, or freedom from the provider's own pricing and terms evolution.

Provider sovereignty vs. governance model sovereignty

Single-provider "sovereign cloud"

  • Governance is within the provider's control plane
  • Exit requires rebuilding the operational model
  • Provider concentration risk remains
  • Pricing and terms set unilaterally by the provider
  • No independent audit trail — evidence via provider's tools

Governance model sovereignty (emma)

  • Governance layer is independent of any single provider
  • Workload migration doesn't require rebuilding governance
  • Provider diversity removes concentration dependency
  • Commercial leverage preserved through genuine optionality
  • Independent continuous audit trail across all providers

emma has no commercial interest in which provider you choose

emma does not own cloud infrastructure. emma doesn't sell cloud capacity. emma has no commercial bias toward any provider — hyperscaler, EU-sovereign, or private cloud. The governance layer making your placement decisions shouldn't benefit commercially from any particular placement outcome.

emma works with hyperscalers where hyperscalers are the right choice. It works with EU-sovereign providers where jurisdictional requirements demand it. It works with on-premises infrastructure where that's what the workload needs. The decision is yours — governed by your policy, not by emma's economics.

"The test for whether you have sovereignty is not which cloud you're on. It's whether you can leave — without catastrophic operational disruption, without rebuilding your governance model from scratch, and without losing the commercial leverage that comes from genuine optionality."

The governance model is the differentiator

The competitive brief covers the sovereignty-as-label problem in detail, including how to evaluate sovereign cloud offerings against governance model criteria.

Book a Governance Walkthrough Take the Assessment