Directory › Guides › VMware alternatives after Broadcom

VMware Alternatives After Broadcom (2026): A Buyer's Guide for IT Leaders

Last reviewed: October 23, 2026 · Published October 23, 2026 · By RackGuide

Since Broadcom closed its acquisition of VMware, almost every vSphere shop has had the same conversation at renewal time: stay on VMware under the new subscription model, or move to something else? This guide lays out what actually changed, the five alternatives mid-size IT teams shortlist most often (Nutanix, Microsoft Hyper-V and Azure Local, Proxmox VE, Scale Computing, and XCP-ng), how each one handles migration off ESXi, and when staying on VMware Cloud Foundation is the right call.

Every product and licensing fact below links to the vendor's own site or documentation. There are no price quotes here: most of these platforms are sold through partners, and list prices change, so get current numbers from your reseller and model them against your own core counts.

What changed after Broadcom

Broadcom completed its acquisition of VMware on November 22, 2023. Within weeks it announced the changes that are driving today's evaluations:

• Perpetual licenses ended. Broadcom's announcement says it stopped selling perpetual licenses and Support and Subscription (SnS) renewals for perpetual offerings, with all VMware products moving to subscription or term licenses. You can keep running perpetual licenses you already own.
• The portfolio collapsed into two main offers. VMware's January 2024 update names VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF) as the two new offers, with many former standalone products available only inside them. The same update kept vSphere Standard and vSphere Essentials Plus subscriptions for lighter needs; confirm with your reseller which editions are still sold when you renew.
• Licensing is per core with a floor. Broadcom's core-counting KB says VCF and VVF are licensed on every physical core, with a minimum of 16 cores per CPU, so a host with two 8-core CPUs is billed as 32 cores.
• Running without support has limits. Broadcom's KB on perpetual licenses after SnS expires says hosts and VMs keep running, but you lose access to patches, security updates, and new versions, and you can't open support cases.
• VCF 9 requires subscription. Broadcom's VCF 9.1 FAQ says customers with perpetual licenses must switch to subscription licenses before upgrading to VCF 9.

The practical effect: if you were on perpetual vSphere with SnS, your next renewal is a subscription decision, priced on cores. That's the moment to compare alternatives, even if you end up staying.

The short answer

• Stay on VMware (VCF or VVF) if you rely on vSAN, NSX, or deep third-party integrations, have a large estate, and the subscription quote fits your budget. Migration has real cost and risk too.
• Pick Nutanix if you want a full hyperconverged platform with enterprise support and a polished migration tool, and you're open to buying or refreshing hardware.
• Pick Hyper-V or Azure Local if you're a Microsoft shop already licensing Windows Server Datacenter, or you want on-prem VMs managed from Azure.
• Pick Proxmox VE if your team is comfortable with Linux and wants an open-source platform with per-socket support subscriptions and a built-in ESXi import wizard.
• Pick Scale Computing if you're a small team or have many edge sites and want the simplest possible appliance-style platform.
• Pick XCP-ng if you want open source with a vCenter-like central console (Xen Orchestra) and integrated backup.

Side-by-side comparison

Option 0: stay on VMware (VCF or VVF)

Staying is a legitimate outcome, and you should price it properly before you price anything else. Per Broadcom's VCF 9.1 FAQ, VCF includes vSphere, vSAN, NSX, vSphere Kubernetes Service, VCF Operations, VCF Automation, and HCX, with add-ons such as advanced security, load balancing, and VMware Advanced Cyber Compliance sold separately. VVF is the vSphere-focused offer for traditional data center consolidation.

Things to check in your quote:

• Core math. Run Broadcom's counting method from the core-counting KB across every host. Older low-core CPUs get rounded up to 16 cores each, so consolidating onto fewer, denser hosts can change the number.
• vSAN capacity. The same KB explains how vSAN capacity is entitled with VCF and VVF and when you need to buy more TiBs.
• Roadmap items you depend on. For example, the VCF 9.1 FAQ says vVols are deprecated starting with VCF 9.0 and will be removed in a future release. If your arrays rely on vVols, that's a project either way.

Nutanix Cloud Infrastructure (AHV)

Nutanix Cloud Infrastructure is a hyperconverged stack: compute, storage, networking, and the AHV hypervisor, managed with Prism. It's the alternative that most closely matches a full vSphere-plus-vSAN environment in scope.

• Licensing. Nutanix's software options page says NCI licenses are applied per physical CPU core, are portable across hardware platforms, and come in 1 to 5-year terms, in Starter, Pro, and Ultimate editions. Starter tops out at 12 nodes per cluster. Nutanix also sells per-VM (NCI-Edge) and per-user (NCI-VDI) options for small edge clusters and VDI.
• Hypervisor choice. The same page describes an NCI Data option for running Nutanix storage under another hypervisor, which lets some teams move storage first and the hypervisor later.
• Migration. Nutanix Move migrates VMs from ESXi (and Hyper-V and public cloud) to AHV with test migrations and controlled cutover, and Nutanix says it's included with all Nutanix software editions. Check the Move release notes for supported ESXi and vCenter versions before you plan.

Watch for: hardware. NCI runs on supported platforms, so a move to Nutanix is often tied to a hardware refresh. That can be a feature if your hosts are due anyway.

Microsoft Hyper-V and Azure Local

Microsoft gives you two paths. Hyper-V is the hypervisor built into Windows Server, clustered with Windows Server Failover Clustering. Azure Local is Microsoft's hyperconverged platform, renamed from Azure Stack HCI effective November 19, 2024, which runs on validated hardware and uses Azure Arc as its control plane.

• Hyper-V licensing. Microsoft's Windows Server 2025 licensing guide says you license every physical core, with minimums of 8 core licenses per processor and 16 per server. Datacenter edition then covers unlimited Windows Server VMs on that host; Standard covers two. If you already own Datacenter with Software Assurance for your Windows guests, the hypervisor is effectively already paid for.
• Azure Local licensing. The Azure Local pricing page describes a monthly host service fee per physical core, billed through your Azure subscription after a 60-day free trial. Windows guests are licensed separately, through Azure Hybrid Benefit or a Windows Server subscription, and Microsoft says Azure Hybrid Benefit can waive the host fee for eligible hyperconverged deployments.
• Migration to Hyper-V. The VM Conversion extension for Windows Admin Center migrates VMs from vCenter 6.x to 8.x to Hyper-V, using an initial sync and Changed Block Tracking for a short final cutover, up to 10 VMs per batch. It's free, but it's still in preview, and Microsoft notes Linux guests need Hyper-V drivers installed before migration.
• Migration to Azure Local. Azure Migrate supports VMware to Azure Local (Azure Local 2503 and later) with source and target appliances. VM data stays on-premises; only metadata and replication state go to Azure.

Watch for: Azure Local requires an Azure subscription and cluster registration, which is a governance conversation as much as a technical one.

Proxmox VE

Proxmox VE is an open-source platform built on KVM virtual machines and LXC containers, with built-in clustering, high availability, Ceph and ZFS storage, software-defined networking, and a web UI.

• Licensing. Proxmox's pricing page sells subscriptions per occupied CPU socket, with no per-core pricing and every feature available at every level. Plans differ by support tickets and response time, and all nodes in a cluster must use the same level. Subscriptions also give access to the stable Enterprise Repository.
• Migration. The Migrate to Proxmox VE wiki documents a built-in ESXi import wizard: add the ESXi host as an import storage, pick a VM, map disks and networks, and import. Proxmox says it was tested with ESXi 6.5 to 8.0. It doesn't work for vSAN-backed disks or encrypted disks, VMs with snapshots import more slowly, and importing through vCenter is much slower than importing from the host directly.

Watch for: operational skills. Proxmox rewards teams that are comfortable on the Linux command line, especially when running Ceph. Budget time for monitoring, backup (Proxmox Backup Server or your existing tool), and runbooks.

Scale Computing SC//HyperCore

SC//HyperCore is a lightweight, all-in-one platform focused on simplicity, high availability, and self-healing. It's aimed at small IT teams and distributed sites where there's nobody on-site to manage infrastructure.

• Migration. Scale's SC//Migrate data sheet describes backing up VMware, Hyper-V, or physical workloads and converting them to VMs on the target cluster, with agentless migration for VMware and Hyper-V and agent-based options for many other sources. SC//Migrate is licensed per host for a 90-day term, so plan the migration window before you buy it.
• Licensing. Scale doesn't publish list prices; work with a partner for a quote.

Watch for: scale and ecosystem. Confirm that your backup, monitoring, and DR tools support HyperCore, and size the clusters for your largest workloads, not just your average ones.

XCP-ng with Xen Orchestra

XCP-ng is an open-source, Xen-based virtualization platform backed by Vates. Its documentation describes it as a turnkey appliance you install from an ISO and manage centrally with Xen Orchestra, which also provides agentless VM backup. Architecturally, it's the option that feels closest to ESXi plus vCenter.

• Migration. Xen Orchestra's VMware V2V guide covers importing VMs from ESXi 6.x, 7.x, and 8.x, directly or through vCenter. It's a warm migration: most of the data copies while the source VM keeps running, then a final delta sync happens after the VM is stopped. As of the current docs, the import runs from the XO 5 interface, and RDMs and independent disks aren't supported.
• Licensing. XCP-ng is free and open source; Vates sells commercial support for the stack.

Watch for: Xen-specific guest drivers. Vates recommends uninstalling VMware Tools and, for Linux guests, preparing drivers before migrating so the VM boots cleanly.

Migration considerations

Whichever platform you pick, the migration plan matters more than the hypervisor. A checklist that works across all of them:

1. Inventory and right-size first. Export every VM with its CPU, memory, disk, network, OS, and owner. Retire what nobody claims. Fewer VMs means fewer cores to license on any platform.
2. Find the blockers. Flag vSAN-backed disks, encrypted VMs, RDMs, independent disks, vTPM, and long snapshot chains. Every vendor tool above has limits on at least one of these.
3. Map the dependencies on VMware itself. Backup software, monitoring, DR orchestration, VDI, automation scripts using PowerCLI, and any appliance shipped as an OVA all need a plan on the new platform.
4. Plan guest drivers and tools. Remove VMware Tools and install the target platform's drivers (VirtIO, Hyper-V integration, or Xen tools). Note static IPs, since the new virtual NIC usually shows up as new hardware.
5. Pilot with non-critical VMs. Use the vendor tool's test-migration mode where it exists, measure throughput, and time the cutover.
6. Migrate in waves with a rollback path. Group VMs by application, keep the source VM powered off but intact until the application owner signs off, and don't decommission hosts until the last wave is stable.
7. Time it against your renewal. Broadcom's KB says perpetual hosts keep running after SnS expires, but without patches. If migration will run past your support end date, decide in advance how you'll handle security fixes in the gap.

Which one fits your environment

Building a shortlist? See every platform in the Virtualization & HCI category on RackGuide, and check the Backup & Disaster Recovery and Monitoring & Observability categories to confirm your existing tools support the platform you pick.