Every organisation that runs on someone else's infrastructure is making a bet: that the price, the terms, the availability, and the access will not change in ways that harm it. For years that bet felt safe. It no longer does.

The dependency you did not quite choose

Hyperscale cloud became the default for good reasons - it is convenient, capable, and quick to adopt. But convenience accumulates into dependency. Over time, critical workloads, data, and institutional knowledge settle onto a single provider's platform, using that provider's proprietary services, priced on that provider's terms, governed by that provider's jurisdiction.

None of that is a problem until it is. A pricing change, a policy shift, a regulatory ruling, or a geopolitical event can turn a convenient arrangement into a strategic liability - and by then, moving is expensive, slow, or practically impossible.

What sovereignty actually buys you

Sovereign computing is not about distrusting every supplier or running everything yourself. It is about keeping control of the decisions that matter:

• where your data physically sits, and under whose laws
• whether you can leave a provider without rebuilding from scratch
• whether your infrastructure keeps working if a supplier relationship ends
• who holds the keys, the identity system, and the logs

These are architectural properties. Sovereign infrastructure is built so that control stays with you by design, rather than being promised in a contract.

Exit as a design principle

The clearest test of sovereignty is whether you can leave. Hyperscalers are increasingly subject to switching rules - in the EU, customers have the right to move within defined periods, and further unbundling obligations are expected. But a legal right to switch is worth little if the architecture makes switching impractical.

Sovereign computing puts the exit plan into the design: data and workloads in standard, portable formats; open interfaces between every layer; no single proprietary service that cannot be replaced. The ability to walk away is what gives you leverage, even if you never use it.

The regulatory tailwind

The direction of travel in Europe is clear. The EU Cloud Sovereignty Framework sets out what sovereignty should mean. NIS2 raises the bar on operational resilience and supply-chain accountability. The Cyber Resilience Act places obligations on the software in your stack. Data-residency rules constrain where regulated data may live.

Meeting these obligations is far easier on infrastructure that was sovereign by design than on a platform retrofitted with a sovereignty label.

Being honest about the trade-offs

Sovereign computing is not free and not effortless. Convenience is the single biggest reason organisations choose hyperscalers, and that convenience is real. The perception that running your own foundation means taking on unmanageable risk is widespread - even where it is not true.

This initiative exists partly to close that gap: to make sovereign computing well-defined, conformance-tested, and genuinely procurable, so that choosing it is a sound, low-drama decision rather than a leap of faith. The aim is to remove the excuses for not choosing an open, sovereign, European option - by making the open option the easy one.

Where to start

If you are weighing your own exposure, begin with what sovereign computing is and the capabilities it covers. We are also developing a short sovereignty self-assessment that will give you a tailored view of where you stand - if that would be useful, tell us.

If your organisation wants to shape the category or offer conformant services, get involved.