One page per stack, written for the people doing the evaluation: what you are leaving behind, where each piece of your estate lands, and what the managed layer on OpenStack does differently. Start with the stack you run 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.
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.
What 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 pageBook 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.
