Sovereignty is about control: where your data is stored, who can operate and access the systems that hold it, which jurisdiction they fall under, and whether you can walk away from a provider without rebuilding everything.
A proprietary stack can be hosted in the right country and still leave the important decisions with its vendor. Open source changes that. When the software is open, upstream and portable, any capable team can run it — yours, a local provider’s, or ours.
What makes a cloud sovereign
- Location — data and services stay in the data centres and countries you choose.
- Operations — the people with access are the people you choose, and you can change them.
- Software — the whole stack is open source, with no licence that can be withdrawn or repriced.
- Portability — workloads, data and automation move between operators without rewriting.
How we approach it
We build sovereign clouds from the same open infrastructure we use everywhere else: OpenStack for the cloud layer, Kubernetes for platforms, Metal3 and Ironic for hardware, and Zuul to test every change. Everything is configured in code, kept in your repositories and documented so that another team could take over.
That’s the point of upstream first here: there is no proprietary layer, no private fork, and nothing that only we can operate.
Where we help
- New sovereign clouds — for organisations, public bodies and providers building their own.
- Existing platforms — finding lock-in, planning an exit and moving to open components step by step.
- Providers — local and regional clouds that want to offer sovereign services on open infrastructure.