Give teams the database experience they expect from a public cloud, on hardware inside your perimeter: PostgreSQL provisioned on request, highly available, lifecycle handled, scoped to the project that owns it.
On-premises databases usually arrive in one of two shapes: a request in a ticket queue that takes days, or a virtual machine a team installed PostgreSQL on and now nobody wants to touch. Both mean the same thing, that managed PostgreSQL on-premises is a person rather than a service. edgeContinuum makes it a product in your catalog: a team asks for a database inside its project, the platform provisions it with high availability and the right storage size, and lifecycle management is the platform’s job from then on. It runs on the OpenStack you already operate, so the data stays exactly where your compliance story needs it.
What teams mean when they ask for a managed Postgres service is usually a public cloud DBaaS experience: pick a size, get a connection string, never think about the host again. That expectation is the standard now, and it is why an internal database request measured in days feels broken. edgeContinuum delivers the same shape of service, a fully managed Postgres instance provisioned from a catalog alongside managed Kubernetes and virtual machines, on infrastructure you own rather than someone else’s region.
The difference from a hyperscaler managed database is where it sits and who can reach it: your OpenStack, your storage, your network, and in the on-premises model a control plane inside the same perimeter. Learn more on our private cloud platform page, or explore our private cloud PostgreSQL DBaaS reference architecture.
Databases live where the rest of the platform lives: inside a project, under the quotas that project was given, requested from the same console, API or Terraform provider as clusters and VMs. Who may read an instance, read its metrics or delete it are separate permissions, so a database team can operate without holding destructive access (see identity and access). Teams stop waiting for provisioning, and platform owners keep the guardrails, because who can create what is governed by roles and quotas.
The platform runs on declarative foundations, so a database is a declared desired state that the system keeps true: provisioning, high availability, storage sizing and lifecycle management are handled rather than scheduled. The AI assistant in the console answers questions about what you run, including inventory, versions and health.
From the catalog, inside the requesting project.
Declarative foundations, no configuration drift.
Quotas per project, usage tracked per tenant.
On your OpenStack, air-gap capable, EU-built.
Most databases exist to serve an application, and that application usually runs on a cluster. Here both are services in the same platform, in the same project, with the same roles and quotas: a managed Kubernetes cluster, its PostgreSQL instance and the VMs around them, provisioned from one console and reconciled by one control plane.
CNCF-conformant clusters on your OpenStack.
Catalogs, networks, routers and firewall rules.
Helm charts and your own apps in one click.
Several infrastructures shaped into one platform.
Book a call to see managed databases in the console, or request a free trial and provision one on your own infrastructure in minutes.
