VMware replacement after Broadcom: a guide for service providers, banks, and sovereign clouds in 2026

After Broadcom, the VMware bill stopped being predictable. Subscription-only licensing, mandatory VCF bundling, two-to-five-times price increases on renewal, and the end of perpetual licenses changed the math for every infrastructure team running VMware at scale. The result has been a documented wave of VMware replacement projects across service providers, banks, government, telecom, and AI/GPU operators evaluating how to exit VMware safely.

VMware competitors at a glance

If you’re scoping the market, here is how Cozystack compares to the most-cited alternatives to VMware:

• Cozystack (this page) — open-source, Kubernetes-native, multi-tenant. VMs + containers + databases + object storage + GPU on one platform. Best for service providers and regulated enterprises that need sovereignty and want one stack.
• Nutanix AHV — proprietary KVM-based hypervisor inside Nutanix HCI. Strong VM-only story, weak on Kubernetes-native multi-tenancy, expensive at scale.
• Proxmox VE — open-source KVM + LXC. Excellent for SMB and labs; thin on managed databases, multi-tenancy, and enterprise support model.
• Scale Computing HC3 — appliance-based hyperconverged stack. Good for ROBO/edge; closed ecosystem.
• Red Hat OpenShift Virtualization — KubeVirt-based, similar foundations to Cozystack. Heavier OpenShift footprint and Red Hat licensing model.
• OpenStack — broad, mature, large operational surface area. Best when you have a dedicated team running it.
• Microsoft Azure Stack HCI — Hyper-V on validated hardware. Locks into Microsoft licensing.
• Verge.io / Spectro Cloud / Platform9 — vendor-led KubeVirt or hyperconverged stacks; comparable to Cozystack on architecture, different commercial models.

The rest of this page goes deep on Cozystack as a Cozystack-specific VMware replacement. For a head-to-head listicle, see VMware alternatives.

Why teams replace VMware in 2026

The technical case for moving off VMware existed before Broadcom. Broadcom turned it into a board-level decision.

1. Unpredictable, subscription-only economics

VCF subscription pricing replaced perpetual licensing. Renewal quotes have come back at 2× to 5× prior spend across our pipeline. ELAs have been broken or restructured mid-term. Standalone vSphere SKUs were retired in favour of bundled VCF tiers that include components most customers do not need.

For service providers, this collapses margin: end-customer prices are sticky, license costs are not. For banks and regulated enterprises, it breaks multi-year capex planning that was built around perpetual entitlements.

2. Vendor lock-in across the stack

VMware’s strength was integration: vSphere, vSAN, NSX, vRealize, Horizon, vCD, all assumed each other. That same integration is now the lock-in surface. Replacing one component meant rebuilding adjacent ones, so most teams stayed.

Cozystack inverts this. Each layer is an independent open-source project (KubeVirt, LINSTOR/DRBD, Cilium, Kube-OVN, KubeVirt CDI, SeaweedFS, Velero, Flux, etc.), composed by a Kubernetes operator. You can replace any layer without rewriting the rest, and you can audit every line.

3. Sovereignty, regulator pressure, and US-vendor risk

DORA (in force across the EU since January 2025) and NIS2 require demonstrable control over critical ICT third parties. For European banks, telcos, and government workloads, depending on a US-headquartered closed-source hypervisor stack is a documented operational risk.

Cozystack is open source under Apache 2.0. Your binaries, your hardware, your data plane. Ænix ships air-gap install workflows and an advisory support model that does not require direct customer-environment access.

4. Pricing isn’t the only cliff — capability is

VMware’s roadmap is now Broadcom’s roadmap. KubeVirt and the Kubernetes-native virtualization stack have a community of hundreds of contributors and a release cadence VMware can no longer match in the open. GPU support, multi-tenant tenancy, modern storage replication, GitOps-native ops — all moved to Kubernetes-native projects years ago. VMware tries to retro-fit them through Tanzu and VCF.

What Cozystack gives you instead

Cozystack is a single platform you install on bare metal. Once it’s up, you have:

• Virtual machines through KubeVirt — full KVM-based VMs with live migration (CPU only), block-storage attach, snapshots, and templates.
• Tenant Kubernetes clusters for customers who want containers — every tenant gets their own K8s, isolated.
• Managed databases — PostgreSQL, MariaDB, MongoDB, Redis, Valkey, RabbitMQ, Kafka, NATS, ClickHouse, OpenSearch, Qdrant, FoundationDB — exposed as cloud services your tenants self-provision.
• S3-compatible object storage — for backups, application data, and AI training sets.
• GPU as a service — for VMs (VFIO passthrough, or NVIDIA vGPU with an NVIDIA licence) and for Kubernetes pods (whole-GPU through the NVIDIA GPU Operator, fractional sharing through HAMi). Validated on A100, H100, H200, L40S, and Blackwell.
• Multi-tenant control plane — Tenant Kubernetes CRD, nested tenants, per-tenant quotas and presets.
• Observability built in — VictoriaMetrics + VictoriaLogs, no Prometheus/Loki licensing trap.
• Backup and DR — Velero + S3 + per-database point-in-time recovery for managed services.
• Self-service portal and billing — through Cozystack Dashboard or via WHMCS integration (production-ready, two integration modes — see below).

It runs on your bare metal. No public cloud dependency. No phone-home telemetry by default.

VMware-to-Cozystack architecture mapping (vSphere alternative, ESXi alternative, vCenter alternative — all in one)

The questions every VMware admin asks first: “What replaces vSphere? What’s a real ESXi alternative? What replaces vCenter, NSX, vSAN, vCloud Director?” Here is the direct one-to-one mapping.

Two areas need redesign rather than one-for-one mapping: networking (Cilium is fundamentally different from NSX) and multi-tenancy model (Cozystack tenants are Kubernetes-native; vCD orgs are vSphere-native). For both, we run an architecture review before any migration commits.

How VMware migration actually works

Migration paths are workload-dependent. For most teams, this is the realistic sequence.

1. Discovery and assessment

We run a structured assessment of the current vSphere / VCF / vCD inventory: workload count, OS mix, vSAN / NSX dependencies, integrations (backup, identity, monitoring), and tenancy model. Output is a migration plan with workload buckets, risk flags, and timing.

2. Cozystack deployed in parallel

Cozystack is installed on new or repurposed hardware alongside the existing VMware estate. No big-bang cutover. Tenants migrate cohort by cohort.

3. VM-by-VM image migration to KubeVirt

For most VMs, migration is a disk-image copy. We use KubeVirt CDI plus a set of dedicated migration scripts we’ve built and reused across customer deployments. For Windows VMs and VMs with VMware Tools dependencies, we run an automated cleanup pass before boot on KubeVirt.

4. Network and storage cutover

Networking: VLAN mapping into Cilium, with policy parity checked against the source NSX rules. Storage: import disks into LINSTOR, validate IOPS and replication.

5. Validation and DR cutover

Each migrated workload runs in parallel on Cozystack until validated by the application owner. DR plans (Velero, PostgreSQL PITR) replace SRM playbooks before final cutover.

6. VMware decommission

Licenses end on their own terms. Hardware repurposed into the Cozystack cluster (we run on commodity x86 — your existing servers usually qualify).

For OpenStack, CloudStack, and Proxmox sources we run the same playbook with different image-import and network-mapping steps. Ænix has shipped each path in production.

Looking for a checklist? A detailed migration assessment template is on the roadmap. For now, a structured assessment is part of the engagement — book it through the form below.

Multi-tenancy and sovereignty

Cozystack was built for service providers first. The same model works for any organization that needs hard separation between business units.

• Tenant CRD — each tenant is a Kubernetes object. Namespaces are derived (<parent>-<name>), nested tenants are supported, quotas are enforced via Kubernetes ResourceQuotas.
• RBAC by default — tenants cannot see each other. Tenant operators get a scoped Kubernetes API.
• Air-gap install — supported and documented; works behind Harbor / Nexus / proxy patterns.
• No phone-home — telemetry is opt-in and disabled by default.
• DORA / NIS2-aligned controls — operational resilience, incident reporting, supplier-risk documentation. Architecture maps to the controls; certification, where required, is the customer’s audit process to run.
• Ænix support model — advisory, runbooks, GitOps PR review. We do not require kubectl access to your production cluster. Critical for banks, telcos, and any regulated buyer who cannot expose infrastructure to a vendor.

Cozystack vs VMware — feature comparison

FAQ

Can we keep our existing hardware?

Yes — in most cases. Cozystack runs on commodity x86. The standard scenario is to deploy Cozystack on a new pod of servers, migrate workloads off VMware, then repurpose the freed VMware hardware into Cozystack as licenses lapse.

How long is a typical migration?

For a 100-1000 VM estate, 8–18 months elapsed from assessment to decommission. Small, simple estates (well under 100 VMs, flat networking, no vCD) land at the short end; vCD- or NSX-heavy regulated estates at the long end, run in cohorts. The driver is rarely raw migration speed — it’s regression testing and parallel-run windows agreed with application owners.

Do you support Windows VMs?

Yes. KubeVirt runs Windows. We have an automated cleanup step that removes VMware Tools and installs the right virtio drivers before first boot on KubeVirt. Activation handling depends on your Windows licensing model — discussed during assessment.

What happens to our existing VMware operational skills?

The hypervisor concepts (VMs, snapshots, templates, networking) carry over. The control-plane shifts from vCenter to Kubernetes — for most teams this is a 4–8 week ramp with the right training and runbooks. Ænix runs the training as part of professional services.

What about VMware Cloud Foundation specifically — is the migration different?

VCF migrations are larger (more components, more integrations). The discovery phase covers SDDC Manager, Workspace ONE, Aria, NSX-T overlays, and any custom service definitions. Ænix has run VCF migrations end-to-end.

What if we use vCloud Director for our customers?

vCD migration is the most common path for service providers. Tenant model maps to Cozystack Tenant CRD, service catalog maps to ApplicationDefinition, billing maps to the WHMCS integration or Cozystack Dashboard. We’ve shipped this for several providers — happy to share architecture in an NDA call.

Is GPU live migration supported?

No — industry-wide limitation, not Cozystack-specific. VMware vGPU live migration has known caveats too. For inference workloads we recommend designing for stateless restart rather than relying on GPU live migration.