Introduction
On April 10, 2025, Broadcom quietly raised the bar on VMware licensing: every VMware product—from vSphere Foundation to VMware Cloud Foundation—now carries a 72-core minimum purchase per order, per product. The familiar 16-core-per-CPU rule still applies, meaning you pay whichever total is higher. For organizations running lightweight or edge workloads, this shift can translate into an immediate increase of up to 350% in software spend. As Chief Sales Officer at Cybele Software, I’ve seen firsthand how this “flat-tax” approach catches many teams off-guard. But with proactive planning, strategic consolidation, and the right abstraction tools, you can not only survive the licensing shock—you can turn it into an opportunity for infrastructure modernization.
What Changed on April 10, 2025?
Before the update, VMware’s only licensing floor was 16 cores per socket, ensuring even small servers paid for at least 16 cores. As of April 10, the new rule enforces:- Per-CPU minimum: still 16 cores per socket
- Per-product minimum: now 72 cores per order, per product — counted across every host on that order, not per host
Example: A single host with two 10-core CPUs (20 cores total), licensed on its own order
- Old license fee: 16 cores × 2 sockets = 32 cores
- New license fee: 72 cores (you “shelve” 52 unused cores)
One caveat on the rollout: this change reached customers through partner and distributor notices rather than a formal announcement, applied in the Americas and APJ while EMEA continued under the 16-core rule, and Broadcom later told press that it had not announced a price change. Confirm the terms that apply to your region and contract with your reseller before you budget.
Why Broadcom Drew the 72-Core Line
Analysts widely agree that Broadcom’s motives include:
- Elevating the entry fee
By raising the minimum, smaller customers face a higher “gate” to adopt VMware, shifting attention toward enterprise accounts. - Promoting bundled products
A 72-core minimum makes offerings like VMware Cloud Foundation more cost-effective per core. - Simplifying SKU management
Fewer SKUs and standardized minimums streamline sales and renewals for Broadcom’s teams.
While this change simplifies licensing on paper, it forces organizations to rethink capacity planning and license management strategies.
Real-World Cost Impact
| Deployment | Old Cores Billed | New Cores Billed | Cost Increase |
|---|---|---|---|
| 1U edge box (8-core) | 16 | 72 | +350% |
| Single 2×10-core host (20 cores) | 32 | 72 | +125% |
| SMB 3-node cluster (2×8-core per host, one order) | 96 | 96 | 0% |
| Dense host (2×48-core) | 96 | 96 | 0% |
How the minimum is applied: the 72 cores are a minimum purchase quantity per order, per product—not a charge levied on each host. Every host covered by the same product order counts toward that total, which is why a cluster already at 72 cores or more sees no increase. What you cannot do is pool cores across different products: 40 cores of VVF plus 32 of VCF does not clear the floor—each product needs its own 72.
Without intervention, your licensing budget could balloon overnight—making core-first hardware decisions and license audits more critical than ever.
Five Proven Cost-Control Tactics
- Consolidate onto high-core servers
Deploy servers with 32–64 cores per socket so each host meets or exceeds the 72-core threshold with fewer licenses. - Collapse redundant product instances
Share vCenter or VMware Cloud Foundation domains across workloads to avoid multiple 72-core minimums. - Institute monthly license audits
Identify idle clusters, stray test environments, and underutilized hosts; power them down or reassign licenses. - Right-size hardware refreshes
When replacing gear, favor CPUs with higher core counts and long-term ROI under the new rules. - Pilot hypervisor alternatives
Explore Microsoft Hyper-V, KVM/Proxmox, or Nutanix AHV to gain negotiation leverage and diversify your virtualization strategy.
These measures not only curb immediate cost spikes but also lay the groundwork for a more efficient, multicloud-ready infrastructure.
Exploring Hypervisor Alternatives
When budgets tighten, alternative platforms can be powerful negotiation tools:
- Microsoft Hyper-V
Included with Windows Server Datacenter—no extra hypervisor licensing required and seamless Active Directory integration. - Proxmox
Open-source and license-free. A steeper learning curve, yes, but unmatched flexibility and a vibrant community. - Public-Cloud Compute
Shifting suitable VMs to Oracle Cloud (OCI), AWS EC2, Azure VMs, or Google Compute can eliminate on-prem core licensing—though it requires additional cloud optimization work.
Even if you remain primarily on VMware, running small pilots on these platforms gives you critical data points to negotiate better renewals.
Thinfinity Workspace: Decouple Access from Licensing
An effective long-term strategy is to separate application access from hypervisor licensing. That’s where Thinfinity Workspace shines:| Component | Benefit Under 72-Core Rule |
|---|---|
| Thinfinity Workspace | Browser-based portal for Windows, web, and SaaS apps—consistent UX regardless of underlying hypervisor or cloud platform, decoupling user access from core licensing costs. |
| Thinfinity Cloud Manager | Unified control-plane to provision, scale, and cost-track workloads across. |
| Public Clouds: AWS EC2, Azure VMs, Google Compute Engine, OCI Compute, IONOS Cloud | On-Prem Hypervisors: VMware vSphere & VMware Cloud Foundation, Microsoft Hyper-V, Proxmox VE. |
90-Day Action Plan
- Audit & model your current core counts against the new 72-core minimum.
- Consolidate low-core hosts onto denser hardware.
- Stand up a Thinfinity Workspace PoC spanning VMware and an alternative hypervisor.
- Refresh hardware on a core-per-dollar basis where ROI is under 18 months.
- Negotiate renewals armed with pilot insights and alternative platform data.
Implementing this plan will stabilize licensing costs and set you up for more agile, secure operations.
Conclusion
The VMware licensing shift to a 72-core minimum poses a significant challenge—but it also creates a catalyst for infrastructure optimization. By combining consolidation strategies, exploring Windows VDI on Oracle Cloud alternatives, and strengthening defenses through a VDI cybersecurity strategy for CISOs, organizations can both control costs and modernize their virtualization estate. Leveraging an abstraction layer like Thinfinity Workspace enables seamless migration paths while aligning with secure, cloud-ready architectures.
2 Comments
Hi, I think you might have misunderstood what the 72 core limit applies to. It’s per product or per contract, not per host.
So assuming all licenses were bought under a single contract, your SMB 3-node cluster example is wrong. It would not be 216 cores billed, it would still be 72. So 0% increase.
Hi, and thanks for the correction — you’re right.
The 72 cores are a minimum purchase per order, per product, not a per-host
charge. Every host on the same order counts toward that total, so a 3-node
cluster already at 72+ cores is billed at its real core count. Our “216 cores,
+200%” row was wrong, and the intro’s “per license instance” wording is what
caused it.
I’ve fixed the article.
One thing worth adding: cores can’t be pooled across products either — 40 cores
of VVF plus 32 of VCF doesn’t clear it, each product needs its own 72.
Appreciate you flagging it.