edgeContinuum is the private cloud managed services platform that cloud service providers (CSPs), MSPs and telcos use to sell managed Kubernetes, PostgreSQL and virtual machines on OpenStack: multi-tenant from the ground up, with usage tracked per client and a catalog you curate.
Every client lives in its own organization with its own projects, users, roles and quotas. Clients sign in, provision managed services inside the limits you set, and never see each other or your plumbing. You operate one platform underneath all of them. The users, projects and quotas guide explains why OpenStack projects alone do not express a client, and the databases on OpenStack guide does the same for the database catalog.
Hard isolation per client, with projects, groups and composed roles inside each organization: your client’s own administrator invites their people and assigns access, while the platform permissions stay with you. See identity and access.
Set resource limits per organization and project, and read usage per tenant: the numbers your billing needs, per client, per period.
Choose what each client can buy: managed Kubernetes, PostgreSQL, VMs, and applications, including your own apps published as private templates.
The cloud you sell should look like your cloud. Run on-premises and the whole platform lives inside your perimeter, on your own hostnames, under your own name: your clients sign in at your address and never encounter ours. The catalog they browse is the one you curated, and the applications in it can be your own, published privately for your tenants.
The console, the API and sign-in all answer on hostnames you own, so the address bar carries your name from the first click.
Your mark, your contact address and your policies in front of your clients, rather than a vendor logo on a portal you are reselling.
You decide which services and applications each client can buy, and your own apps sit alongside the standard ones as private products.
The commercial relationship stays yours end to end: your tenants, your prices, your invoices from your own billing, and per-client usage figures exported from the platform to feed them. We do not appear between you and your customer.
A private cloud managed services platform allows service providers to offer turnkey, self-service cloud infrastructure to their clients without building a dedicated internal platform team. Reselling public cloud is a race to thin margins and vendor lock-in. Running a managed services platform on your own infrastructure flips the economics: hardware you already amortize, services priced by you, and a catalog carrying your brand. If you are comparing that against an OpenStack billing portal, see how we differ from Fleio, OSIE and Platform9. The self-service platform architecture guide covers the platform layer that makes it repeatable per client.
edgeContinuum delivers exactly this on top of OpenStack: automated managed Kubernetes, high-availability PostgreSQL and virtual machines with hard multi-tenancy and per-client usage tracking.
CNCF-conformant clusters your clients provision themselves: autoscaling node pools, in-place upgrades, dedicated or hosted control planes. They download a kubeconfig and ship. What those clusters are built from is set out in the Kubernetes on OpenStack architecture guide.
Production databases with provisioning, high availability and lifecycle handled by the platform. Your clients connect; nobody babysits.
Image and flavor catalogs with networks, routers and firewall rules managed like public cloud, on your hardware.
Helm charts and containers your clients instantiate with one click, and your own value-added apps rolled out across every region as private templates.
Most providers arrive here already reselling: a hyperscaler agreement, a margin set by someone else, and a customer relationship that belongs partly to the vendor whose logo is in the console. The alternative is not building a cloud from nothing, it is putting a platform layer on the infrastructure you already own and operate, and selling managed services on top of it.
Invoicing stays in the billing system you already run. The platform meters usage and quota per organization, project and managed resource and exports it as JSON or CSV, so there is one source of truth for revenue and nothing to reconcile between two systems.
Connect as many infrastructures as you operate (your data centers, private clouds, client sites, edge locations) and shape them into your own platform regions and zones. Regions are autonomous by design: a client site that loses connectivity keeps serving, and resyncs when the link returns. Built for footprints that include factories, ships and points of presence.
Book a call and bring a client use case: we’ll walk the tenancy model, the catalog and the usage reporting end to end.
