Need GPUs? Ship without a waitlist.
Get started
Why Digital Independence and Cloud Performance Is Just a Perceived Trade off
"Sovereignty means flexibility, and flexibility costs money." That's how Jochen Decker, member of the executive board at Swiss Federal Railways, put it at the 2026 Hamburger IT-Strategietage — one of Europe's most influential CIO gatherings. He compared it to an insurance premium. You can choose not to pay it. But when something goes wrong, it hurts.
The panel he shared with Prof. Helmut Krcmar (TU Munich) and Anke Sax (CTO/COO, KGAL) painted a picture that will be familiar to any technology leader operating in Europe today: digital sovereignty is not optional, but the path to achieving it feels like a penalty on competitiveness. Walk away from the three dominant hyperscalers and you gain independence. However, it comes at a price that most organizations struggle to justify.
This framing — sovereignty as cost — has dominated the European cloud conversation for years. And it is wrong. Not because sovereignty is free, but because the cost is a symptom of deep rooted architectural problems, not an inherent property of independence itself.
The panelists in Hamburg identified the pain points clearly. Decker noted that when every competitor depends on the same providers, breaking away unilaterally is structurally punished. Krcmar pointed out that Europe demands alternatives to the hyperscalers but refuses to pay what it costs to sustain them. Sax described how
DORA regulation forced her organization to map its supplier dependencies for the first time — and the results were revealing.
These are real problems. But they share a common root: the absence of a management layer that lets organizations leverage all cloud environments equally.
When an organization uses AWS for compute, a sovereign European provider for regulated data, and on-premises infrastructure for legacy workloads, it doesn't just have three environments. It has three sets of dashboards, three cost models, three security paradigms, three governance frameworks, and three teams who understand each one. The "sovereignty premium" isn't the cost of using an additional sovereign cloud. It's the cost of operating in fragments.
This is the problem emma was built to solve.
emma is an enterprise multi-cloud management platform headquartered in Luxembourg. It doesn't replace cloud providers — it unifies them. Hyperscalers, sovereign clouds, private infrastructure, bare metal, GPU clusters, edge — all managed, optimized, and governed through a single operational layer.
This changes the sovereignty equation fundamentally. Here's how.
The most common objection to multi-cloud sovereignty is cost. But that objection assumes each environment is managed independently, with its own tools, its own team, and its own blind spots. emma consolidates cost visibility across every provider, applies AI-driven rightsizing and waste detection, automates scheduling of non-critical workloads, and routes inter-cloud traffic through its own networking backbone at roughly one-third of standard industry rates.
Organizations routinely discover that the savings from unified optimization exceed the incremental cost of sovereign alternatives. The "premium" doesn't just shrink, it even inverts.
Krcmar's metaphor was precise: sovereignty means being able to stand up from the negotiating table because you have alternatives. But alternatives only matter if you can actually use them — if workloads can move between providers without months of re-engineering.
emma abstracts infrastructure through a provider-agnostic orchestration layer. Workloads are portable. New providers — like IONOS, which emma integrated in January 2026 — can be onboarded and productive within the same management plane. Kubernetes clusters can span multiple clouds. The result is that "exit capability" stops being a strategic aspiration and becomes a standing operational feature.
When you can move workloads in minutes, not months, you negotiate differently.
Anke Sax made a critical observation: DORA forced her organization to identify its supplier dependencies, and the exercise was valuable precisely because those dependencies had been invisible. Most organizations have the same problem — not because they are careless, but because fragmented tooling makes holistic visibility structurally impossible.
emma provides centralized resource inventory, cost breakdowns by provider, region, service, and department, automated resource discovery, and cross-cloud audit trails. This isn't a compliance feature. It's the foundation of operational control. You can't manage concentration risk you can't see.
GDPR, NIS2 and DORA — the regulatory landscape for European enterprises is intensifying. Each framework demands transparency about ICT suppliers, data residency controls, incident reporting, and governance documentation. In a fragmented multi-cloud environment, meeting these requirements means manually reconciling information across multiple native dashboards, each with different taxonomies and different gaps.
emma operationalizes compliance through policy enforcement applied consistently across all providers. Data residency rules are automated at provisioning time. Access controls follow resources across clouds. Compliance checks run continuously against regulatory standards. Audit trails are unified.
The difference between "compliance as a project" and "compliance as a platform feature" is the difference between surviving an audit and operating with confidence.
The panel in Hamburg debated whether European organizations are willing to pay the sovereignty premium. It's a fair question, but it's the wrong framing.
The right question is: what is the cost of not having sovereignty operationally viable?
That cost is measured in deepening lock-in, deteriorating negotiating leverage, fragmented compliance posture, invisible dependencies, engineering capacity consumed by platform management instead of innovation, and — as Decker warned — a window of opportunity that is closing fast. "If we don't act now," he said, "the dependencies will be even greater in three or four years." Instead of focusing on the sovereignty premium, it’s time to focus on architectural choices and platforms that make sovereignty operational, viable, and even profitable.
emma doesn't ask organizations to choose between hyperscaler capability and sovereign control. It provides the unified management layer that makes both available simultaneously — governed consistently, optimized continuously, and portable by default.
The sovereignty premium doesn't have to be a cost. With the right operational foundation, it becomes a competitive advantage.
For CIOs ready to move beyond the debate:
See what you have
Connect existing cloud environments to emma to gain immediate, unified visibility into dependencies, costs, and compliance posture — without changing anything operationally.
Model the real cost of lock-in
Use emma's FinOps capabilities to compare the "sovereignty premium" against the hidden costs of concentration: egress fees, pricing leverage loss, duplicated tooling, compliance overhead.
Pilot a balanced strategy
Place regulated workloads on sovereign European providers while retaining hyperscaler services where they deliver genuine value — all managed through a single pane.
Build the exit muscle.
Establish workload portability as a standing capability. The ability to walk away from the table only matters if you can actually do it.
The panelists in Hamburg were right that the time to act is now. The infrastructure to act is already available.
This post references the panel discussion "Digitale Souveränität erkaufen: Warum CIOs jetzt aufstehen müssen" at the 2026 Hamburger IT-Strategietage, as reported by CIO.de.
