Broadcom's VMware licensing changes and what each one costs you.
Broadcom collapsed 168-plus VMware point products into two bundles, moved every customer to per-core subscriptions with a 16-core-per-CPU minimum, and ended perpetual license sales. This note maps each change to its cost impact, isolates the traps that inflate renewals, and sets out the levers — renewal defence, consolidation, and a credible exit — that pull the bill back down.
Almost nothing about how you were licensed before the acquisition survives unchanged. The gaps between the old and new models — bundling, the per-core minimum, and the subscription renewal cliff — are exactly where cost balloons. None of it is reversible, but all of it is plannable: audit real cores, document actual usage, and price the exit before you renew.
01 Key findings
Three structural changes arrived together, not in stages. Two bundles, per-core subscriptions, and the end of perpetual sales are all expressions of one strategy — simplify to the highest-margin core and convert one-time revenue into recurring revenue — so none of them is a temporary policy likely to reverse.
Bundling, not list price, is the main cost mechanic. You no longer pay for the products you selected; you pay for a suite assembled for the average customer. Cheap, narrow editions for test or non-critical workloads are gone, so those workloads now sit in the same per-core bundle as production.
The 16-core-per-CPU minimum penalises lightly populated sockets. A host with two 10-core CPUs is billed as 32 cores rather than 20 — a 60% overcharge relative to physical cores. Consolidation onto fewer, denser hosts is now a direct financial lever, not just an engineering nicety.
Standing still has a real, compounding cost. Support is bundled into the subscription; perpetual licences you own stop receiving patches when your existing support lapses. Running unsupported virtualization is a security exposure, not a saving.
Readiness, not the changes, is what you control. A buyer who starts six months out can consolidate, document usage, and price a board-approved exit before the quote lands — and negotiate from a position rather than absorb whatever is offered.
02 Old model vs new model
The table contrasts the old and new models on the dimensions that drive cost. The shift from per-socket to per-core with a 16-core floor is the change most likely to surprise teams. It extends our VMware by Broadcom licensing guide and the Broadcom changes analysis.
| Dimension | Old VMware model | New Broadcom model |
|---|---|---|
| License type | Perpetual plus annual support | Annual subscription only |
| Metric | Per CPU socket | Per physical core |
| Minimum | None | 16 cores per CPU |
| Product structure | 168-plus point products | Two main bundles |
| Renewal | Support renewal only | Full subscription renewal |
Perpetual licences you own do not entitle you to ongoing updates once your support contract lapses. Running unsupported perpetual versions is a security and compliance risk, not a cost saving, and Broadcom has tightened enforcement. Decide deliberately between subscribing, migrating, or accepting unsupported status — do not drift into the last option by inattention, because the exposure compounds quietly until an incident makes it visible. See our VMware perpetual end analysis.
03 The two bundles
The sprawling catalog collapsed into two principal SKUs with a small set of add-ons. Customers who licensed a handful of specific products now buy a bundle that includes capabilities they may never use — the mechanic behind much of the cost increase.
- vSphere, vSAN, NSX and Aria management
- Full software-defined datacentre stack
- Highest per-core rate of the two bundles
- Pay for the whole suite, not what you selected
- Overkill for narrow vSphere-only workloads
- vSphere plus a bundled management tier
- Lower entry point than VCF
- Still per-core, still 16-core minimum
- No cheap standalone edition beneath it
- Test/dev now priced like production
- A small set of discrete add-on SKUs
- Layer on top of VVF or VCF
- Scoped to specific capabilities
- Stacking add-ons can approach the next bundle's price
- Narrow point products no longer sold standalone
04 The 16-core minimum in practice
The per-core minimum is the change that most often produces an unexpected number. Each CPU is licensed for at least 16 cores regardless of how many it physically has, so lightly populated sockets pay a penalty every year until you address it. Licensed cores versus physical cores, by host configuration:
A server with two 8-core CPUs is billed as 32 cores because of the minimum, even though it has 16 physical cores. Multiply that across an estate built without the minimum in mind and the impact is substantial. The defence is consolidation onto fewer, fully populated sockets — a concrete engineering action with a direct financial return, and the first thing to do before any renewal quote is prepared.
05 Renewal-defence levers
Each change is a lever as well as a cost. Recurring cost replaces one-time cost, the core minimum rewards density, and bundling means savings run through documenting usage rather than picking cheaper products — because the cheaper products no longer exist. Our guides to the Broadcom price increase and negotiating with Broadcom show how to pull each one in a live renewal.
Reduce the core count before you negotiate. Consolidating onto fewer, fully populated sockets aligns the licensable count with physical reality and eliminates the minimum penalty. It is the one lever entirely within your control, and it changes the quantity being priced rather than merely the price.
Document which bundle components you actually use. Usage evidence supports a narrower commercial construct or a credit, and protects you in any audit. Then model the recurring subscription over five years with the renewal cliff included — the true cost is only visible on the longer horizon, detailed in our VMware Cloud Foundation pricing analysis.
06 Stay-vs-exit decision framework
Four considerations decide whether you subscribe, migrate, or run a hybrid. Weight them to your estate before committing, and price each path over the same horizon including migration and support.
Feature dependence
How much of the estate genuinely needs VMware-specific capabilities? The VMware-dependent subset sets the floor on your core count; everything else is a migration candidate.
Migration risk
Standard workloads move to a cheaper hypervisor with modest risk; feature-dependent, tightly coupled workloads do not. Match the path to the risk, not the other way round.
Three-year cost
Model the negotiated subscription against a costed exit over the same horizon. The decision should turn on numbers — see our VMware alternatives and VMware migration guides.
Operational depth
A hybrid caps the VMware bill but adds the complexity of running two platforms. It suits organisations with the engineering depth to manage both.
07 Our recommendation
Do this when the estate is deeply VMware-dependent. Discipline the quote with right-sizing and a costed exit, consolidate to kill the minimum penalty, and force a five-year model that exposes the renewal cliff before you sign.
Do this when the workload allows and the three-year cost favours an alternative hypervisor. Board-approve and price the migration in advance so you can credibly decline an unacceptable quote.
Do this for large mixed estates: keep feature-dependent workloads on a small VMware footprint and move the standard majority to a cheaper platform. Caps the VMware core count while avoiding the riskiest migrations.
08 Timing your response
The window to respond well is the months before your contract expires, not the weeks after the quote lands:
Start six months out Recommended
Complete a consolidation exercise, build a costed alternative, document product usage, and model the five-year cost before the negotiation opens. You arrive with a full position and a credible walk-away point.
Wait for the quote Weaker
A buyer who waits until the renewal quote arrives has none of that and negotiates from weakness — renewing on whatever terms are offered rather than the terms a costed exit would earn.
Turn the change into a plan
Our advisors model the negotiated subscription and the exit before you renew — buyer-side only, no reseller agreements, no referral fees.
The Licensing Edge
Weekly vendor and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.