Docs
Sign In

A sovereign cloud on hardware you control

Sovereignty here is architecture, not a compliance badge: your hardware, your network, your data, with the whole platform able to run inside your perimeter, down to fully air-gapped sites. Built and supported in the EU.

Book a callRequest a free trial
Runs entirely inside your perimeter when you need it toAir-gap capable, down to fully disconnected sitesBuilt and supported in the EU
On-premises model
Your perimeter
Console & APIyour teams
Control planeoperated by you
edgeContinuum
Your OpenStackyour hardware
Your datanever leaves
Air-gap readyno uplink required

Residency is not sovereignty

Most of what is sold as sovereign cloud is a hyperscaler region with local paperwork: the data sits in your country while the control plane, the update pipeline and the operational control sit somewhere else. The questions that matter are structural. Who operates the control plane? Where does the platform phone home? What still works when the uplink is cut? edgeContinuum answers all three with architecture: the entire platform can run inside your perimeter, operated by your team, on OpenStack and open-source foundations you can audit, with no dependency on a foreign control plane.

Sovereign virtualisation and sovereign Kubernetes

A sovereign virtualisation platform guarantees that your hypervisors, virtual machines, networks and storage remain entirely under your legal jurisdiction and operational perimeter. Built on OpenStack, open source and fully auditable on your hardware, no proprietary layer sits between you and your compute. It delivers true freedom: the ability to inspect the code, operate indefinitely, and migrate without lock-in.

The second layer is Kubernetes. Sovereign Kubernetes means clusters and control planes run wherever you choose, including fully air-gapped sites, with zero vendor telemetry or call-home dependencies. Clusters are CNCF-conformant standard Kubernetes, keeping all Helm charts, operators and CI manifests completely portable.

OpenStack virtualisationCNCF-conformant clustersControl planes where you chooseNo call-home dependency

Set against what is usually sold as an open sovereign cloud, a hyperscaler region with local governance, the structural differences are simple to state. Those offers get data residency right and stop there: the control plane is regional endpoints backed by shared global services, operated by the provider, and management stops when the uplink does. Here the control plane can be a dedicated instance inside your perimeter, operated by your team, on OpenStack and CNCF Kubernetes you can audit, and a site keeps running with the cable pulled.

Deployment models

From SaaS to fully air-gapped

Sovereignty is a spectrum and you pick the point: start with the SaaS control plane against your infrastructure, or run it fully on-premises, where everything, control plane included, lives inside your perimeter. Same console, same API, same managed services at every point.

Same platform everywhereStart SaaS, move insideClassified-environment ready

SaaS

Fastest start

We host and operate the control plane; you connect infrastructure. Workloads and data stay on your hardware.

On-premises

Sovereign by design

Run the control plane on your own servers: the whole platform, sovereign, on your side, internet-facing or not. Nothing depends on us.

Air-gapped

No uplink

Fully disconnected sites: the platform installs, runs and updates without internet access.

Link independence

Sovereign also means when the link drops

Autonomy is part of control. Regions in edgeContinuum are autonomous: if a site loses its connection to the core, workloads keep running and local management keeps working, then everything resyncs when connectivity returns. A remote plant, a ship or a classified site does not stop being a cloud because a cable does.

Autonomous regionsLink-loss tolerantResync on reconnect
One platform, sovereign sites
edgeContinuum
EU data centeryour region
Classified sitetotal isolation
Edge siteautonomous, resyncs
Still a cloud

Sovereign, and still self-service

Sovereignty usually costs you the cloud experience; here it doesn’t. Inside the perimeter your teams still get managed Kubernetes, PostgreSQL, VMs and an app marketplace, self-service inside organizations, projects and quotas, with usage tracked per tenant. Open foundations underneath (OpenStack, Kubernetes) mean no proprietary layer between you and your infrastructure.

Managed KubernetesManaged PostgreSQLVMs & networkingApp marketplace

Kubernetes

Conformant clusters, in-place upgrades, autoscaling.

PostgreSQL

HA databases with lifecycle handled by the platform.

Virtual machines

Catalogs, networks and firewall rules, like public cloud.

Marketplace

Your apps as one-click products for every team.

Sovereignty you can demo, not just declare

Book a call and we’ll walk the on-premises model against your requirements, or start on the free trial and see the platform before any commitment.

Book a callRequest a free trial

Frequently asked questions

What is a sovereign cloud?
A sovereign cloud is one where the data, the operations and the control of the platform all stay under a jurisdiction and an organization you accept. Data residency alone is the weakest version of it: your data sits in-country while the control plane, the update pipeline and the people with operational access sit elsewhere. The stronger test is structural, and it is three questions. Who operates the control plane? What does the platform have to reach to keep working? What still functions if that connection is cut? edgeContinuum is designed so all three answers can be "you and your own site", including on hardware with no internet access at all.
Is the control plane in a sovereign cloud shared with non-sovereign regions, or fully independent?
In most hyperscaler sovereign offerings it is shared: the regional endpoints are real, but they are backed by global identity, billing and management services the provider operates centrally, which is why sovereignty claims there rest on contracts and governance rather than on topology. With edgeContinuum it is your choice, and it is topological. In the on-premises model the control plane is a dedicated instance running inside your perimeter, with no shared multi-tenant layer and no dependency on ours; you can cut the uplink and it keeps operating. In the SaaS model we host a control plane and your workloads and data still stay on your hardware. Nothing is shared between one customer’s on-premises control plane and anyone else’s.
What is sovereign Kubernetes?
Kubernetes whose clusters and control planes run where you decide, on infrastructure you own, without a vendor service they must reach to stay healthy. The important part is that it is standard: edgeContinuum provisions CNCF-conformant clusters with no fork and no proprietary APIs, so Helm charts, operators and CI work unchanged and your workloads remain portable. Control planes can be dedicated or hosted, and in the on-premises and air-gapped models both the clusters and the platform managing them sit inside your perimeter.
What functional gaps should we expect moving from public cloud to a sovereign cloud, and how do we mitigate them?
Worth being direct, because this is where sovereign migrations disappoint people. You keep the primitives: managed Kubernetes, managed PostgreSQL, VMs with real networking, an app marketplace, quotas and per-tenant usage. What a private platform does not reproduce is the long tail of a hyperscaler catalogue. edgeContinuum does not ship a managed serverless or functions product, and it is not a CDN: there is no global anycast point-of-presence network for edge content delivery. Elasticity is bounded by the hardware you own rather than effectively infinite. The practical mitigations: autoscaling node pools cover most burst patterns; function and queue runtimes (Knative, OpenFaaS and similar) run as ordinary workloads on managed Kubernetes and can be published in your marketplace as one-click products; and where you need geographic proximity, edge sites put a full managed platform close to users, each reconciling locally so it survives link loss. If a global CDN is genuinely load-bearing for you, plan to keep one in front.
In SaaS mode, what leaves our perimeter?
Your workloads and data stay on your hardware in every model; in SaaS only the control plane runs hosted by us. If that is still too much, the on-premises model moves the whole platform inside your perimeter.
What works in a fully air-gapped site?
The platform itself: console, API, managed Kubernetes, PostgreSQL, VMs and the marketplace all run without an uplink. Regions are autonomous and resync whenever connectivity exists.
Who is behind edgeContinuum?
edgeContinuum is built and supported in the EU. The platform stands on open-source foundations (OpenStack, Kubernetes) rather than a proprietary virtualization stack, so there is no foreign-controlled layer underneath.
Does sovereignty cost us the managed experience?
No. The same managed services and self-service tenancy run in every deployment model; automation is driven by desired state inside the platform, not by a remote operations team.
How does this help with regulation?
Data residency, operational control and disconnection tolerance become properties of the architecture, which is the part auditors ask hardest about. You choose the deployment model that matches your regulatory reality. For detailed regulatory architecture, see our sovereign cloud blueprint for NIS2 and DORA.

Keep exploring

Edge computingPrivate cloud platformFor service providersProduct tourAir-gapped KubernetesCompare platformsResources