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

The Model That Changed Everything

Broadcom completed its acquisition of VMware in November 2023 and moved immediately to restructure the commercial model. All VMware perpetual licences were discontinued in early 2024. The product portfolio was consolidated from approximately 8,000 SKUs to a small number of bundled subscription offerings — principally VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF), with vSAN Foundation available as an add-on. Every new subscription is metered on a per-core basis.

The shift was deliberate and commercially significant. VMware's prior per-socket model charged organisations based on the number of physical processors in their environment, regardless of how many cores each processor contained. As CPU density grew — modern server processors now commonly ship with 24, 32, 48, or even 64 cores per socket — per-socket licensing became increasingly favourable for customers. Broadcom's per-core model reverses this dynamic entirely, ensuring that every core generation advance increases the vendor's revenue rather than benefiting the customer.

Understanding this per-core model in detail is no longer optional for IT leaders with VMware in their environment. The commercial implications are too significant — and the alternatives too consequential — to leave to a reactive renewal discussion.

How the Per-Core Model Works

The core-based licensing model appears straightforward in concept but contains several critical rules that the published documentation does not prominently surface. Getting the calculation right requires understanding all of them.

What Counts as a Licensable Core

A licensable core is a physical processor core — not a logical core and not a hyperthread. A processor with 16 physical cores and hyperthreading enabled (presenting 32 logical processors to the operating system) counts as 16 licensable cores, not 32. This distinction is important because many infrastructure inventory tools report logical processor counts by default. Organisations relying on hyperthread counts rather than physical core counts will systematically overestimate their licensing requirement and overpay.

Broadcom's published guidance confirms that only physical cores are counted: "A core is a physical processor core. Hyperthreaded logical processors are not counted." Infrastructure teams must be diligent in verifying that their core count methodology aligns with this definition before any commercial engagement with Broadcom.

The 16-Core Minimum Per Socket

This is the most commercially significant rule in Broadcom's per-core model — and the one that produces the most unexpected cost impact for organisations with older or lower-density server hardware. Broadcom's licensing terms impose a minimum of 16 cores per CPU socket, regardless of the actual physical core count of the installed processor. If a server contains a processor with 4, 8, or 12 physical cores, it is still licensed as if it has 16 cores.

The practical impact of this rule is substantial in environments with older server generations. Consider a host server with two 8-core processors (16 physical cores in total). Under the per-core model, the server is licensed for 32 cores — two sockets at 16 cores each — rather than the actual 16 physical cores present. The customer is paying for 16 cores that do not physically exist. For large environments with significant numbers of older, lower-density hosts, the gap between actual core count and licensable core count can represent 30 to 50 percent of the total licence fee.

The Bundling Requirement

Broadcom no longer sells individual VMware products. VMware Cloud Foundation bundles vSphere, vSAN, NSX networking, Aria management tools, and HCX migration capabilities together in a single per-core subscription. VMware vSphere Foundation bundles vSphere and the Tanzu Kubernetes Grid runtime. Organisations that previously licensed only vSphere, or only vSphere and vSAN without NSX, are now compelled to pay for capabilities they did not previously use and may have no need for.

The effective per-core cost of the bundle therefore exceeds the effective per-core cost of the previous narrower licence scope — even before accounting for the core count inflation produced by the 16-core minimum rule. The combination of these two factors (broader scope requirement and higher minimum core count) is what drives the 3x to 5x cost increases that dominate VMware renewal discussions.

Calculating Your Per-Core Exposure

A reliable per-core cost calculation requires a thorough infrastructure inventory covering every host in scope. The following methodology produces an accurate baseline for commercial planning.

Step 1: Physical Core Inventory

Inventory every vSphere host in the environment, recording the number of physical CPU sockets and the number of physical cores per socket. Do not use logical processor or hyperthread counts. In environments where VMware vCenter is deployed, the physical core count is available directly from the vCenter hardware inventory — it is the "CPU Cores" value in the host hardware summary, not the "CPU Threads" value.

Step 2: Apply the 16-Core Minimum

For each socket on each host, take the higher of the actual physical core count and 16. Sum the adjusted core counts across all sockets. This gives the total licensable core count for the environment. The difference between actual physical cores and licensable cores — produced by the 16-core minimum — represents the phantom core cost that organisations should understand before entering any renewal negotiation.

Step 3: Apply Bundle Pricing

Broadcom does not publish standard per-core prices, but benchmarked market rates for enterprise renewals at volume place VMware Cloud Foundation at approximately $60 to $100 per core per year at list, with negotiated rates for large environments ranging from $45 to $75 per core per year. VMware vSphere Foundation is priced lower at approximately $30 to $55 per core per year at enterprise volume. Multiply the licensable core count by the applicable per-core rate to produce an annual subscription cost estimate.

This estimate should then be compared directly to the prior-year maintenance cost for the same environment. The ratio of new subscription cost to prior maintenance cost is your effective cost increase factor — typically between 3x and 5x for most enterprise environments, with environments dominated by older, lower-density hardware experiencing higher ratios due to the 16-core minimum rule's disproportionate impact.

The Late Renewal Penalty

Broadcom has introduced an additional commercial mechanism that punishes organisations who allow their VMware subscriptions to lapse past the anniversary date. A 20 percent penalty is applied to the first-year subscription price for any renewal that is not completed by the contract anniversary. This penalty is applied before the annual subscription is invoiced — it is not a separate line item but an uplift on the first-year cost.

The practical implication is that organisations should begin renewal discussions at least three months before their anniversary date, even if they are evaluating alternatives. The cost of allowing the subscription to lapse while the alternative evaluation is in progress can be significant. If the alternative evaluation concludes in favour of continued VMware, the penalty cost will have been incurred unnecessarily. Securing a short extension to the current terms while the evaluation is completed — even at a modest administrative cost — is commercially preferable to incurring the renewal penalty.

Strategic Alternatives Worth Evaluating

The Broadcom pricing restructure has dramatically accelerated the business case for VMware alternative evaluation. Two platforms in particular have become the most commercially credible alternatives for enterprise environments: Nutanix and Azure VMware Solution.

Nutanix

Nutanix provides a hyperconverged infrastructure platform (AHV hypervisor, Nutanix Cloud Clusters compute, and Nutanix unified storage) that is a genuine functional alternative to VMware vSphere plus vSAN for most enterprise workloads. Nutanix's commercial model is hypervisor-plus-storage subscription, priced on a per-node or per-core basis. At current market rates, Nutanix's total per-core cost is materially lower than Broadcom's VMware Cloud Foundation pricing, and Nutanix's hypervisor (AHV) is included in the platform subscription at no additional cost — unlike VMware's separate vSphere and NSX licensing.

The migration challenge from VMware to Nutanix is real but well-understood. Nutanix provides migration tooling, and large infrastructure consultancies have mature VMware-to-Nutanix migration methodologies. Organisations with standardised workload environments — where VMs run standard operating systems without complex VMware-specific dependencies — typically find the migration manageable within a 12 to 18 month horizon.

Azure VMware Solution

Microsoft's Azure VMware Solution (AVS) provides a fully managed VMware environment running on Azure dedicated hardware. For organisations that are committed to Microsoft Azure as their strategic cloud platform, AVS provides a path to run existing VMware workloads on Azure infrastructure without re-platforming — while shifting the commercial relationship from Broadcom to Microsoft. VMware licences are included in the AVS pricing, and the per-hour pricing model provides consumption-based flexibility that is absent from Broadcom's annual subscription model.

AVS is most compelling for organisations with existing Azure infrastructure and a strategic commitment to the Microsoft cloud platform. It is less compelling for organisations with predominantly on-premises infrastructure and no strategic Azure direction, where the operational and commercial model of a hyperscaler managed service introduces complexity that on-premises Nutanix avoids.

Negotiating with Broadcom Under the New Model

Broadcom's approach to VMware renewals has been characterised by reduced flexibility compared to the VMware era. Large deal teams at Broadcom have explicit approval authority for discounts, but the ceiling on negotiated discounts is lower than customers previously experienced. The following negotiation principles apply in the current environment.

The most powerful leverage is a credible alternative evaluation. Broadcom knows that Nutanix and Azure VMware Solution are credible alternatives for enterprise environments, and a well-evidenced alternative evaluation — with proof of vendor engagement and preliminary pricing — materially improves Broadcom's commercial flexibility. Without this leverage, Broadcom account teams have limited incentive to discount below their standard enterprise terms.

Multi-year commitments unlock higher discounts but lock in costs during a period when the competitive landscape is evolving rapidly. A three-year VMware Cloud Foundation commitment at a negotiated discount may appear attractive in isolation but forecloses the option to migrate to a lower-cost alternative during the commitment period. Organisations should model the cost of staying versus migrating over the commitment period before accepting a multi-year lock-in as a discount mechanism.

The infrastructure right-sizing exercise — accurate core counting that applies the 16-core minimum correctly — is the baseline for any commercial engagement. Organisations that enter Broadcom negotiations without a verified physical core inventory consistently pay for more licensable cores than their environment requires. The time investment in a thorough inventory audit pays for itself many times over in the renewal negotiation.