edgeContinuum vs Platform9, in one line: Platform9 brings its own private cloud platform and asks for your hosts. edgeContinuum sits on the OpenStack you already run and turns it into managed Kubernetes, PostgreSQL, VMs and apps. If your infrastructure works, you do not need to replace it to fix the layer above it.
Private Cloud Director deploys its own OpenStack-based control plane on your hosts. If you have one that works, adopting it means replacing infrastructure to fix the layer above it. edgeContinuum adds that layer directly: managed Kubernetes with real day-2 operations, managed PostgreSQL, an application catalog and permissions at the level of the individual action. Start a free trial and connect a lab deployment, or book a call.
Leaving VMware? Then this is the destination, not a detour: OpenStack underneath, edgeContinuum on top, with the migration path set out here.
Managed Kubernetes with real day-2. Clusters on Cluster API with the OpenStack provider, dedicated or hosted control planes, control plane upgrades on request, node pools that scale and autoscale, and failed nodes remediated by health checks.
Managed PostgreSQL. Instances under an operator with high availability, in-place version upgrades and storage growth, ordered from the same catalog as everything else. Platform9 documents no database service.
An application catalog. Helm and container applications, private to a project or published platform-wide, versioned, with your own private registry credentials.
Permissions at the level of the action. Roles composed from more than two hundred individual permissions, granted to a user or a group at organization or project scope. Platform9 documents three built-in roles, with a granular model in beta. See identity and access.
Both products are OpenStack underneath, and Platform9 says so in their own documentation: compute, block storage, network and identity expose OpenStack APIs, with Keystone for identity and Cinder for block storage. So this is not OpenStack against something else. It is whose OpenStack, and how many control planes you end up running.
Private Cloud Director installs KVM and an agent on your hosts and runs a management plane, hosted by them or self-hosted on K3s. Adopting it means adopting it as the platform. edgeContinuum installs nothing on your compute nodes: it points at the OpenStack endpoints you already have, which is why connecting an existing deployment takes hours rather than a migration, and your operators keep Horizon and their tooling.
Open a row if you want the detail behind it. Where their documentation is silent we say so, rather than claiming a capability is absent.
Sources: Platform9 product and architecture documentation and release notes to August 2026, plus their service provider programme page, checked September 2026.
If you are getting off vSphere, you are our core case, not a reason to look elsewhere. The route is OpenStack for the infrastructure and edgeContinuum for everything your teams touch: the VMware alternative page sets out where each piece of a vSphere estate lands, and the migration guide covers the phases. You do not have to move in one step, and you end up with managed Kubernetes, managed PostgreSQL and an app catalog rather than a like-for-like hypervisor swap.
The virtualization operations people ask about, live migration, VM high availability, rebalancing across hosts, come from OpenStack itself, configured by your team or ours during the build. What we add is the layer VMware never gave you either: self-service, managed services, tenancy that reports, and permissions per action.
Connect a lab OpenStack and see what the layer above it does. You will leave the call with a map of what your teams could be self-serving within a quarter, either way.
