Contents
- The VCF price shock: what changed and why
- Alternative 1: Nutanix AHV
- Alternative 2: Microsoft Azure Stack HCI
- Alternative 3: Red Hat OpenShift Virtualisation
- Alternative 4: KVM/Proxmox VE (open-source)
- Alternative 5: Hyperscaler migration (AWS/Azure/GCP)
- If you're staying: how to negotiate VCF
- The decision framework
The VCF Price Shock: What Changed and Why
Overpaying for Broadcom/VMware? We handle Broadcom and VMware contract negotiation on a 25% gainshare basis — you keep 75% of every dollar saved. No retainer. No risk.
Get a free Broadcom/VMware savings estimate →When Broadcom completed its $61 billion acquisition of VMware in November 2023, it immediately restructured VMware's product and pricing strategy. The core changes: VMware's product line was consolidated into VMware Cloud Foundation (VCF) as the primary offering, perpetual licenses were eliminated in favour of subscription-only, and pricing moved from per-CPU socket to per-core. Simultaneously, Broadcom discontinued partner reseller models that had provided enterprise discount channels, forcing direct commercial relationships.
The per-core shift is what drove the price increases enterprises actually felt. Under VMware's old model, a server with two 16-core CPUs was licensed as two CPU sockets. Under VCF, it's licensed as 32 cores. For most enterprise server configurations — which have moved to 32–64 core CPUs since VMware's old pricing was established — this means licence costs increased 4–8x for identical infrastructure.
Broadcom's rationale is straightforward: they acquired VMware to extract maximum value from its dominant market position. VMware runs an estimated 70%+ of enterprise virtualisation workloads. Broadcom's calculation is that the switching costs — technical complexity, retraining, application compatibility — make most enterprises stay even at higher prices. For many enterprises, they're right. But for others, the price increase was large enough to make the switching cost calculation come out differently.
Facing a Broadcom VMware renewal?
Whether you're staying on VCF or evaluating alternatives, we can help. We negotiate Broadcom VMware contracts on a 25% gainshare basis — and we can model the full total cost of ownership for migration scenarios. No obligation, no cost unless we deliver savings.
Explore Broadcom/VMware Negotiation →Alternative 1: Nutanix AHV
Nutanix AHV — Hyper-Converged Infrastructure with Built-In Hypervisor
Nutanix's AHV (Acropolis Hypervisor) is the most frequently deployed VMware alternative among enterprises making deliberate infrastructure switches. Nutanix made AHV free as part of its Nutanix Cloud Infrastructure (NCI) subscription in 2019, removing the licence cost for the hypervisor itself. For enterprises already running Nutanix hardware, the migration path from vSphere to AHV is well-documented and operationally manageable.
Nutanix's pitch is compelling: the HCI stack (compute, storage, networking) is managed through a single Prism interface comparable to vCenter, AHV is included in NCI subscription costs, and Nutanix's Live Migration feature provides VM mobility comparable to vMotion. The commercial model — subscription-based, per-node pricing — is transparent and doesn't have the core-count exposure that makes VCF expensive on modern hardware.
Honest limitations: AHV's ecosystem depth is narrower than vSphere's. Third-party backup, monitoring, and security tools have strong Nutanix integrations but vendor support certification is less universal. Enterprises with VMware-specific software dependencies (VMware NSX for networking, vSAN for storage) face integration work that doesn't have a direct Nutanix equivalent in all cases.
Typical cost outcome: Enterprises migrating from VCF to Nutanix AHV on Nutanix hardware report 30–50% all-in infrastructure cost reductions over three years, including migration costs and training.
Alternative 2: Microsoft Azure Stack HCI
Microsoft Azure Stack HCI — On-Premises Infrastructure with Azure Integration
Azure Stack HCI is Microsoft's hyper-converged infrastructure platform that runs Hyper-V as its hypervisor and is managed through Windows Admin Center and Azure Arc. For enterprises with significant Microsoft Enterprise Agreements and deep Azure investment, Azure Stack HCI offers a compelling cost story: the base platform licence is included in certain Microsoft EA tiers, and Azure Arc integration enables hybrid management across on-premises and Azure environments.
The strategic case for Azure Stack HCI is about more than hypervisor cost: it positions your on-premises infrastructure as an extension of your Azure environment, simplifying management overhead and creating a migration path to Azure that preserves operational consistency. For enterprises that are already moving workloads to Azure or planning to, this on-premises/cloud consistency has real operational value.
Honest limitations: Azure Stack HCI's Hyper-V hypervisor is technically capable but has historically lagged VMware vSphere in features like memory ballooning, NUMA management, and live migration performance at scale. At very large vSphere deployments — 500+ VMs with demanding performance requirements — Azure Stack HCI may require infrastructure overprovisioning to match vSphere performance profiles.
Typical cost outcome: Enterprises already on Microsoft EA with Azure Stack HCI licensing included see near-zero incremental hypervisor cost. Net savings vs. VCF of 40–60% are achievable when Microsoft licensing is already in place.
Alternative 3: Red Hat OpenShift Virtualisation
Red Hat OpenShift Virtualisation — Container-Native VM Management
Red Hat OpenShift Virtualisation (formerly OpenShift CNV) runs VMs inside Kubernetes pods using KVM as the underlying hypervisor. The pitch is architectural transformation: rather than maintaining a separate VM management plane alongside your container platform, OpenShift Virtualisation runs both VMs and containers through a single Kubernetes-based control plane.
This model makes most sense for enterprises that are already invested in OpenShift for container workloads and want to consolidate infrastructure management. It's less compelling for organisations with a primarily traditional VM estate that has no container transformation roadmap, because adopting OpenShift Virtualisation requires Kubernetes operational skills that traditional vSphere teams typically don't have.
Honest limitations: The operational model shift from vCenter-centric VM management to Kubernetes-native management is significant. Enterprises underestimate the retraining cost. OpenShift Virtualisation also adds the Red Hat subscription cost on top of the underlying infrastructure, which can reduce the cost advantage vs. VCF for mid-size deployments.
Typical cost outcome: For enterprises already on Red Hat Enterprise Linux and OpenShift, OpenShift Virtualisation typically adds 15–25% to existing subscription costs while eliminating vSphere licensing entirely — net positive for most deployments above 200 VMs.
Alternative 4: KVM/Proxmox VE (Open-Source)
KVM / Proxmox VE — Open-Source Hypervisor Without Licence Cost
KVM (Kernel-based Virtual Machine) is the Linux kernel hypervisor that underpins virtually every cloud provider's infrastructure — including AWS (Nitro), Google Cloud, and most OpenStack deployments. Proxmox VE is the most widely deployed open-source management layer for KVM, providing a web UI, clustering, live migration, and backup capabilities that make KVM operationally manageable at enterprise scale.
The commercial case is stark: Proxmox VE's subscription for enterprise support costs approximately $1,000–$2,000 per node per year — versus VCF's per-core pricing that can reach $10,000–$20,000 per server for modern high-core-count hardware. For enterprises with large VM estates and in-house Linux expertise, KVM/Proxmox VE eliminates hypervisor licensing cost almost entirely.
Honest limitations: The lack of commercial vendor backing creates genuine risk for enterprises with strict vendor support requirements. Proxmox VE's commercial support is limited compared to VMware, Nutanix, or Microsoft. Hardware vendor certifications are narrower. The management tooling is functional but lacks the ecosystem depth of vCenter — particularly for large-scale automation, advanced networking (equivalent to NSX), and integration with enterprise monitoring platforms.
Typical cost outcome: Enterprises with strong Linux operations teams and permissive support policies achieve 70–85% cost reductions vs. VCF. Total migration cost (training, tooling, validation) typically takes 18–24 months to break even, after which annual savings are substantial.
Alternative 5: Hyperscaler Migration (AWS, Azure, GCP)
Hyperscaler Migration — Eliminating the On-Premises Infrastructure Problem
For some enterprises, the right response to VMware VCF pricing is to question whether on-premises virtualisation infrastructure is still the right architecture — not which hypervisor to replace VMware with. AWS, Azure, and Google Cloud all offer dedicated VMware migration pathways: AWS VMware Cloud on AWS (VMware Cloud on AWS, now also operated under Broadcom/VMware), Azure VMware Solution, and Google Cloud VMware Engine provide vSphere-compatible environments hosted in hyperscaler data centres.
These services are not the cost-saving option — they run vSphere on dedicated cloud hardware and carry both VMware licensing and cloud infrastructure costs. Their value proposition is operational simplicity and capital expenditure elimination, not software cost reduction. However, for enterprises whose primary constraint is CapEx budget rather than OpEx, VMware on a hyperscaler can be commercially rational.
The more aggressive alternative is a genuine "lift and shift" migration to cloud-native infrastructure — migrating VMs to cloud VMs (EC2, Azure VMs, GCE instances), containerising applications on EKS, AKS, or GKE, and eliminating on-premises infrastructure entirely. This is the right long-term answer for many enterprises, but it requires 3–5 years of migration investment and carries significant application compatibility risk for legacy workloads.
Honest limitations: Cloud migration is not a VMware cost-reduction strategy in the short term. For virtualisation-heavy workloads that don't benefit from cloud-native services, cloud infrastructure costs typically exceed on-premises VMware costs — even at VCF prices. The cost savings come from headcount reduction, data centre lease elimination, and hardware refresh avoidance over a 5+ year horizon.
If You're Staying: How to Negotiate VCF
The most important thing to understand about Broadcom VMware negotiations is that the published price list is not the starting point for serious commercial discussions — it's a ceiling. Broadcom's sales team has commercial flexibility, particularly for enterprises with large existing VMware estates, multi-year commitment willingness, and genuine alternative evaluation underway.
The levers that work in VMware VCF negotiation:
- Alternative evaluation credibility: If Broadcom believes you're genuinely evaluating Nutanix or Azure Stack HCI, concessions materialise. You need to demonstrate this — with evaluation timelines, proof of concept results, or documented vendor conversations — not just claim it as a negotiating position.
- Core count cap negotiations: Broadcom will negotiate a per-server core cap for licensing purposes. For servers with 64+ core CPUs, a contractual cap at 48 licensable cores per server can reduce your total licence cost by 25–33%.
- Multi-year commitment: Three-year VCF commitments with upfront payment generate meaningful discounts — typically 20–35% off per-core list pricing. The trade-off is reduced flexibility to migrate away during the commitment period, so migration readiness assessment should precede any multi-year commitment.
- Workload tiering: Negotiate a lower VCF tier for development and test environments. Broadcom offers a VCF Developer tier with reduced functionality and significantly lower per-core pricing. Accurately categorising non-production workloads can reduce your effective licence cost by 15–20%.
- Legacy perpetual licence treatment: If you have existing perpetual VMware licences, their treatment in the VCF transition is negotiable. Push for perpetual licence credit against your VCF subscription cost, even if Broadcom's default position is to treat them as expired.
Further Reading
- Broadcom End-User Computing Transition Guide ↗
- VMware by Broadcom Licensing FAQ ↗
- Gartner Magic Quadrant for Desktop Virtualization ↗
Navigating a VMware VCF negotiation or migration decision?
We work with enterprises on both sides of this decision — negotiating VCF contracts for those staying and modelling total migration costs for those leaving. Our fee is 25% of verified savings. Zero cost if we don't deliver. See how our model works.
Get a Free VMware Assessment →The Decision Framework
The right answer for your organisation depends on four variables that are specific to your situation:
- Your VMware estate size: Migration economics improve significantly above 500 VMs. Below 100 VMs, the migration cost often exceeds the licence savings from alternatives for at least 3–4 years.
- Your existing vendor relationships: If you're a Microsoft EA customer or Red Hat customer, the cost structure of Azure Stack HCI or OpenShift Virtualisation looks very different than for an organisation starting without those relationships.
- Your operations team's Linux expertise: Open-source alternatives require Linux operational maturity that many traditional vSphere teams don't have. Be honest about this — migration cost estimates that assume existing Linux skills in a Windows-dominant operations team are systematically understated.
- Your tolerance for migration risk: Every alternative involves application compatibility testing, potential downtime risk during migration, and a period of parallel operation. Enterprises with mature change management processes absorb this more comfortably than those with limited change risk appetite.
Whatever decision you reach, don't sign your next VMware VCF contract — or commit to a migration investment — without an independent commercial review. The Broadcom VMware negotiation and the total cost of migration both have more flexibility than the initial numbers suggest, and the right analysis changes the decision calculus for most enterprises we work with.
If you're currently evaluating this decision or approaching a Broadcom renewal, contact our team for a confidential assessment. We'll model both paths — negotiate and stay, or migrate and save — and quantify which creates better long-term value for your specific infrastructure estate.