VMware Cloud Foundation Cost Per Core: Real Numbers After Broadcom

The 50 Percent Price Cut That Increased Costs by 10x

Broadcom's account teams present the VCF per-core pricing reduction — from $700 to $350 per core per year — as evidence of a customer-friendly pricing strategy. The claim requires context to evaluate accurately. The $700 per core was a standalone vSphere licence cost that did not include NSX, vSAN, the Aria Suite, or any of the other components now mandatory in VCF. The $350 per core covers the entire bundled stack, but it is applied to every physical core in every licensed host, and it replaces a perpetual licence model with an annual subscription that eliminates the ability to run paid-up software beyond the subscription term.

The structural cost drivers that convert a per-core price reduction into enterprise cost increases are the forced bundling of components customers may not need, the extension of licensing to every physical core rather than just those running licensed workloads, the elimination of perpetual licence carryover, and the core count inflation that occurs naturally as enterprises refresh hardware to modern high-core-count processors.

Support cost increases of 3 to 5 times compared to the old perpetual plus maintenance model compound the effect. An organisation that paid $250,000 per year in VMware maintenance and support may face an annual VCF subscription of $750,000 to $1,250,000 for the same infrastructure footprint.

VCF Per-Core Pricing: The Full Picture

Understanding the per-core economics requires mapping out all cost components, not just the licence headline.

List Price vs. Enterprise Negotiated Price

VCF list price is $350 per core per year. No enterprise customer pays list price on a large deployment. Enterprise negotiated rates for VCF typically fall between $140 and $180 per core per year for customers with 500 or more cores and meaningful negotiating leverage. Small deployments or customers with limited leverage tend to achieve $180 to $250 per core per year. The variance is significant and negotiating from the right starting position matters materially.

For comparison, the lower-tier VMware vSphere Foundation (VVF) has a list price of $135 per core per year and enterprise negotiated rates of $80 to $120 per core per year. VVF excludes NSX, SDDC Manager, and the Aria Suite Enterprise components.

The 16-Core Minimum Per Socket

Broadcom requires a minimum of 16 cores per physical CPU socket for licensing purposes. A server with two 12-core CPUs is licensed as 2 × 16 = 32 cores, regardless of actual core count. This minimum does not apply to servers with 16 or more cores per socket — which describes most modern server CPUs. The practical effect of the minimum is most significant for older server hardware with sub-16-core processors, where it can inflate the licensed core count by 20 to 30 percent.

The 72-Core Order Minimum

Effective from April 2025, Broadcom requires a minimum order of 72 cores. This does not affect the per-core price but establishes a minimum annual spend of $25,200 at list or approximately $10,000 to $13,000 at enterprise negotiated rates. For very small deployments, this floor matters. For medium and large enterprises, the physical core count typically exceeds 72 significantly.

The 20 Percent Late Renewal Penalty

VCF subscriptions that lapse — even briefly — attract a 20 percent surcharge on the renewal. This penalty is applied automatically and account teams have no authority to waive it. For an organisation renewing 2,000 cores at $160 per core per year ($320,000 annual), missing the renewal date costs an additional $64,000. The operational controls required to prevent inadvertent lapses in large organisations add administrative overhead that was not present under the perpetual licensing model.

Why Core Counts Are Growing, Not Shrinking

The most insidious aspect of per-core licensing is the interaction with hardware refresh cycles. Server CPU architectures have been adding cores per socket at a consistent pace. The transition from 16-core CPUs to 32-core CPUs doubles the licensed core count for the same number of physical hosts. The transition to 48-core or 64-core CPUs triples or quadruples it.

An enterprise that runs 100 vSphere hosts with 16-core CPUs (1,600 licensed cores at $160 per core = $256,000 per year) faces a staggering cost exposure when refreshing to 32-core CPUs: 3,200 cores at the same per-core rate equals $512,000 per year — a 100 percent cost increase purely from hardware refresh, with no change in workload footprint. The per-socket perpetual licensing model that preceded Broadcom's changes did not expose customers to this hardware refresh inflation.

Non-production environments compound this further. Development clusters, disaster recovery clusters, and test environments all require full VCF licensing. An enterprise with a production environment of 1,000 cores, a DR environment of 500 cores, and a development environment of 300 cores is licensing 1,800 cores, not 1,000. The pre-Broadcom model often included discounted or free non-production licensing rights that do not exist in the standard VCF subscription.

Real-World Enterprise Cost Increase Examples

The documented examples of VCF cost increases are extreme enough to have attracted significant media and legal attention.

AT&T: A 1,050 Percent Increase

AT&T's CEO documented a proposed VMware billing increase of 1,050 percent in a letter to Broadcom CEO Hock Tan. AT&T alleged that Broadcom violated contractual terms by not honouring previous pricing commitments. The dispute proceeded to litigation, with Broadcom and AT&T reaching a settlement in late 2024 under confidential terms. The AT&T case is the highest-profile illustration of Broadcom's aggressive pricing strategy but is not an outlier in direction — only in magnitude.

UK Universities and Public Sector

Multiple UK higher education institutions reported VMware renewal quotes of 10 to 15 times their previous annual costs. One documented case involved an annual cost increase from approximately £40,000 to £500,000 — a 1,150 percent increase. Public sector organisations, constrained by budget cycles and procurement rules, face particular difficulty absorbing these increases or executing migration projects rapidly enough to avoid them.

Mid-Market Enterprise: The Typical Range

For mid-market enterprises with 300 to 2,000 cores, documented cost increases from perpetual VMware licensing to VCF subscriptions typically range from 200 to 500 percent. The lower end of this range reflects organisations that negotiated effectively, had meaningful competitive alternatives developed, and committed to multi-year terms. The upper end reflects organisations that renewed without independent advisory support or competitive leverage.

Total Cost of Ownership Modelling

A realistic TCO model for VCF requires accounting for all cost components across the full subscription period, including factors that are frequently underestimated in initial procurement assessments.

Three-Year TCO for a 500-Core Enterprise Deployment

Starting assumptions: 500 licensed cores, enterprise negotiated rate of $160 per core per year, 3-year subscription term. Annual licence cost: $80,000. Three-year licence cost: $240,000. At a 5 percent annual escalation cap (best achievable in negotiation), year three cost reaches $88,200, and the three-year total is $248,000.

Adding production DR environment at 250 additional cores: $40,000 per year additional, $120,000 over three years. Adding development environment at 150 cores: $24,000 per year additional, $72,000 over three years. Total three-year VCF licence cost for the full deployment footprint (900 cores): $540,000 at $160 per core per year.

If the same organisation was previously paying $200,000 per year in VMware perpetual maintenance (a common cost level for this deployment scale at pre-Broadcom rates), the three-year increase is $340,000 — representing a 170 percent cost escalation.

Hardware Refresh Impact

If the organisation refreshes to 32-core CPUs during the three-year subscription period, the core count grows from 900 to 1,800 cores at renewal, and the annual VCF cost doubles. TCO modelling must account for this scenario, especially for organisations with hardware refresh cycles of three to five years.

Per-Core Cost Comparison: VCF vs Nutanix vs Azure VMware Solution

The most effective negotiating preparation involves developing credible cost comparisons with the two primary alternatives that Broadcom's account teams take seriously: Nutanix Cloud Infrastructure and Azure VMware Solution.

Nutanix Cloud Infrastructure

Nutanix Cloud Infrastructure (NCI) provides compute virtualisation (AHV hypervisor), hyper-converged storage, and management capability in a modular subscription model. Pricing is tier-based — Starter, Pro, and Ultimate — with enterprise rates typically falling between $100 and $150 per core per year for the Pro tier, which provides capability comparable to VCF. Critically, Nutanix does not force customers to pay for networking components they do not use — the equivalent of NSX functionality (Nutanix Flow) can be added selectively.

Customers migrating from VMware to Nutanix report total cost savings of 40 to 60 percent compared to post-Broadcom VCF pricing in most documented cases. The migration requires workload re-platforming from vSphere to AHV, which carries implementation cost and operational change management requirements, but for organisations with straightforward VM workloads the migration path is well-established and achievable within a 12 to 18-month programme.

Azure VMware Solution

Azure VMware Solution (AVS) runs VMware workloads natively in Microsoft Azure using a portable VCF subscription from Broadcom. The AVS model eliminates on-premises infrastructure capital expenditure and maintenance overhead but combines Broadcom per-core licence costs with Azure infrastructure consumption charges. At the current portable VCF subscription rate of $140 to $180 per core per year plus Azure infrastructure costs of approximately $0.25 to $0.40 per core per hour, the total annual cost of AVS is typically higher than on-premises VCF for steady-state workloads but eliminates the capital refresh requirement.

AVS provides particular value for organisations that are reducing on-premises footprint, have significant burst workload requirements, or need Azure ecosystem integration (Microsoft 365, Azure AI Services, Azure Extended Security Updates for Windows). Microsoft Azure Reserved Instances and Savings Plans can reduce the infrastructure component by 30 to 50 percent for predictable workloads.

Five Recommendations for Managing VCF Per-Core Costs

1. Audit your actual core count before any renewal. Many organisations maintain inaccurate records that overstate the physical cores in active VMware clusters. An independent audit regularly identifies 15 to 25 percent reductions in the licensed core scope, directly reducing renewal costs before any negotiation.

2. Model hardware refresh scenarios in your TCO. Any business case for continuing on VCF must include a sensitivity analysis for hardware refresh at modern core counts. The cost of a server refresh from 16-core to 32-core CPUs should be modelled as a 100 percent per-core licensing cost increase, not a neutral infrastructure refresh.

3. Develop a Nutanix or AVS competitive comparison before renewal. The most effective per-core negotiating lever is a documented, costed alternative. An engagement letter with a Nutanix implementation partner or an Azure VMware Solution sizing assessment from Microsoft is the minimum requirement for creating real commercial pressure on Broadcom.

4. Negotiate multi-year price escalation caps. Annual escalation caps of 3 to 5 percent, locked in at the current per-core rate, can save significant cost over a three to five-year contract term relative to Broadcom's standard escalation schedule. These caps must be explicitly negotiated — they are not in the standard VCF subscription terms.

5. Scope non-production environments separately. Negotiate the most favourable possible treatment for DR, development, and test environments. Some customers have successfully negotiated reduced-rate licensing for environments with defined usage restrictions. This requires direct negotiation with Broadcom and explicit contractual definition of what qualifies as non-production.