Somewhere in your renewal folder is a VMware quote that is 3x to 10x what you paid Dell, HPE, or VMware directly three years ago — and that range is not an outlier, it is the pattern I hear from IT directors across every vertical since Broadcom closed the acquisition in late 2023. The licensing model that produced that quote is genuinely different: per-core subscriptions only, a 16-core minimum per CPU, a 72-core minimum per order, and — as of the 9.0 release in June 2025 — no standalone vSphere SKU at all.
This brief is the plain-English decoder: what Broadcom actually changed, what the bundles contain, how the minimums distort the math for small and edge sites, and what to do before your renewal lands. No vendor spin, no consultant gatekeeping.
What changed
Broadcom collapsed a catalog of 160-plus VMware products into a handful of subscription bundles. Perpetual licenses are gone — you cannot buy one, and existing perpetual keys keep running but receive no updates once support lapses. Everything is now licensed per physical core, with a floor of 16 cores counted per CPU even if the socket has fewer.
Two later moves matter just as much. In April 2025, Broadcom added a 72-core minimum per order, which quietly repriced every small deployment. And with the 9.0 release in June 2025, vSphere stopped being a product you can buy at the current version: vSphere 9 ships only inside VMware Cloud Foundation (VCF) or vSphere Foundation (VVF). The standalone vSphere Standard and Enterprise Plus SKUs top out at version 8 Update 3. A “vSphere renewal” in 2026 is really a decision about which bundle to move to — that is the part most quotes bury.
The 2026 bundle decoder
As of mid-2026 the practical menu is three items. VCF is the full private-cloud stack — vSphere, vSAN, NSX networking, automation, and operations tooling as one integrated platform, now on release 9.1. VVF is the middle tier: vSphere plus operations management and a smaller vSAN entitlement, aimed at shops that want current vSphere without the full stack. vSphere Standard survives as a budget SKU, but only at the 8.x code line.
| vSphere Standard | VVF (vSphere Foundation) | VCF (Cloud Foundation) | |
|---|---|---|---|
| Current version | 8 Update 3 only | 9.x | 9.x |
| What’s inside | Core hypervisor, vCenter | vSphere 9, VCF Operations, limited vSAN | Full stack: vSphere, vSAN, NSX, automation, operations |
| vSAN entitlement | None | 0.25 TiB per core | 1 TiB per core |
| Who it fits | Legacy estates coasting to a migration decision | Virtualization-first shops that skipped NSX | Committed VMware private-cloud strategies |
| Trap to watch | vSphere 8 support ends in 2027 | vSAN entitlement rarely covers real capacity | You pay for NSX and automation whether you deploy them or not |
Credit where due: VCF 9 is the most coherent private-cloud platform VMware has ever shipped. Broadcom’s engineering consolidation produced one aligned release instead of a loose federation of products, and for enterprises that actually run vSAN and NSX at scale, the bundle can pencil out against buying the pieces separately in the old catalog. The criticism is not that VCF is bad software. It is that VCF is the only door, and the door has a cover charge.
The minimums that change the math
Run the numbers on a typical edge site: two hosts, each with a single 12-core CPU. Physically that is 24 cores. The 16-core-per-CPU floor rounds it to 32. The 72-core order minimum then more than doubles it again — you are billed for 72 cores to run 24. Branch offices, retail back rooms, factory floors, and small DR sites all hit this wall, and it is why the 2025 change generated more anger than the original subscription pivot.
- Below roughly 72 physical cores per site, you are paying for phantom capacity — consolidate sites onto shared clusters or move those workloads off VMware.
- Between 72 and a few hundred cores, high-core-count CPUs are your friend: fewer sockets at 32 or 48 real cores waste less against the 16-core floor than many small sockets.
- Above that, the minimums stop mattering and the negotiation is purely about per-core rate and term length.
The takeaway a VP can repeat: VMware now prices like a data-center platform, so anything smaller than a data center is structurally overpaying.
What a renewal actually costs now
List pricing varies by geography, term, and tier, so treat any single number you read online with suspicion. The shape of the market as of mid-2026: organizations coming off perpetual-plus-support agreements report first quotes at 3x to 10x their prior annual spend, with the worst multiples hitting small estates (the minimums) and vSphere-only shops being pushed up-tier into VVF or VCF. Three-year commitments price meaningfully better per core than one-year terms, which is exactly the lock-in they are designed to buy.
Do the true comparison before you sign anything. Your old number was license amortization plus roughly 20 percent annual support. Your new number is the subscription — but the honest comparison also prices the alternative: migration cost plus the competing platform’s subscription. Broadcom’s negotiators know most enterprises cannot migrate before the renewal date, and the quote reflects that leverage. Your counter-leverage is a credible, costed exit plan — we cover the tactics that have actually moved quotes in our Broadcom renewal negotiation playbook.
Why it matters
This is not a procurement annoyance; it is an architecture decision with a deadline. Staying current on VMware now means adopting a bundle strategy, and coasting on vSphere 8 only works until general support runs out — see our timeline analysis in vSphere 8 end of support: what October 2027 really means. After that, an unpatched hypervisor under everything you run stops being a cost decision and becomes an audit finding.
Budget owners should also note what the model does to forecasting. Perpetual licensing front-loaded cost and made support predictable. Per-core subscription converts your hypervisor into a recurring line item that reprices at every renewal — on Broadcom’s schedule, not yours.
What to do about it
Three moves, in order. First, inventory your real core counts per site and model them against the 16-core and 72-core floors — that spreadsheet is the single highest-leverage hour of work available to you this quarter. Second, segment your estate: workloads that genuinely benefit from VCF’s integrated stack, workloads that just need a hypervisor, and edge sites the minimums punish. Third, price the exits honestly. Proxmox, Nutanix, Hyper-V, and OpenShift Virtualization each fit a different segment of that split, and we have compared them head-to-head in our guide to VMware alternatives in 2026.
The verdict: if you are large, standardized, and using the full stack, VCF at a negotiated three-year rate is defensible. Everyone else should be running a funded migration evaluation right now — not because leaving is mandatory, but because a credible option to leave is the only thing that changes the quote.
Frequently asked questions
Can you still buy VMware perpetual licenses?
No. Broadcom ended perpetual sales in early 2024. Existing perpetual licenses keep running, but without an active support contract you get no patches or updates — and vSphere 9 was never released as a perpetual product at all.
What is the minimum number of cores for VMware licensing?
Two floors apply: every CPU is counted as at least 16 cores regardless of its actual core count, and since April 2025 new orders carry a 72-core minimum. Small sites frequently pay for two to three times the cores they physically run.
Is vSphere 9 available as a standalone product?
No. vSphere 9 ships only inside VMware Cloud Foundation 9 or vSphere Foundation 9. The standalone vSphere Standard and Enterprise Plus SKUs are frozen at version 8 Update 3.
How much did VMware prices increase under Broadcom?
There is no single official increase, but as of mid-2026 organizations moving from perpetual-plus-support to subscription commonly report quotes 3x to 10x their prior annual spend. Small estates hit hardest because of the core minimums; large multi-year commitments negotiate materially better rates.
What is the difference between VCF and VVF?
VCF is the full private-cloud stack — vSphere, vSAN (1 TiB per core), NSX, automation, and operations. VVF is vSphere plus operations tooling with a smaller vSAN entitlement (0.25 TiB per core). VCF costs more per core and is worth it only if you deploy the stack you are paying for.
Enterprise Techie publishes vendor-honest analysis like this daily — get the brief by email, free.