Broadcom rebuilt VMware licensing around per core subscriptions and two bundles. Here is the math, the moves, and the levers that still work.
Broadcom replaced VMware perpetual licensing with per core subscription bundles, and the renewal math now turns on core counts, bundle tier, and how credible your exit looks.
Broadcom ended perpetual VMware licensing and now sells subscription bundles priced per physical core, with a 16 core minimum per CPU. The portfolio consolidated around VMware Cloud Foundation, with vSphere Foundation as the smaller estate option.
Support is no longer a separate maintenance line. It rides inside the subscription, which is why the renewal compare against old maintenance looks so violent.
Old model vs the Broadcom model
| Dimension | Pre acquisition | Under Broadcom |
|---|---|---|
| License type | Perpetual plus SnS maintenance | Subscription term only |
| Metric | Per CPU, core caps varied | Per core, 16 core minimum per CPU |
| Portfolio | Dozens of standalone SKUs | VCF and VVF bundles plus few add ons |
| Renewal posture | Maintenance roll forward | Repriced commit at term end |
Bundles raise the revenue floor per customer and make line item negotiation harder. That is the design intent, and the buyer response has to work at the estate level, not the SKU level.
VMware subscriptions meter every physical core on hosts running the software, and each CPU bills at least 16 cores even when it carries fewer. A two socket host with 12 core CPUs therefore licenses 32 cores, not 24.
Counts go wrong on decommissioned hosts still in the inventory export, on clusters that no longer run VMware, and on oversized failover capacity. A pre quote scrub of the RVTools export against the live estate is the cheapest savings available.
The 2026 moves tightened the bundle structure further: VCF absorbed more of the advanced services, license portability between on premises and supported clouds firmed up, and minimum commit expectations rose for direct enterprise accounts. Broadcom publishes current packaging through the Broadcom support portal and product pages.
Channel economics changed too. Smaller accounts moved to authorized partners for the Broadcom portfolio, which changes who you negotiate with even when the price list does not move.
Portability helps hybrid estates because the same subscription can follow workloads to supported clouds. It does not lower the price; it removes one excuse for double licensing during migrations.
Four levers consistently moved VMware renewals in our file: a scrubbed core inventory, bundle tier fit, term length traded against caps, and a funded exit for a defined estate slice. None of them require actually leaving.
A credible exit names the platform, the budget line, and the migration date for a specific cluster set. A slide that says we are evaluating alternatives moves nothing; a signed pilot moves the discount.
The standard advice says sign the shortest possible term and wait for Broadcom to soften. We disagree. In roughly 20 of the 30 plus VMware estates Fredrik Filipsson advised in 2024 to 2025, short panic terms simply repeated the shock a year later at a higher list, while buyers who segmented the estate, exited the slice with real alternatives, and committed the core under a cap got the durable number. The buyer side move is to decide what stays VMware for three years, cap it, and make the rest visibly contestable. Waiting is not a strategy; segmentation is.
Three cuts of our advisory engagement file frame the size of the opportunity.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Five moves turn this analysis into a lower invoice on the next renewal.
White Paper · Broadcom / VMware
Broadcom VMware Renewal Survival 2026
The 2026 buyer side reference on Broadcom VMware renewals. Read it free.
No. Broadcom sells VMware as subscription only, priced per physical core with a 16 core minimum per CPU. Existing perpetual licenses keep running, but support renewals on them have ended in favor of subscription offers.
Every CPU bills at least 16 cores even when it has fewer. A two socket host with 12 core CPUs licenses 32 cores, which is why host hardware shape changes the subscription bill.
First subscription quotes in our 2024 to 2025 file ran 2 to 3 times prior maintenance spend. Buyers who scrubbed cores, fixed tier fit, and showed a funded exit closed 25 to 40 percent below the opening number.
No. vSphere Foundation and remaining standalone editions cover estates that do not use the full VCF stack. Paying for VCF where the features go unused is the most common tier mistake we see.
Yes. In our engagement file the discount moved when a defined estate slice had a named platform, budget, and migration date. Vague evaluation language moved nothing.
Sign the longer term only when it buys a renewal cap and locked unit pricing on the clusters you will keep. A short term without leverage just reprices the estate sooner.
The bundle map, core counting rules, and renewal levers from 25 plus VMware engagements.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Broadcom prices the estate, not the SKU. Decide what stays, cap it, and make the rest visibly contestable.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Pricing moves, audit signals, and the levers that work. No vendor spin.