The VMware by Broadcom Licensing Guide

VMware by Broadcom is now sold only as per-core subscriptions with a 16-core-per-processor minimum, and renewal quotes have run 3x to 10x the prior perpetual-plus-support cost since the 2023 acquisition closed. Broadcom retired perpetual licenses, collapsed thousands of products into a handful of bundles led by VMware Cloud Foundation, and moved every customer to an annual term. This guide sets out how VMware licensing works in 2026: the editions, the per-core math, the core minimums, where the renewal increase comes from, how compliance is enforced, and the realistic exit options to Proxmox, Nutanix, and Hyper-V.

What Broadcom changed

Broadcom completed its acquisition of VMware in November 2023 and rewrote the commercial model within months. Three changes matter most. Perpetual licenses were withdrawn from sale and replaced with subscription only, so the asset you used to own is now rented annually. The product catalog was simplified from a long list of standalone SKUs into a small set of bundles, principally VMware Cloud Foundation and VMware vSphere Foundation. And the licensing metric was standardized on the physical core, with a minimum number of cores charged per processor regardless of the actual core count.

Each change pushes the same direction: higher, recurring, bundle-based spend. A customer that previously bought vSphere standalone on perpetual licenses with annual support now buys a core-based subscription to a bundle that may include components it does not use. The result is the 3x to 10x renewal increases that have defined the post-acquisition period. This page is the pillar for our VMware coverage; the firm-side help sits in our VMware by Broadcom practice.

Customers who hold perpetual VMware licenses are in a particular position. Those licenses do not expire, so an organization can legally continue to run the version it owns indefinitely. What it cannot do is buy new support, receive updates, or add capacity under the old model, because Broadcom withdrew perpetual support renewals. That makes the perpetual estate a depreciating but real asset: it buys time to plan a renewal or a migration on the customer schedule rather than under deadline pressure, which is a stronger negotiating position than most perpetual holders realize they have.

The VCF and vSphere Foundation editions

The portfolio now centers on two bundles. VMware Cloud Foundation (VCF) is the full private-cloud stack, combining vSphere, vSAN storage, NSX networking, and the Aria management suite into one per-core subscription aimed at customers running a complete software-defined data center. VMware vSphere Foundation (VVF) is the smaller bundle for customers that need compute virtualization and core management without the full networking and storage stack. Below those sit limited editions such as vSphere Standard and vSphere Essentials Plus for small environments.

The edition choice is the largest single cost lever, because VCF carries the most components and the highest per-core price while many customers only use the vSphere and vSAN parts. Buying VCF for a workload that needs VVF is the most common way to overspend on Broadcom. The detail on each bundle is in our VMware Cloud Foundation licensing guide and our vSphere Foundation pricing guide.

Per-core subscription pricing

Every current VMware edition is priced per physical core per year, on subscription. You count the physical cores in every processor running the software and multiply by the per-core list rate for the edition, subject to the core minimum described below. Because the metric is the physical core, modern high-core-count processors increase the bill directly: a server with two 32-core processors carries 64 licensable cores, and the same workload on older 16-core processors would have carried half that. The per-core model rewards consolidation onto fewer, smaller-core hosts, which is the opposite of the density strategy many data centers pursued under perpetual licensing.

List rates differ by edition, with VCF the highest and the vSphere editions lower, and Broadcom discounts against those rates by volume and term. The mechanics and current rate bands are in our VMware per-core licensing guide and our 2026 subscription pricing guide. The key discipline is to count cores accurately and license the edition each workload actually needs, because both the core count and the edition are negotiable inputs, not fixed facts.

A worked example makes the per-core math concrete. Take a six-host cluster, each host with two 24-core processors, so 288 physical cores. On VMware Cloud Foundation that full core count is licensed annually, and at a representative discounted rate the subscription runs into the high six figures every year, recurring. On vSphere Foundation, for the same cores where the full stack is not needed, the per-core rate is materially lower and the annual figure falls accordingly. The same 288 cores therefore carry very different costs depending only on the edition chosen, which is why the edition decision dominates every other lever on the per-core model.

Core minimums and counting

Broadcom applies a minimum of 16 cores per processor. A processor with fewer than 16 physical cores is still licensed as 16, so an 8-core processor is billed at 16 cores, doubling its effective rate. This minimum is a frequent source of overcharge on older or smaller hardware, and it is a direct argument for consolidating workloads onto processors at or above 16 cores so no licensed capacity is wasted on the minimum. The counting rules and the minimum are detailed in our per-core licensing guide.

The other counting trap is licensing every core a workload could run on rather than the cores it does run on. In a cluster with vMotion or DRS enabled, a conservative reading licenses all hosts the workload can move to. Confirming which hosts are actually in scope, and segmenting clusters where appropriate, is part of right-sizing the core count. The table shows how the minimum and the counting basis affect a worked example.

VMware Cloud Foundation pricing

VMware Cloud Foundation is the premium bundle and the one Broadcom pushes hardest, because it carries the most components and the highest per-core rate. For an organization genuinely running vSphere, vSAN, NSX, and Aria together, VCF can be cost-effective against buying those capabilities separately. For the larger group that uses vSphere and perhaps vSAN but not NSX or the full Aria suite, VCF means paying for shelf-ware bundled into the per-core rate. The full pricing breakdown is in our VMware VCF pricing guide.

The right test for VCF is component utilization. Map which of the bundled components each cluster actually runs, and if NSX and Aria are unused, price VVF against VCF before accepting the larger bundle. Broadcom will present VCF as the default; the buyer decision is whether the bundled components justify the premium for the specific estate, not in general. A short audit of which clusters genuinely consume the networking and management layers usually settles the question quickly, and it is the first analysis any VMware customer should run before a renewal.

vSphere Foundation pricing

VMware vSphere Foundation is the mid-tier bundle for customers that need compute virtualization and core management without the full private-cloud stack. It includes vSphere and the core management tooling, with a smaller vSAN entitlement than VCF, at a lower per-core rate. For many traditional virtualization estates that used vSphere Enterprise Plus on perpetual licenses, VVF is the natural subscription equivalent and a meaningful saving against being moved to VCF by default. The detail is in our vSphere Foundation pricing guide.

The decision between VVF and VCF is the single most consequential pricing choice a VMware customer makes in 2026. It is worth modeling carefully, because the per-core difference compounds across every licensed core in the estate and across the multi-year term. Where a workload needs only compute and management, VVF is the correct license, and accepting VCF for it is pure overspend.

Support changes and reduction

Under the subscription model, support is bundled into the per-core subscription rather than sold as a separate maintenance line, so the old lever of dropping support while keeping perpetual licenses no longer exists. What remains negotiable is the support tier and the response commitments inside the subscription, and whether premium support that is paid for is actually used. Many estates carry a higher support tier than their operations require, which is a reduction available at renewal. The strategies are in our Broadcom support reduction strategies guide.

For environments that have stabilized and no longer need vendor updates, the deeper support question merges with the exit question: a stable estate that will be migrated within the term may not need a premium subscription at all for its remaining life. That calculation belongs in the renewal and exit planning, covered below. The practical step is to inventory the support tier actually purchased against the response times the business genuinely needs, because the gap between the two is recurring spend that delivers nothing.

Renewals and price increases

The renewal is where the model change becomes a cash event. A customer whose perpetual licenses and annual support previously cost a certain amount now receives a subscription quote that, on like-for-like capacity, commonly runs 3x to 10x that figure. The increase is driven by the move from a one-time license plus modest support to a recurring core-based subscription, often to a larger bundle than the workload needs. The renewal mechanics and defense are in our VMware renewal negotiation guide and the post-acquisition changes in our Broadcom VMware licensing changes guide.

A short worked renewal illustrates the shock and the defense together. A mid-size customer running a 200-core estate previously paid a perpetual license amortized over years plus annual support, an effective cost in the low hundreds of thousands. The Broadcom subscription quote for the same 200 cores on full VCF arrives several times higher, recurring every year with no perpetual asset to show for it. Right-sized to vSphere Foundation, with the core count validated and a multi-year cap negotiated, the same renewal lands far closer to the prior cost. The difference between the two outcomes is entirely the edition, the counting, and the negotiation, none of which is fixed by Broadcom.

The increase is not a fixed fact. It is the product of the edition, the core count, the term, and the support tier, every one of which is negotiable. A renewal worked 120 days ahead, with the core count validated and the edition right-sized, settles far below the opening quote. The firm-side negotiation is our VMware by Broadcom negotiation practice.

Compliance and audits

Broadcom has the contractual right to verify VMware deployment, and the per-core subscription model makes the core count the focus of any review. The compliance risk concentrates in two places: under-counted cores where the licensed subscription does not cover all hosts the software runs on, and edition mismatches where a higher-function component is in use without the corresponding entitlement. Because the metric is the physical core, a compliance gap is straightforward for Broadcom to compute and to price, which raises the stakes on accurate counting. The defense is in our VMware audit defense practice.

The same discipline that controls cost controls compliance: maintain an accurate, current inventory of hosts, cores, and the editions in use, reconciled to the subscription entitlement. An organization that holds its own validated core inventory enters any review from strength and avoids the over-counting that a vendor measurement tends to produce.

Exit options and migration

The scale of the Broadcom increase has made migration a mainstream consideration rather than a fringe one. Three alternatives carry the most weight in 2026. Proxmox VE is an open-source hypervisor with no per-core license fee and optional paid support, suited to organizations comfortable with a Linux-based platform. Nutanix offers an integrated hyper-converged platform with its own commercial model that many buyers find more predictable than Broadcom subscriptions. Microsoft Hyper-V is available to organizations already invested in Windows Server and Azure. The trade-offs are set out in our VMware exit strategy guide.

None of these is a drop-in replacement, and the right choice depends on the existing platform, the in-house skill base, and the workloads involved. Migration is a project, not a switch, and the realistic timeline runs months not weeks, dominated by testing and operational re-tooling rather than the move itself. The detail for the two most common paths is in our VMware to Proxmox migration guide and our VMware to Nutanix migration guide. Even where migration is not executed, a costed and timelined exit plan is the strongest position a customer holds at the Broadcom renewal, because it removes the assumption that the customer is captive.

Negotiation strategy

The Broadcom renewal is a negotiation, not a fixed quote, and the levers are specific to the new model. Right-size the edition from VCF to VVF where the bundled components are unused. Validate the core count and dispute any host counted that is out of scope. Hold a costed exit plan as the alternative. Time the deal to Broadcom fiscal period close, which falls at the end of October, where the discount flexibility concentrates. And commit to term only against a fixed multi-year price ceiling so the year-two and year-three increases are capped in advance.

These levers work together. The edition and core-count work establishes the technical floor, the exit plan establishes the walk-away, and the timing establishes the discount window. Applied 120 days ahead by advisors who priced these deals inside the vendor, they routinely settle the opening increase well below where it started. The engagement is our VMware by Broadcom negotiation practice and the wider software licensing advisory service.

One further consideration is the cloud and hosted route. Broadcom also offers VMware Cloud Foundation through hyperscaler and partner programs, where the same software runs on a provider platform under a consumption or committed model rather than on owned hardware. For some workloads this shifts capital cost to operating cost and removes the hardware refresh question, but it does not remove the per-core economics, so the edition and capacity discipline still applies. The hosted option is worth pricing alongside the on-premises subscription and the migration alternatives, because for a subset of estates it is the lowest-friction way to reduce the immediate renewal pressure while a longer-term platform decision is made.

The 2026 action plan

For any organization running VMware in 2026, the sequence is the same. Build an accurate inventory of hosts, physical cores, and the editions and components actually in use, because that inventory drives both cost and compliance. Decide the correct edition per cluster, defaulting to VVF unless the full VCF stack is genuinely used. Validate the core count against the minimum and the scope rules. Cost a realistic exit to Proxmox or Nutanix as both a planning option and a negotiating position. And start the renewal 120 days ahead, timed to the Broadcom quarter, with a multi-year price cap as the goal.

Done together, these steps turn a 3x to 10x shock into a controlled, capped cost or a planned migration. Start with the area most pressing for your estate: VCF licensing, per-core licensing, renewal negotiation, or the exit strategy. For engagement help, our VMware by Broadcom practice covers negotiation, audit defense, and migration end to end.