Docs
Sign In

The Tanzu alternative that isn’t tied to vSphere

Standard, CNCF-conformant Kubernetes, plus the VMs and databases a platform needs, on OpenStack you control instead of a vSphere licence you are trying to leave. Priced per managed resource. Your charts, operators and tooling work unchanged.

Book a callRequest a free trial
Standard CNCF Kubernetes, not a vSphere-bound distributionRuns on open OpenStack, no VMware licence under your clustersLicensed per managed resource, not per core or per socket
Tanzu today
Tanzu Kubernetes Gridthe clusters
Supervisor / vSpherethe foundation
vCentermanagement
edgeContinuum
Managed KubernetesCNCF conformant
PostgreSQLmanaged, HA
VMson your OpenStack
On edgeContinuum

Why teams are leaving Tanzu

Tanzu was the way you got Kubernetes out of your VMware estate. Since the Broadcom changes it arrives folded into VMware Cloud Foundation: to keep managed Kubernetes you carry the whole bundle, and the standalone path teams relied on is no longer the simple purchase it was. The credible exit is open infrastructure; the honest problem with that exit is that raw OpenStack plus DIY Kubernetes is powerful but operationally demanding.

That is the gap edgeContinuum closes: managed, conformant Kubernetes, virtual machines and databases, a modern console and one API, all on OpenStack you own. You leave the bundle without trading down to a build-it-yourself platform project.

Kubernetes shouldn’t require a vSphere licence

This is the part a generic comparison misses. Tanzu Kubernetes Grid runs on vSphere: a Supervisor cluster and ESXi underneath every workload cluster. So the Kubernetes you adopted to modernise sits on top of the exact VMware licensing you are trying to escape, and the two cannot be separated.

edgeContinuum runs conformant Kubernetes on OpenStack, an open foundation with no proprietary hypervisor licence beneath your clusters. You get standard clusters your teams already know, on infrastructure that is yours, priced per managed resource. (For the head-to-head on distro pricing, see the OpenShift alternative.)

Where your Tanzu workloads land

Tanzu Kubernetes Grid clusters
CNCF-conformant managed KubernetesStand up standard clusters and redeploy your workloads onto them: Helm charts, operators and CRDs run unchanged, with autoscaling node pools and in-place upgrades
vSphere VMs under Tanzu
OpenStack VMs, managed like public cloudImage and flavor catalogs, SSH keys, and networks, routers and firewall rules from the console
vCenter and Supervisor management
One console, one API, plus TerraformEvery cluster, VM and database you operate, managed from a single pane
Multi-cluster fleet management
Desired-state automationUpgrades, scaling and failure recovery run continuously across every region, without runbooks
VCF bundle, per-core licensing
Per managed resourceOpen-source foundation with a subscription per resource managed through the platform, independent of cores, sockets or users

What you gain in the move

One migration, not two

Don’t move to bare OpenStack and then spend years rebuilding managed Kubernetes on top. Land directly on a platform where clusters, VMs and databases are one click away.

Sovereignty included

From shared SaaS to fully air-gapped sites: the same platform and API. Your hardware, your data, your perimeter, with no foreign licensing lever over your infrastructure.

More than Kubernetes

Standard clusters are the starting point. You also gain managed PostgreSQL, OpenStack VMs and an application marketplace your teams serve themselves from.

Frequently asked questions

What are the main Tanzu alternatives and competitors?
The Kubernetes platforms people weigh against Tanzu are usually Red Hat OpenShift, Rancher, Google Anthos and the managed Kubernetes services of the public clouds, plus building on upstream Kubernetes with Cluster API. They differ mostly in how opinionated the distribution is and how much of the platform you still assemble. edgeContinuum sits in a different place on purpose: standard CNCF-conformant Kubernetes with no fork, and the layer underneath and around it managed too, your OpenStack shaped into regions, managed PostgreSQL, VMs with real networking, and multi-tenant quotas with per-tenant usage. Critically, none of it requires a vSphere licence underneath.
We are leaving VMware entirely. Does that change the Tanzu decision?
It usually simplifies it. Tanzu’s value is tightest when vSphere stays, because that is the substrate it assumes. If the vSphere licence is the thing you are exiting, keeping Tanzu means paying for the platform layer while replacing the layer it was designed to sit on. Moving both together to open infrastructure is normally less work than moving them separately, and it is the same migration our engineers plan with you.
Will our Helm charts and operators work?
Yes. Clusters are CNCF-conformant standard Kubernetes, so Helm charts, operators, CRDs and CI pipelines work unchanged. There is no fork and no distribution-specific API to lock into, so what runs on your Tanzu clusters runs here.
Do we need OpenStack to use edgeContinuum?
Yes, OpenStack is the foundation, and that is deliberate: it is the mature, open, widely deployed virtualization layer. edgeContinuum changes operability: you manage clusters, VMs and databases through the console and API rather than operating raw OpenStack day to day. Coming off Tanzu on vSphere, you replace the Kubernetes layer and the virtualization underneath it in one move, instead of solving them as two separate projects.
What happens to the vSphere VMs running under Tanzu?
They move onto OpenStack virtualization and are managed from the same console and projects as your clusters: image and flavor catalogs, networks, routers and firewall rules. VM images import through standard tooling, and our engineers work the migration plan with you.
How do we manage clusters across sites without Tanzu Mission Control?
Fleet management is built into the platform. Every cluster, in every region, is driven from one console and API by declarative desired state, so upgrades, scaling and recovery run continuously. Regions stay autonomous under link loss and resync when connectivity returns.
How do our Tanzu clusters move over?
You don’t lift the clusters themselves. You stand up fresh, conformant clusters on edgeContinuum and redeploy your workloads onto them, which is straightforward precisely because they are standard Kubernetes: Helm charts, operators and CRDs run unchanged. Our engineers work the plan with you: cluster sizing and control plane models, redeploying workloads, moving vSphere VM images into OpenStack, and shaping your sites into regions and zones. Start on the SaaS control plane against a lab OpenStack, or book a call for an on-premises pilot.

Keep exploring

VMware alternativeOpenShift alternativeKubernetes on OpenStackProduct tourNutanix alternative

Plan your exit with engineers, not salespeople

Tell us what your Tanzu and vSphere estate looks like and we’ll map it to open infrastructure together, honestly, including the parts that take work.

Book a callRequest a free trial