One page per product, written for the people doing the evaluation. Some of these you would replace with edgeContinuum. Others solve a different layer and can sit alongside it, and those pages say so. Start with whatever you run or are shortlisting today.
Each of these pages runs the same ladder: every piece of the platform you have today, and what it becomes when the infrastructure is OpenStack and the services on top are managed. They are written to be read before a call, not after one.
Start here if you know what you are replacing. If you are still deciding whether to replace it, the shortlisting guide works through the four routes out of VMware first, and the migration guide covers execution once the direction is set. For Kubernetes specifically, the Kubernetes on OpenStack architecture guide and the OpenStack self-service platform architecture guide cover the layer above the hypervisor.
Off vSphere and the VCF bundle, onto open infrastructure you own, with managed services on top.
Read the pageKeep Prism-style self-service without the appliance model or per-node licensing.
Read the pageStandard, conformant Kubernetes instead of a distribution, priced per managed resource.
Read the pageManaged Kubernetes that is not tied to vSphere, with your Helm charts unchanged.
Read the pageWhen one cluster is not enough: tenancy, quotas, managed services and many sites.
Read the pageMove past IaaS orchestration to a managed services catalog you curate.
Read the pageComparisons are only half the decision. These pages answer the questions that come up once the direction is settled: how the two stacks really differ, what isolation costs you, and how the managed services behave on your own hardware. Where a platform page argues the case, these argue the mechanics.
The permission model all three comparisons come back to: users, groups, roles composed per action, organization or project scope.
Read the pageWhy add anything if OpenStack already runs? Where each layer sits, and what changes for the people consuming it.
Read the pageWhat each stack gives you, what it asks in return, and where the operability gap sits.
Read the pageThe whole platform inside your perimeter, still self-service, nothing leaving the site.
Read the pageDatabases as a service on your own OpenStack, high availability and lifecycle handled.
Read the pageHow clusters, control plane models and node pools actually work here.
Read the pageThese three are not hypervisors, they are products that sit where edgeContinuum sits, on top of an OpenStack somebody already runs. The pages are written to be useful even if you pick the other one: each says plainly what the other product does better, because the honest answer usually depends on which layer you are trying to solve.
Both are OpenStack underneath. The question is whether you want a second control plane or want to keep the one you run.
Read the comparisonSelling OpenStack resources with billing attached, against building managed services on the infrastructure underneath.
Read the comparisonA billing and portal layer that makes OpenStack consumable, against a service layer that runs Kubernetes and databases on it.
Read the comparisonBook a call and we will walk your current stack through the ladder that fits it, or request a free trial and provision managed services on your own infrastructure.
