The whole platform runs inside your perimeter, control plane included, with no dependency on anything hosted outside. Teams still self-serve managed Kubernetes, PostgreSQL and VMs, and nothing about your workloads leaves the site.
Air-gapped environments normally pay for isolation twice: once in the network design, and again in the operating model, because the tools that make Kubernetes pleasant assume a hosted control plane, a registry on the internet and an update path through it. So classified sites, ships, factories and defence estates end up with hand-built clusters and change windows. edgeContinuum is designed the other way round. In the on-premises model the entire platform runs inside your perimeter, so air-gapped Kubernetes is the same product as the hosted one: the same console, the same API, the same managed services, with no dependency on a control plane you do not own.
In the on-premises model there is no hosted component in the path: the console, the API and the control plane all run on your infrastructure, operated by your team. Workloads, data and platform metadata stay inside the perimeter, and access within the platform is governed by the organizations, projects, roles and quotas you define.
The same design that serves classified estates serves ships, plants and points of presence: regions are autonomous, so a site is never one WAN outage away from being unmanageable. Combine that with a curated catalog and private application templates and a disconnected site still feels like a cloud to the people using it.
Whole platform in your perimeter, no uplink required.
Desired state pulled and reconciled locally.
Your own applications as one-click products.
Your hardware, your data, supported from the EU.
Book a call to walk through the on-premises model with our engineers, or request a free trial and start against a lab OpenStack.
