The shift from VMware's socket-based perpetual licensing to Broadcom's core-based subscription model has created significant pricing complexity for enterprise buyers. Understanding exactly how the new pricing works — and how to challenge it — is the foundation of any VCF negotiation. This article provides the complete pricing mechanics with concrete calculations. For the broader strategic context, see the VMware Broadcom Guide 2026.
The Core-Based Pricing Model Explained
Broadcom's VMware pricing is based on physical CPU cores — every physical core in every server that is part of your vSphere cluster must be licensed. This is a significant departure from the pre-acquisition model, where vSphere was licensed per socket (per physical CPU), regardless of core count. Modern servers with high-core-count CPUs (32, 64, or even 96 cores per socket) make the core-based model substantially more expensive than socket-based licensing for most enterprise configurations.
The key definitions that drive your core count and therefore your cost:
- Physical core: A single processing core within a physical CPU. A 32-core CPU has 32 physical cores. Hyperthreading (logical cores / vCPUs) does not increase the physical core count for licensing purposes.
- Licensed server: Any physical server that is part of a vSphere cluster — including hosts that are powered off but connected to vCenter. You cannot exclude servers from licensing by powering them down.
- Minimum core count: Broadcom enforces a minimum of 16 cores per CPU for licensing. A 12-core CPU must be licensed as 16 cores. This primarily affects older hardware and edge deployments.
VCF and VVF List Pricing
| Product | Includes | List Price per Core/Year | Typical Enterprise Price |
|---|---|---|---|
| VCF Standard | vSphere, vSAN, NSX, Aria Suite (standard) | ~$90 | $55–$72 |
| VCF Advanced | VCF Standard + advanced Aria operations | ~$130 | $78–$104 |
| VVF (vSphere Foundation) | vSphere, vCenter, Aria Operations (basic) | ~$60 | $38–$50 |
Note: These are indicative pricing ranges based on our advisory engagements. Broadcom does not publicly publish a binding price list, and actual pricing varies by deal size, term, competitive situation, and account history. The "typical enterprise price" ranges represent what well-prepared buyers with 500+ core footprints and multi-year terms achieve — not the price a buyer will receive on a first quote without leverage.
Server-Level Pricing Examples
To make the pricing concrete, here are representative cost calculations for common enterprise server configurations.
Example 1: Standard 2-Socket Server (2026 Configuration)
Example 2: High-Density 4-Socket Server
Example 3: 50-Server Enterprise Datacenter (Typical)
The core count multiplier effect: The transition from socket-based to core-based pricing creates a multiplier effect that is invisible if you only look at per-core pricing. A 2-socket server with 32-core CPUs has 64 physical cores — the same server under the old model was licensed as 2 sockets. At $90/core VCF list pricing, the annual cost per server is 3–7× higher than typical previous SnS costs for the same hardware.
Why Core Counts Are Often Disputed
Broadcom's initial VCF quotes frequently use incorrect core counts. The sources of error are consistent across the engagements we have reviewed:
Stale CMDB Data
Most Broadcom quotes are based on infrastructure data exported from vCenter or provided by the customer's CMDB. CMDB data is notoriously stale — it frequently reflects servers that have been decommissioned, hardware that has been replaced with different core counts, and test infrastructure that should not be included in production licensing. Validating actual deployed server specifications directly from the infrastructure team before accepting any VCF quote is essential.
Inclusion of Non-Production Infrastructure
Broadcom's initial quotes often include all servers connected to vCenter — including development, test, and DR environments. Some customers have legitimate grounds to license non-production environments differently, or to structure agreements so that development infrastructure carries a reduced licensing obligation. This requires specific negotiation and documentation but is achievable.
Servers Scheduled for Decommission
Enterprises with hardware refresh cycles often have servers approaching end-of-life that will be decommissioned within 12–18 months. Including these servers in a 3-year VCF commitment creates pricing for capacity that will not exist for most of the commitment period. Negotiate the right to reduce licensed core count at no penalty as servers are decommissioned, or exclude soon-to-decommission hardware from the initial commitment entirely.
VCF vs VVF: When VVF Is the Right Choice
VMware vSphere Foundation (VVF) includes vSphere and vCenter but excludes vSAN, NSX, and Aria Suite. At $38–$50 per core per year for enterprise buyers versus $55–$72 for VCF Standard, VVF represents a 25–35% reduction for organisations that have independent solutions for storage, networking, and management.
VVF is appropriate when:
- Storage is provided by a dedicated SAN or NAS platform (NetApp, Pure Storage, HPE Primera) and vSAN is not required
- Network security and micro-segmentation is handled outside VMware (Palo Alto, Cisco, Zscaler)
- Infrastructure management is handled by ITSM/CMDB tools separate from Aria (ServiceNow, BMC Helix)
- The organisation has existing Aria licences through a previous arrangement that are not reflected in the Broadcom renewal quote
The qualification process for VVF requires demonstrating to Broadcom's deal desk that VCF components beyond vSphere and vCenter are genuinely not needed or are covered by existing separate tools. This argument must be made in writing with evidence — it is not accepted verbally. Organisations that successfully qualify for VVF instead of VCF typically save $30–$50 per core per year, which at 3,000 cores represents $90,000–$150,000 in annual savings.
Enterprise Discount Structure
Broadcom's discount structure is not published but follows consistent patterns based on our advisory engagements. Understanding the discount levers allows buyers to structure their engagement to maximise discount depth.
Volume Tiers
Core count drives base discount eligibility. Buyers with fewer than 500 cores typically receive minimal discount from list. 500–2,000 cores attracts 10–20% volume discount. 2,000–10,000 cores attracts 20–30%. Above 10,000 cores, discounts of 30–40% are achievable for well-prepared buyers. These are cumulative opportunities — stacking term, volume, and competitive leverage together produces the best outcomes.
Multi-Year Term Discounts
1-year terms: minimal discount from standard pricing. 2-year terms: 10–15% incremental discount versus annual pricing. 3-year terms: 20–25% incremental discount. The trade-off is contractual lock-in — 3-year VCF agreements should include annual price caps, technology refresh provisions, and exit rights for material product changes.
Competitive Discount
The most powerful discount lever is documented competitive evaluation. Buyers who present a written Nutanix or Azure Stack HCI evaluation with proof-of-concept results and migration cost estimates trigger Broadcom's competitive response pricing, which unlocks an additional 10–20% beyond standard volume and term discounts. This is the discount category that separates buyers who achieve 35–45% off list from those who achieve 15–20% off list.
Advisory firms including Redress Compliance maintain current Broadcom deal benchmarks from closed transactions — this benchmarking data is not available from any public source and provides the external reference point that allows buyers to evaluate whether Broadcom's offer is competitive relative to what comparable organisations have actually paid.
The Hardware Refresh Opportunity
If your organisation has a planned hardware refresh in the next 12–24 months, the intersection of hardware procurement and VCF licensing is a significant optimisation opportunity. Modern server CPUs carry substantially higher core counts than previous generations — a server refresh that upgrades from 16-core to 32-core processors doubles your licensed core count, doubling your VCF cost at the same server count.
Two strategies address this: first, optimise workload consolidation so the server refresh reduces total server count while increasing per-server density — maintaining or reducing total core count despite higher cores-per-server. Second, negotiate the hardware refresh timeline into your VCF agreement — begin the commitment at current core count and structure contractual rights to adjust licensing at defined intervals as the hardware refresh completes.
For the full negotiation strategy, see the VMware Broadcom Guide 2026. For migration alternatives that may be more cost-effective, see VMware Alternatives: Nutanix, Hyper-V, OpenShift Compared.