Broadcom / VMware · Licensing Deep-Dive

Cracking the Per-Core VMware Licensing Model Calculations and Cost Pitfalls

Broadcom's shift from per-CPU to per-core licensing is driving 5x to 40x cost increases for VMware customers. This CIO playbook dissects the maths, exposes the traps, and delivers a 10-step strategy to regain control of your virtualisation spend.

5x-40x
Reported Cost Increase Range
16 Cores
Minimum Licence Count Per CPU Socket
20%
Late-Renewal Penalty on First Year
3-5 Yr
Multi-Year Lock-In Terms Broadcom Pushes
Series Context. This article is part of the Broadcom/VMware Licensing Overview pillar. Read the full guide for the complete picture of post-acquisition changes.

Get Broadcom/VMware Licensing Insights Delivered

Join enterprise IT leaders receiving our monthly advisory on Broadcom/VMware licensing changes, negotiation tactics, and cost optimisation strategies.

Subscribe Free →

Licensing Deep-Dive  ·  Fredrik Filipsson  ·  Updated February 2026

01 Executive Summary

VMware's move from per-processor to per-core licensing, enacted under Broadcom's ownership, represents the most consequential change to virtualisation economics since VMware first introduced per-socket pricing two decades ago. Every physical core in a host now requires its own licence unit, a 16-core-per-CPU minimum floor applies regardless of the actual silicon, and a punitive 20% late-renewal fee awaits anyone who misses an anniversary date.

The result? Renewal quotes that range from uncomfortable to existential for IT budgets, with documented increases of 5x to 40x depending on hardware density and prior contractual terms.

🔢

Core Counts Have Exploded

Modern dual-socket servers often carry 64 to 128 cores per host. Each one is a billable licence unit under the new model.

💲

Subscriptions Replace Perpetual

One-time licence fees are gone. Annual or multi-year subscriptions now represent the sole procurement path for VMware.

📦

Mandatory Bundling Inflates Bills

vSphere Foundation and Cloud Foundation bundles force customers to pay for components (vSAN, Aria, NSX) they may never deploy.

Penalties Punish Procrastination

A 20% surcharge on late renewals, far steeper than Microsoft's approximately 3%, creates a financial cliff for any lapsed subscription.

02 From Processors to Cores: A Licensing Sea Change

For the better part of two decades, VMware licensing was elegantly simple: one licence per CPU socket. A dual-socket server needed two licences. A four-socket host needed four. The number of cores inside each socket was irrelevant. This simplicity made capacity planning, budgeting, and compliance verification straightforward.

Broadcom's acquisition in late 2023 dismantled that model. Starting in early 2024, every new VMware subscription is metered on a per-core basis. The shift aligns VMware with a broader industry trend (Microsoft SQL Server and Oracle Database have used per-core metrics for years) but introduces a fundamentally different cost dynamic for virtualisation infrastructure.

Why Broadcom Made the Switch

The commercial logic is transparent. Modern server processors have evolved dramatically: AMD EPYC 9004 chips ship with up to 128 cores per socket, and Intel Xeon 6 "Sierra Forest" reaches 144 cores. Broadcom has publicly targeted growing VMware revenue from $4.7 billion to $8.5 billion within three years of the acquisition, and per-core metering is the primary mechanism to achieve that.

Old Per-Socket Model

10 hosts x 2 sockets = 20 licences. Core count inside each socket was irrelevant. Perpetual licence + annual support fee (approximately 20% of licence value). Budget: predictable, capital expenditure-based.

New Per-Core Model

10 hosts x 2 CPUs x 20 cores = 400 licences. Every physical core is a billable unit. 16-core minimum per CPU applies. Subscription-only, no perpetual option. Budget: recurring OpEx, subject to annual repricing.

03 What Exactly Counts as a "Core"?

Before you can calculate your licence exposure, you must understand precisely what Broadcom considers a "core." The definition is deceptively simple (one physical computing unit on a processor die) but its application across on-premises, virtualised, and cloud environments introduces several nuances that regularly trip up procurement teams.

📦

Physical Servers (On-Prem)

A core is a physical processor core. Hyperthreading does not double your count. Two hardware threads on one physical core still represent one licensable core. This is consistent with how Microsoft and Oracle treat hyperthreading.

💻

Virtualised Environments

The licence count ties back to the physical cores powering the hypervisor layer, not the virtual CPUs assigned to guest VMs. You licence the host, not the guests. The number of VMs running on a host is irrelevant to the core count.

☁️

Public Cloud (BYOL)

Cloud providers often label units as "vCPUs" which typically correspond to one hyperthread, meaning 2 cloud vCPUs = 1 physical core for licensing purposes. Misinterpreting this ratio is one of the most common sources of over-purchasing.

Mini Case Study: Cloud vCPU Misinterpretation Averted. A European logistics firm assumed their Azure VMware instances' "8 vCPU" allocation meant 8 core licences per instance, across 40 instances (320 cores total). An internal review confirmed that Azure VMware's vCPUs use hyperthreading. Correct count was 160 cores, 50% fewer than initially quoted. The firm avoided approximately $240,000 in unnecessary annual subscription costs.

04 The 16-Core Minimum: How the Per-CPU Floor Inflates Costs

Broadcom's per-core model imposes a minimum of 16 cores per CPU socket, regardless of the actual silicon installed. If your server contains a processor with only 4, 8, or 12 physical cores, VMware licensing treats it as if it has 16. You pay for cores that do not physically exist.

The rule is applied per CPU, not per server. A single-socket server with an 8-core processor is licensed as 16 cores. A dual-socket server with two 8-core CPUs is licensed as 32 cores (16 per socket), even though the server only has 16 physical cores.

Server ConfigurationPhysical CoresLicensable Cores (16-min/CPU)Phantom Core Tax
1 socket x 4 cores416+300%
1 socket x 8 cores816+100%
2 sockets x 8 cores1632+100%
2 sockets x 16 cores32320%
2 sockets x 32 cores64640%
2 sockets x 64 cores1281280%
The 72-Core Proposal and Its Reversal. In March 2025, Broadcom communicated an even more aggressive policy: a 72-core minimum per server for all new subscriptions. The backlash was swift. Within weeks, Broadcom rescinded the 72-core rule. The 16-core-per-CPU minimum remains the operative rule. However, the episode demonstrates Broadcom's willingness to test aggressive pricing boundaries and only retreat under coordinated customer resistance.

05 How Costs Multiply: Anatomy of the 5x to 40x Sticker Shock

The per-core metric alone does not explain the extreme cost increases. The full picture involves four compounding factors.

1

Core-Count Explosion

An enterprise that previously licensed 100 CPU sockets now licenses thousands of cores. A 50-host cluster with dual 64-core EPYCs moves from 100 socket licences to 6,400 core licences. Even at a fraction of the per-socket price, the total spend climbs dramatically.

2

Mandatory Bundling

Broadcom consolidated VMware's catalogue from 160+ products into a handful of bundles (VCF and VVF). Many organisations that previously purchased only vSphere Enterprise Plus now find themselves paying for vSAN, NSX, or Aria capabilities they never intended to deploy.

3

Perpetual-to-Subscription Conversion

Perpetual licences are no longer sold and existing SnS contracts are not being renewed. The subscription that replaces them often costs as much as the original perpetual licence itself, annually. Over 5 years, this can represent a 3x to 5x increase in total cost of ownership.

4

List-Price Inflation

Broadcom has raised list prices across the board. Legacy discounts (academic, government, volume-based) have been eliminated or significantly reduced. Customers who previously enjoyed 40 to 60% off list are now being quoted at 10 to 20% off or list price outright.

ScenarioOld Annual CostNew Annual CostIncrease
Mid-size enterprise, 64 cores, basic vSphere$20,000$100,0005x
Public-sector org, 200 cores, legacy perpetual + SnS$100,000$500,0005x
University, 500 cores, no academic discount retained$40,000$500,00012.5x
Large enterprise, 2,000+ cores, full VCF migration$400,000$2,000,0005x
Mini Case Study: Educational Institution Faces 12.5x Increase. A UK university running VMware on approximately 500 cores paid GBP 40,000/year under an academic perpetual licence. Upon renewal, Broadcom quoted GBP 500,000/year at full commercial rates with no academic discount. Collective escalation with peer universities plus an RFP for alternatives (Proxmox, Hyper-V) resulted in a 40% reduction to approximately GBP 300,000/year, still a 7.5x increase. The university is migrating non-critical workloads to Proxmox.

06 The 20% Late-Renewal Penalty

If your VMware subscription expires before you complete the renewal, Broadcom imposes a one-time 20% surcharge on the first year's subscription cost. For context, Microsoft's comparable late-renewal penalty is approximately 3%. Broadcom's is nearly seven times steeper.

The penalty applies when a subscription renewal is processed after the contract's anniversary date. It does not matter whether the delay is two days or two months. On a $500,000/year subscription, that means a $100,000 penalty. On a $2 million contract, it is $400,000.

Mini Case Study: Procurement Delay Triggers $180,000 Penalty. A US manufacturing firm with a $900,000/year VMware subscription was awaiting final CFO sign-off when the renewal deadline passed by 11 days. Broadcom added a $180,000 line item (20% of first-year subscription). The position was firm and contractual. The firm paid the full penalty and now begins all VMware renewal discussions 6 months before expiry.

07 Multi-Year Lock-Ins: Evaluating 3 to 5 Year Commitments

🔴

5-Year Commitment (High Risk)

Best per-core discount but maximum lock-in. Suitable only for organisations with high confidence that VMware will remain their core virtualisation platform through 2030+. Requires robust exit and scale-down clauses.

🟠

3-Year Commitment (Moderate Risk)

The "sweet spot" for most enterprises. Secures meaningful discount while limiting strategic exposure. Aligns with typical IT planning horizons and allows re-evaluation at a reasonable cadence.

🟢

1-Year Subscription (Low Risk)

Maximum flexibility but highest per-core cost and full exposure to annual repricing. Best suited as a bridge while evaluating alternatives or during active migration planning.

Mini Case Study: Global Manufacturer Chooses 3-Year Middle Ground. A multinational with 4,200 licensable cores faced a 1-year renewal quote of $3.2M (4x increase). The 5-year offer was $2.1M/year but required Cloud Foundation including NSX (unused). The CIO negotiated a 3-year vSphere Foundation deal at $2.4M/year with a clause allowing 15% core-count reduction at Year 2. 3-year total: $7.2M vs. projected $9.6M on 1-year path. The scale-down clause was the critical win.

Vendor Shield: Broadcom/VMware Cost Assessment

Our independent advisors assess your VMware core counts, model renewal scenarios, and negotiate on your behalf. Vendor-neutral, fixed-fee advisory that typically reduces renewal costs by 25 to 50%.

Broadcom Advisory Services →

08 Navigating the Most Dangerous Licensing Pitfalls

PitfallTypical Financial ImpactMitigation Strategy
Treating vCPUs as cores50-100% over-purchase or compliance gapAnchor counts to physical host cores; verify HT ratio
Sub-16-core hardware penalty100-300% per-host core inflationRetire/consolidate sub-16-core servers
Late renewal20% first-year surchargeT-180 alerts; pre-authorise renewal budgets
Multi-year over-commitment15-30% wasted spend across termConservative forecasting; scale-down clauses
Bundle composition changesLoss of expected features at renewalContractual product-list exhibit; annual review

09 10-Step Strategic Action Plan

1

Baseline Your Environment Exhaustively

Conduct a full inventory of every VMware host: CPU model, socket count, cores per socket, hyperthreading status, and VMware product deployed. Export from vCenter and cross-reference with your CMDB. This is your single source of truth for all downstream calculations and negotiations.

2

Calculate Your True Licensable Core Count

Apply the 16-core-per-CPU minimum to each host. Sum across the entire estate. Separate the count by site, business unit, or cluster for optimisation opportunities. Compare the total to your current licence entitlement to quantify your gap or surplus.

3

Right-Size Hardware for Licence Efficiency

Identify hosts where the licence cost exceeds the workload value. Consolidate VMs from multiple low-core hosts onto fewer high-core modern servers. Retire sub-16-core hardware aggressively. Model the total-cost-of-ownership (hardware refresh + licence savings).

4

Evaluate Edge and ROBO Alternatives

For small remote-office or edge sites running 1 to 3 VMware hosts, assess whether VMware is still cost-effective. Alternatives like Proxmox, Hyper-V, or KVM may deliver equivalent functionality at a fraction of the licensing cost.

5

Lock Renewal Dates into Organisational Workflow

Implement automated alerts at T-180 and T-90 days. Designate a renewal owner. Pre-authorise budget ranges with finance so that CFO approval is not a last-minute bottleneck. The 20% late-renewal penalty is entirely preventable.

6

Engage Broadcom Early, Not Reactively

Begin renewal conversations at least 6 months before contract expiry. Request indicative pricing and new SKU mappings early. Broadcom's processes can be rigid and slow. Early engagement gives you time to escalate, seek counter-quotes, or find creative deal structures.

7

Negotiate Bundles vs. Components Deliberately

Compare the cost of VCF, VVF, and individual subscriptions against your actual usage. If you need only vSphere and vSAN, VVF may be more economical. If you need vSphere only, push for a component-level deal.

8

Secure Multi-Year Price Protections

If committing to a 3-year term, insist on capped annual increases, scale-down rights (ability to reduce core count at each anniversary), and explicit product-inclusion exhibits. A multi-year deal without these protections is just a longer trap.

9

Maintain a Credible Plan B

You do not need to commit to leaving VMware, but you do need Broadcom to believe it is possible. Pilot an alternative hypervisor in a non-critical environment. Issue an RFP for virtualisation alternatives.

10

Engage Independent Advisory Support

Broadcom's negotiation teams are skilled and well-resourced. Levelling the playing field often requires independent expertise: licence benchmarks, contract-clause analysis, and deal-structure creativity. Redress Compliance specialises in Broadcom advisory services.

10 Audit Preparedness: Staying Compliant

Broadcom has signalled that compliance enforcement will be vigorous. Under per-core licensing, the attack surface for compliance gaps is much larger than under per-socket: a single untracked host, a forgotten DR site, or a miscounted cloud deployment can trigger a non-compliance finding.

📋

Document Core Counts Continuously

Maintain an evergreen register of your licensable core count, updated at least quarterly. Automate extraction from vCenter wherever possible. This register serves as both negotiation data and compliance evidence.

🔎

Avoid Common Audit Triggers

Deploying additional ESXi hosts without corresponding licence additions is the most common trigger. Repurposing a licence from a decommissioned host to a new one without formally updating entitlements is another. Running VMware software after subscription lapse creates exposure.

🔒

Prepare for the Audit Conversation

If Broadcom initiates an audit, your first response should be calm and data-driven. Having your core-count register, licence entitlement records, and contract documentation organised demonstrates compliance maturity and reduces audit scope.

11 Looking Ahead: What CIOs Should Expect

📈

Price Increases Will Continue

Broadcom's revenue targets for VMware have not been achieved in full. Analysts expect annual list-price increases of 5 to 15% on top of already-elevated per-core rates. Multi-year agreements with fixed pricing become more valuable each year.

📦

Bundle Compositions May Shift

Components may move between VVF and VCF or be extracted as paid add-ons. CIOs should assume that what they purchase today may be repackaged at renewal.

🔎

Audit Frequency Will Likely Increase

As the installed base fully transitions to subscriptions, Broadcom will have both the incentive and the data to identify compliance gaps. Proactive management is essential.

🔄

The Alternative Ecosystem Is Maturing

Proxmox, Nutanix AHV, and Microsoft Hyper-V are all benefiting from VMware customer dissatisfaction. While none is a drop-in replacement for VCF, the gap is narrowing for Tier 2 and Tier 3 workloads.

Frequently Asked Questions

Broadcom moved to per-core subscriptions to capture revenue from the dramatic increase in core density in modern processors. Under the old per-socket model, a server with 128 cores paid the same as one with 8 cores. Per-core metering ensures customers with higher-density hardware pay proportionally more. It also supports Broadcom's target of growing VMware revenue from $4.7 billion to $8.5 billion through recurring subscription income.

No. VMware defines a licensable "core" as one physical core on the processor die. Hyperthreading (or AMD SMT) creates two hardware threads per physical core, but only the physical core counts toward licensing. Two vCPUs on a hyperthreaded core equal one licensable core.

Allowing a subscription to expire triggers a 20% late-renewal penalty on the first year's cost when you reinstate. You also lose access to updates, security patches, and technical support. In severe cases, Broadcom may treat the reinstatement as a new sale rather than a renewal, forfeiting any loyalty discounts. Start the renewal process at least 6 months before expiry.

Yes. Perpetual licences you already own remain valid, and you can continue running the software indefinitely. However, Broadcom will not renew support (SnS) contracts on perpetual licences. Once your current support term expires, you lose access to patches, updates, and vendor support. The only options are transitioning to a subscription or engaging a third-party support provider.

Preparation is the primary lever. Come to negotiations with a complete core-count inventory, cost models for multiple scenarios, and a clear target outcome. Multi-year commitments (3 years) typically unlock better per-core rates, but insist on annual price caps and scale-down rights. Demonstrate awareness of alternative platforms and consider engaging an independent licensing advisor for benchmarks and deal-structure expertise.

Take Control of Your VMware Licensing Costs

Redress Compliance provides vendor-neutral VMware and Broadcom advisory services, from core-count audits and cost modelling to full contract negotiation support. Independent, fixed-fee engagements.

Book a Consultation →
FF

Fredrik Filipsson

Co-Founder, Redress Compliance

Co-founder of Redress Compliance, a leading independent advisory firm specialising in Oracle, Microsoft, SAP, IBM, Salesforce, and Broadcom/VMware licensing. With over 20 years of experience across IBM, SAP, and Oracle and 11 years as an independent consultant, Fredrik has helped hundreds of organisations optimise costs, avoid compliance risks, and secure favourable terms with major software vendors.

← Back to Broadcom/VMware Licensing Overview