Since Broadcom acquired VMware, the renewal you thought you were walking into no longer exists. Perpetual licenses are gone, thousands of SKUs collapsed into a handful of bundles, and pricing moved from per-CPU to per-core with steep core minimums. The first quote most teams receive is a full-stack bundle priced against a baseline they never agreed to, often reported at anywhere from 2x to 10x the old line item.
The good news: the model is knowable, and it has soft spots. This guide walks through how Broadcom pricing actually drives your cost, where the money hides, the levers that genuinely move a number, and the timing that gives you leverage. It is written from the buyer's side by a strategic sourcing executive with Fortune 50 experience who has worked thousands of renewals, with no vendor referral fees.
This page teaches the shape of the problem. The full VMware / Broadcom Renewal Playbook adds the fillable worksheets, the six-point negotiation plan, copy-paste emails, and the pre-renewal checklist.
Directional and estimated only. These ranges come from public pricing plus aggregated practitioner experience across thousands of renewals. They are not any organization's confidential contract terms, and not a promise or guarantee of savings. Normalize your own order form to the same per-core basis before you compare.
| Cost line | Typical unit | Directional range |
|---|---|---|
| vSphere Standard | per core/yr (subscription) | directionally in the low tens of dollars per core/yr list (~$50); the standalone option that returned after pushback |
| vSphere Foundation (VVF) | per core/yr | directionally around $135/core/yr list; vSphere + smaller vSAN entitlement + operations |
| VMware Cloud Foundation (VCF) | per core/yr | directionally ~$300–350/core/yr list; the full stack, and the biggest overspend this cycle |
| Per-core minimums | ~16 cores per CPU | minimum billing per socket regardless of populated cores |
| Bundled vSAN capacity | per-core entitlement | included in both, but VVF's is much smaller than VCF's (VCF directionally ~1 TiB/core); shelfware if you run third-party storage |
| Discount at scale + term | % off list | directionally ~10–40%+ at large core counts and multi-year; the deepest saving is right-bundling, not rate |
| Annual uplift / true-forward | % + core growth | assume an increase unless capped in writing |
How to read this: keep your own ranges wide and anchor to your current run-rate normalized to the new per-core model. The biggest saving is right-bundling and core right-sizing, not haggling the per-core rate.
How Broadcom pricing really drives your VMware renewal cost
Five levers now determine the number, and they only make sense together, not one at a time:
- Cores, not CPUs. Pricing is per physical core, subscription, billed annually. A dual-socket host with high-core CPUs can carry a very different bill than the same workload on older hardware.
- The bundle you're placed in. The catalog now centers on two stacks: VMware Cloud Foundation (VCF), the full private-cloud stack (vSphere + vSAN + NSX + operations), and vSphere Foundation (VVF), vSphere plus a smaller vSAN entitlement and operations. Standalone vSphere Standard and Essentials Plus returned after customer pushback, but reps won't lead with them.
- Core minimums. Subscriptions carry a per-CPU core minimum (directionally around 16 cores per CPU) that has risen over time. On smaller or lightly-populated sockets you can pay for cores you don't physically have.
- Bundled capacity you may not use. VCF and VVF both bundle vSAN capacity per core, and VCF layers on NSX networking and the full automation stack. Run third-party storage or networking and you may be paying for shelfware by design.
- Term and timing. Multi-year terms lock your baseline. Locking a bad baseline for three years is the most expensive mistake in this cycle.
The core question: are you buying the stack you actually run, or the stack Broadcom would prefer to sell you? Most first quotes assume the latter.
The traps: where the money hides
- Forced full-stack bundling. You ran vSphere, maybe vSAN. The quote is VCF, with NSX, full operations, and a large vSAN entitlement you have no plan to use. This is the single biggest source of overspend this cycle.
- Per-core minimums on small hosts. Minimums can force you to license phantom cores. Host consolidation and CPU selection change this materially.
- Perpetual-to-subscription conversion. Licenses you owned become an annual bill. Model the multi-year delta, not just the year-one quote.
- Portfolio pruning means new contracts, new vendors. End-User Computing (Horizon, Workspace ONE) and Carbon Black were divested. If you rely on them, they are now separate agreements with separate owners; don't let them get orphaned or double-counted.
- Renewal uplift and true-forward. Growth in cores or capacity gets swept into the renewal at list, and an annual VMware renewal uplift is typically assumed unless you cap it.
- Audit exposure. Broadcom's heritage (CA, Symantec) has a reputation for aggressive license compliance. Clean your deployment data before you're in a negotiation, not after an audit letter.
The levers that actually move a Broadcom number
You won't get Broadcom's rate card, and you shouldn't quote one. But you can anchor a defensible position. The discount lives at the bundle and term level, not the line item, so the levers in order of power are:
- A costed exit path. Nutanix AHV, Microsoft Hyper-V / Azure Stack HCI / Azure VMware Solution, Red Hat OpenShift Virtualization, Proxmox VE, or public-cloud migration for a workload segment. You don't have to move everything; one credible, quoted lane changes the conversation. Vague threats do not.
- Right-bundling. Documented proof you don't use NSX or full vSAN, so VCF is the wrong SKU and VVF or vSphere Standard fits. This is where the largest savings tend to live.
- Core right-sizing. Consolidation and CPU choices that cut licensable cores against the minimums.
- Term traded for protections. Concede multi-year only in exchange for a firm renewal price cap, true-down rights, and bundle-swap rights, not just a lower year-one.
Your strongest number is your own current run-rate, normalized to the new per-core model. Walk in knowing your effective cost per core today and what the quote implies.
Timing and leverage: when to start
Start 9 to 12 months before renewal. You need runway to clean deployment data, model bundles, and, if it comes to it, pilot an alternative. Broadcom's fiscal year ends in the late-October to early-November window, and quarter-ends carry the usual motivation, but timing only helps if your baseline and your alternative are ready before the rep's clock, not after.
Protections to put in writing before you sign anything:
- Renewal price cap — a fixed maximum annual uplift for the term and at the next renewal.
- Core-count flexibility and true-down rights at renewal, not just true-up.
- Bundle-swap rights if your architecture changes.
- Co-terming so you're not renegotiating multiple dates a year.
- Migration runway for divested products you still run, and fair audit terms — notice periods, remediation windows, no punitive list-price back-charges.
Get the full VMware (Broadcom) Renewal Playbook
This guide is the shape of the problem. The $59 playbook gives you the fillable worksheets, the six-point negotiation plan, two copy-paste emails, and the full pre-renewal checklist — everything to walk into the VMware (Broadcom) conversation with a number and a plan.
Get the VMware (Broadcom) playbook — $59 → Get the free 15-point renewal checklist →Frequently asked questions
How much does a VMware renewal increase under Broadcom?
There is no single figure, and any number you see is directional. Many teams report first quotes running anywhere from 2x to 10x the old line item, driven mostly by being placed in the full VCF bundle and by per-core minimums rather than by the raw rate. The increase is often controllable: right-bundling to VVF or vSphere Standard when the stack fits, and right-sizing cores, are what bring it down. Treat these as directional ranges from aggregated experience, not a promise about your specific quote.
What is the difference between VCF, VVF, and vSphere Standard?
VMware Cloud Foundation (VCF) is the full private-cloud stack: vSphere plus vSAN, NSX, and operations/automation. vSphere Foundation (VVF) is vSphere plus a smaller vSAN entitlement and operations, without NSX. vSphere Standard is the standalone option that returned after customer pushback, for teams running vSphere alone. The right question is the smallest bundle that fits what you actually run. Being placed in VCF when you don't use NSX or full vSAN is the single biggest source of overspend this cycle.
When should I start my VMware Broadcom renewal negotiation?
Start 9 to 12 months before renewal. You need runway to clean deployment data, reconcile cores and sockets to entitlements, model which bundle fits, and, if needed, cost a credible alternative for at least one workload segment. Broadcom's fiscal year ends in the late-October to early-November window and quarter-ends add motivation, but timing only helps if your baseline and alternative are ready before the rep's clock rather than after.
How is VMware pricing calculated now that it is per-core?
Pricing is per physical core, sold as an annual subscription, with a per-CPU core minimum (directionally around 16 cores per CPU). That means a lightly-populated socket can force you to pay for cores you don't physically have, and CPU selection plus host consolidation change the licensable core count materially. Your strongest reference point is your own current spend normalized to effective cost per core, compared against what the new quote implies.
What protections should I demand in a VMware renewal contract?
Get them in writing: a renewal price cap (a fixed maximum annual uplift for the term and at the next renewal), core-count true-down rights and not just true-up, bundle-swap rights if your architecture changes, co-terming so you aren't renegotiating multiple dates a year, migration runway for divested products you still run, and fair audit terms with notice periods and no punitive list-price back-charges. Concede multi-year term only in exchange for these caps and flexibility.
Key takeaways
- Broadcom moved VMware to per-core annual subscriptions with steep core minimums, and the first quote is usually the full VCF bundle priced against a baseline you never agreed to.
- The biggest savings come from right-bundling (VVF or vSphere Standard when the stack fits) and core right-sizing, not from haggling the per-core rate.
- A single credible, costed exit path for one workload segment is what actually moves a Broadcom number; vague threats do not.
- Start 9 to 12 months out and trade multi-year term only for a firm renewal cap, true-down rights, and bundle-swap rights in writing.
- All pricing ranges here are directional and estimated, not confidential terms or a guarantee; anchor to your own run-rate normalized to per-core.