Docs
Sign In

Turn the OpenStack you run into a cloud people can use

edgeContinuum is an OpenStack management platform that adds what raw OpenStack never shipped: a self-service console, managed Kubernetes, PostgreSQL and VMs, and real multi-tenancy, on the deployment you already operate.

Book a callRequest a free trial
Works with the OpenStack you already operateConsole, API and Terraform for every teamNo rip and replace, no fork
Who serves themselves
Developersclusters & DBs
Client teamsown orgs & quotas
Platform teamguardrails
edgeContinuum
Your OpenStackunchanged underneath

OpenStack gives you primitives. Your teams need a cloud.

Horizon was built for operators, and it shows: every VM, network and volume is a form to fill, every Kubernetes cluster is a project someone glues together, and every request from a team lands in a queue in front of the few engineers who know OpenStack well. An OpenStack management platform closes that gap without touching what works: edgeContinuum layers a self-service portal, managed services and structural multi-tenancy on top of your existing deployment, and drives everything through declarative desired state instead of tickets.

Self-service on top

A console your teams serve themselves from

Point edgeContinuum at your OpenStack and teams stop filing tickets: they create Kubernetes clusters, PostgreSQL instances and VMs from the console, the API or Terraform, inside quotas and roles you define. Horizon stays for your operators; this is the front door for everyone else.

Web consoleAPITerraformQuotas & roles
NameTypeHealthRegion
prod-eu-westSCPHealthydc-vigo
analytics-dbPG 16Healthydc-vigo
web-frontendVM c3-4Onedge-01
+ CreateManage
Managed services

Beyond IaaS: services OpenStack never shipped

Raw OpenStack ends at VMs, networks and volumes. edgeContinuum adds the layer your teams actually ask for: managed Kubernetes with autoscaling and in-place upgrades, managed PostgreSQL with lifecycle handled, VM catalogs managed like public cloud, and an app marketplace where anything Kubernetes-deployable becomes a one-click product.

Kubernetes

CNCF-conformant, dedicated or hosted control planes.

PostgreSQL

HA, size and storage declared up front; lifecycle managed.

Virtual machines

Image and flavor catalogs, networks and firewall rules.

Marketplace

Helm charts and containers as one-click products.

Multi-tenancy

Tenancy OpenStack projects can’t express

Organizations, projects, users, roles and quotas, enforced by the platform’s IAM. Each team or client gets an isolated organization with its own members and limits, and usage is tracked per tenant, ready for your accounting. Isolation is structural, not a naming convention on top of OpenStack projects.

Organizations & projectsRole-based accessQuotas per projectUsage per tenant
Organizations
acme-telecom8 projects
eng-platform4 projects
data-team2 projects
edgeContinuum
Your OpenStackquotas & usage enforced
Scale out

Many OpenStacks, one platform

Connect any number of OpenStack deployments (data centers, private clouds, edge sites) and shape them into your own regions and availability zones. Regions are autonomous: if a site loses its link, workloads and local management keep working and resync when connectivity returns.

Multi-regionAvailability zonesAutonomous edgeLink-loss tolerant
One control plane
edgeContinuum
Region Adata center
Region Bprivate cloud
Edge siteautonomous
Your OpenStacks, shaped into regions and zones

Frequently asked questions

Does it replace Horizon?
For your teams and clients, yes: they work in the edgeContinuum console and API instead. Your operators can keep Horizon and their existing OpenStack tooling; the platform does not fork or modify your deployment.
Do we have to reinstall or migrate our OpenStack?
No. You connect the OpenStack you already run. The platform builds its managed services and tenancy on top and keeps everything in desired state; nothing underneath is ripped out.
What does the platform manage for us day to day?
The full lifecycle of the services it provisions: Kubernetes upgrades, autoscaling and self-healing, PostgreSQL lifecycle, VM catalogs and networking, driven by declarative desired state instead of manual runbooks.
Can we run several OpenStack deployments under one console?
Yes. Connect any number of deployments and shape them into regions and availability zones. Each region stays autonomous under link loss and resyncs when connectivity returns.
How is it priced?
A subscription per resource managed through the platform (clusters, databases, VMs), independent of vCPUs, cores or users, and of your deployment model.

Keep exploring

Private cloud platformKubernetes on OpenStackProduct tour

See your OpenStack become a cloud

Connect a lab OpenStack on the free trial, or book a call and we’ll demo the loop end to end: connect, curate, provision, operate.

Book a callRequest a free trial