A cloud isn’t just servers — it’s the software that provisions, schedules and governs them. That control plane is where much of the sovereignty question is actually decided, and it’s why we built ours on OpenStack.
Why open source in the governing layer
A closed control stack is one vendor decision away from becoming a risk. If the software that governs your resources is a black box under someone else’s control, your infrastructure depends on their decisions and their jurisdiction. OpenStack is open source: the code is auditable, portable and immune to supply-chain demands from outside the EU.
How we run it
We run the core services — compute, networking, block storage and identity — on our own hardware, with per-tenant isolation and keys in EU-resident OpenBao. No component in the governing layer requires an external SaaS that would drag in a foreign jurisdiction through the back door.
An open control plane isn’t anyone else’s to switch off. That’s the whole point.
— from Kepler’s engineering principles
Portability as a byproduct
Because OpenStack is an open standard, portability comes almost for free. Another OpenStack-based cloud can receive your resources without you rewriting everything. That makes exit credible — which, in turn, is the very basis for trusting that you can stay.