Broadcom VMware Licensing Changes Explained:
The Biggest Disruption in Virtualisation in 20 Years

What Broadcom Actually Did to VMware

When Broadcom completed its $61 billion acquisition of VMware in late 2023, it moved fast. Within months, the company had dismantled VMware's entire commercial model and replaced it with something unrecognizable to customers who had been buying VMware products for the past two decades.

The changes are not incremental. They are structural. Broadcom ended the sale of perpetual licenses, which means you can no longer buy a VMware license and own it outright. Every new purchase and every renewal is now a subscription. It collapsed VMware's product catalog from over 160 offerings into two primary bundles: VMware Cloud Foundation (VCF) for enterprise and vSphere Foundation (VVF) for mid-market. It replaced per-socket licensing with per-core licensing, imposed a minimum purchase of 72 cores per order, introduced a 20% late-renewal penalty, reduced the authorized reseller channel, and cut VMware's support and account management staff dramatically.

The combined effect of these changes has produced cost increases that range from 3x for the most favorably positioned large enterprises to 12x or more for mid-market and education customers. A large UK university reported its annual VMware renewal jumping from roughly £40,000 to £500,000. Forrester Research documented a client reporting a 500% increase after mapping existing usage to Broadcom's new packaging. These are not outliers. They are the pattern.

Broadcom's stated objective is to grow VMware's revenue from $4.7 billion to $8.5 billion within three years. That $3.8 billion gap has to come from somewhere. It is coming from you.

The End of Perpetual Licenses: Why This Matters More Than the Price Increase

The shift from perpetual to subscription licensing is the most consequential change, and it is often overshadowed by the price-increase headlines. Price increases are painful but negotiable. The elimination of perpetual licenses changes the fundamental power dynamic between Broadcom and its customers.

Under perpetual licensing, you owned the software. You could run it indefinitely. Support was optional. If the vendor raised prices unreasonably, you could continue using the product without support while you planned a migration. That optionality was leverage. It meant the vendor needed you to keep paying more than you needed them to keep selling.

Under subscription licensing, you rent the software. If you stop paying, you lose the right to use it. Your production workloads stop. There is no grace period, no fallback to an unsupported but functional deployment. The vendor has structural leverage because the cost of non-renewal is not "we lose support." It is "our virtual machines go dark."

For customers who still hold active perpetual VMware licenses, this creates a critical decision point. Those licenses remain valid. You own them. But Broadcom will not sell you new support contracts for them. When your current support agreement expires, your choices are: migrate to Broadcom's subscription model, engage a third-party support provider, or run unsupported. Each option has real trade-offs that depend on your timeline and alternatives. Understanding those trade-offs is essential before your support contract expires.

The Bundling Trap: VCF, VVF, and the Death of A La Carte

VMware's old model let you buy exactly what you needed. vSphere for virtualisation. vSAN for storage. NSX for networking. Aria for monitoring. Each had its own SKU, its own pricing, and its own license metric. If you only needed a hypervisor, you paid for a hypervisor.

Broadcom replaced this with two bundles. VMware Cloud Foundation (VCF) is the enterprise offering. It includes vSphere, vSAN, NSX, and the Aria Suite in a single package. It is a full-stack hyperconverged infrastructure solution designed for large private cloud deployments. The functionality is comprehensive. The price is comprehensive too. vSphere Foundation (VVF) is positioned for mid-market. It includes vSphere, Tanzu (Kubernetes), and Aria Operations, with vSAN available as a per-TB subscription add-on. There are also two standalone options: vSphere Standard and Essentials Plus, but these cover only basic virtualisation without the management and networking capabilities most enterprises require.

The problem is straightforward. Most VMware customers were using two or three products. Now they are paying for six or seven. If you run vSphere and vSAN but have no use for NSX, you still pay for NSX inside VCF. If you have your own monitoring stack and do not need Aria, you still pay for Aria. The bundle includes capabilities that many customers neither want nor will deploy, but there is no opt-out mechanism and no corresponding price reduction.

NSX deserves specific attention. Broadcom has stopped selling standalone NSX licenses entirely. The networking and security capabilities are being repackaged into a "VMware Firewall" solution with Advanced Threat Protection. For organizations that built their network virtualisation strategy around NSX as a standalone product, this forced bundling into VCF represents both a cost increase and a loss of architectural flexibility.

The Aria Suite tells a similar story. Broadcom put Aria SaaS into End-of-Availability in December 2023 and placed the on-premises suite into maintenance mode, meaning no new feature development. You are paying for a monitoring platform inside the bundle that Broadcom has effectively stopped investing in. That is a meaningful consideration for anyone evaluating VCF's total value proposition.

Per-Core Licensing and the 72-Core Minimum: Where the Math Gets Ugly

VMware historically licensed by the CPU socket. One socket, one license. It did not matter whether that socket contained 8 cores or 64 cores. The price was the same. This model was simple, predictable, and generally favorable to customers running modern, high-core-count processors.

Broadcom replaced this with per-core licensing. Every physical core in every CPU requires a license. There is a floor of 16 cores counted per CPU regardless of actual core count, so an 8-core processor is billed as 16 cores. And starting in 2025, Broadcom imposed a minimum purchase of 72 cores per order.

The 72-core minimum is where the economics become punitive for smaller environments. Consider a customer running a two-server cluster with two 16-core CPUs. That is 32 physical cores. Under the old per-socket model, they needed 2 licenses. Under per-core licensing, they need 32 core licenses. Under the 72-core minimum, they must purchase 72 core licenses, paying for more than double their actual core count. The smaller the environment, the worse the ratio becomes. A site with two 6-core CPUs (12 cores) must still buy 72 cores of licensing.

For large enterprises with dense, high-core-count infrastructure, the per-core model also increases costs substantially. A server with two 64-core AMD EPYC processors requires 128 core licenses where it previously required 2 socket licenses. The per-core price is lower than the per-socket price, but not 64x lower. The net effect is a significant increase for any environment running modern processors.

Late-Renewal Penalties and Other Commercial Pressure Points

Broadcom introduced a 20% late-renewal penalty applied to the first-year subscription cost if you renew after your anniversary date. This is a significant departure from VMware's historically flexible approach to renewal timing. Under the old model, customers routinely negotiated renewal terms after the technical expiration date without penalty. Broadcom has closed that window.

The penalty creates an artificial deadline that compresses negotiation timelines and favors Broadcom. If you are six months from renewal and still evaluating alternatives or negotiating terms, the 20% penalty looming on your anniversary date creates pressure to accept whatever terms are on the table rather than risk the surcharge. This is by design.

The counter-strategy is timing. Start renewal discussions 12 to 18 months before expiration. Build your alternative analysis, competitive proposals, and internal migration assessments well in advance so that when the 6-month window arrives, you are negotiating from a position of preparation rather than scrambling to avoid a penalty. If Broadcom knows you have a BMC, Nutanix, or Hyper-V migration plan ready to execute, the late-renewal penalty becomes irrelevant because both parties understand you have a real alternative.

Broadcom has also reduced the number of authorized VMware resellers. Fewer channel partners means less competition on pricing and less leverage for customers who historically played resellers against each other to negotiate better terms. If your preferred partner lost VMware authorization, you may be dealing with an unfamiliar channel with less incentive to fight for your discount.

What Happened to the Rest of the Portfolio

The VCF/VVF consolidation eliminated or absorbed dozens of products. A few deserve specific attention because their fates affect customers in distinct ways.

VMware Horizon (VDI) was sold to KKR and spun out as an independent company called Omnissa. If you are a Horizon customer, you are no longer dealing with VMware or Broadcom. You are dealing with a private-equity-backed startup that inherited a mature VDI product. Licensing, support, and roadmap decisions are now entirely separate from the rest of the VMware stack. This separation may ultimately benefit Horizon customers by giving the product focused investment, but it also means your VDI licensing is no longer negotiable as part of a broader VMware deal.

vCloud Suite and other legacy bundles are discontinued. Customers on these bundles are being migrated to VCF or VVF, typically at higher cost. If you held a vCloud Suite license that included multiple products at a favorable bundled rate, expect that pricing to disappear at renewal.

Bring-Your-Own-Subscription (BYOS) is a genuinely positive change. Broadcom now allows customers to port VMware subscriptions between on-premises and approved cloud environments. For organizations running hybrid strategies, this flexibility has real value and can simplify licensing across multi-environment deployments.

Third-Party Support: Buying Time Without Buying In

For organizations holding perpetual VMware licenses, third-party support providers represent a genuine strategic option. Companies like Rimini Street, Spinnaker Support, and Origina offer break-fix support, technical assistance, and security advisory services for VMware products that Broadcom will no longer support under perpetual agreements.

The economics are usually compelling. Third-party support typically costs 50-70% less than Broadcom's subscription pricing. For an organization facing a 5x cost increase at renewal, switching to third-party support while planning a longer-term migration can save millions over a 2-3 year transition window.

The limitations are real and should be understood clearly. Third-party support does not include new feature releases, major version upgrades, or VMware cloud services integration. You remain on your current software version for the duration. There is no product roadmap. You are running a frozen deployment with someone maintaining it.

That is exactly the right answer for many organizations. If you are planning to migrate 60% of your VMware workloads to public cloud over the next three years, you do not need a VMware product roadmap. You need your current infrastructure to remain stable, secure, and supported while the migration executes. Third-party support delivers precisely that at a fraction of the subscription cost.

The key is treating third-party support as a bridge, not a destination. It buys you 1-3 years of breathing room to evaluate alternatives, plan migrations, and negotiate from strength rather than urgency. Most organizations using it well are simultaneously executing their next move.

The Alternative Landscape: What Actually Works

Broadcom's pricing changes have made VMware alternatives viable for workloads and environments where switching was previously not worth the effort. The question is no longer "is it cheaper to stay?" For many customers, the answer to that question is already no. The question is "what can I realistically migrate to, and how long will it take?"

Microsoft Hyper-V is the most common first move. It is included with Windows Server licensing that many enterprises already own. For Windows-centric workloads, the migration is relatively straightforward. Hyper-V lacks some of VMware's advanced features around distributed resource scheduling and network virtualisation, but for basic server virtualisation, it is functional and effectively free if you already pay for Windows Server Datacenter. The limitation is that Microsoft has signaled reduced investment in Hyper-V as it pushes customers toward Azure, so the long-term product trajectory is uncertain.

Nutanix AHV is the strongest commercial alternative for organizations that want a full hyperconverged stack. AHV is included with Nutanix's platform at no additional hypervisor cost. Nutanix has aggressively targeted VMware refugees since the Broadcom acquisition, offering migration tools and competitive pricing. The trade-off is that you are moving from one proprietary platform to another, and Nutanix's pricing, while currently competitive, is not immune to future increases once you are committed.

Proxmox VE has emerged as a serious option for mid-market and cost-sensitive environments. It is open-source, based on KVM and LXC, and offers a web-based management interface that handles most common virtualisation tasks. Enterprise support subscriptions are available at a fraction of VMware's cost. The limitation is maturity: Proxmox lacks the ecosystem depth, enterprise tooling, and third-party integrations that VMware built over 20 years. For straightforward virtualisation workloads, it works well. For complex environments with heavy automation, DR orchestration, or network virtualisation requirements, the gaps become apparent.

Public cloud migration is the right answer for workloads that should not be on-premises in the first place. Many VMware environments include workloads that would run more efficiently and cost-effectively on AWS, Azure, or Google Cloud. The Broadcom price shock is a useful catalyst for the cloud-readiness assessment that many organizations have been deferring. The caution is that not all workloads are cloud-suitable, and a rushed migration driven by licensing panic rather than architectural planning can create new cost and performance problems.

Kubernetes and container platforms are relevant for new application deployments but are not a lift-and-shift replacement for existing VM-based workloads. If you are building new applications, designing for containers from the start can eliminate the need for VMware entirely. For existing workloads, containerisation is a re-architecture project, not a migration.

How to Negotiate With Broadcom in This Environment

Audit your install base before anything else. Know exactly how many cores you are running across every host. Know which products you are actually using versus what is installed. Know your support contract expiration dates to the day. Broadcom has increased its focus on license compliance, and any over-deployment gives them leverage to impose punitive true-up pricing. A clean compliance position is the foundation of any negotiation.

Model the full financial picture. Do not compare Broadcom's subscription quote to your old VMware maintenance cost in isolation. Model total cost of ownership over 3-5 years under three scenarios: stay with Broadcom at quoted terms, stay with Broadcom at negotiated terms, and migrate to an alternative. Include migration costs, training, productivity loss, and ongoing operational differences. This model gives you and your CFO the data to make a rational decision rather than an emotional one.

Build credible alternatives before you negotiate. Get written proposals from Nutanix, run a Hyper-V proof of concept, engage a third-party support provider for a formal quote. The specificity matters. Broadcom's negotiators have heard "we are looking at alternatives" from every customer. They have not heard "we have a signed Nutanix proposal, a completed Hyper-V POC covering 40% of our workloads, and a Rimini Street contract ready to execute." The second conversation produces different results.

Push for multi-year pricing locks. If you are staying with VMware, negotiate a 3-year or 5-year deal that locks in per-core rates and prevents annual increases above 3%. Broadcom's standard terms allow significant annual uplift. A multi-year commitment is your leverage to cap that exposure. Include flex-down provisions so that if you reduce core counts through consolidation or migration, your costs follow.

Do not accept the first offer. Broadcom's initial quotes are routinely 2-3x higher than the final negotiated price for customers who push back with data, alternatives, and patience. The organizations paying 12x increases are the ones who accepted the first proposal under deadline pressure. The organizations paying 3-4x are the ones who negotiated for months with credible alternatives on the table.

The Bottom Line

Broadcom's VMware licensing changes represent the most significant commercial disruption in the virtualisation market since VMware itself created the category. The end of perpetual licenses, forced bundling, per-core pricing with punitive minimums, and reduced support all point in one direction: higher costs and stronger vendor lock-in.

The organizations that will navigate this best are the ones treating it as a structural change that requires a structural response. That means SAM optimization, competitive evaluation, phased migration planning, third-party support as a bridge strategy, and disciplined negotiation backed by real data and real alternatives.

The organizations that will fare worst are the ones treating it as a renewal event. Showing up at the table 90 days before expiration with no alternatives, no migration plan, and no SAM data is the scenario Broadcom has designed its entire commercial model around. The 20% late-renewal penalty, the compressed reseller channel, the reduced account management, all of it is built to push customers toward exactly that position.

Do not give them that advantage. Start now. Build your data. Evaluate your options. And negotiate from strength.