Editorial photograph of a virtualized data center during a VMware licensing review
Broadcom VMware / Licensing

VMware Cloud Foundation licensing. After Broadcom.

Broadcom moved VMware to a subscription, per core model with a minimum core count per processor. For many estates the bill rose sharply. The buyer question is how to license to real consolidation, not to the old socket count.

Contact Us Broadcom VMware Practice
500+Enterprise clients
$2B+Under advisory
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

VMware Cloud Foundation licenses per core on subscription under Broadcom, with a core minimum per CPU. Understanding the cost shift is the first step to controlling it.

Key takeaways

  • Broadcom consolidated the VMware portfolio into VMware Cloud Foundation and VMware vSphere Foundation.
  • Licensing moved from perpetual to subscription, and from per processor to per core.
  • A minimum core count applies per physical CPU, so lightly populated sockets still incur a floor.
  • Many estates saw a large cost increase at the first Broadcom renewal versus the old perpetual plus support model.
  • License to real consolidation density. Fewer, denser hosts can lower core counts if your workloads allow it.
  • Model the exit honestly. The threat of migration is only leverage if the migration is genuinely viable.

Broadcom completed its acquisition of VMware and reshaped the portfolio. The product list shrank to a small number of bundles, and the licensing model changed at the same time.

The combined effect was a step change in cost for many estates. Understanding the new metric is the first move toward controlling the renewal.

How does VMware Cloud Foundation license in 2026?

VMware Cloud Foundation is now a subscription bundle licensed per core. Each physical CPU carries a minimum core count, so even a lightly populated socket is licensed to that floor.

Broadcom describes the consolidated portfolio on its cloud infrastructure pages. The two anchor offers are Cloud Foundation and vSphere Foundation, with the broader bundle aimed at full private cloud.

What changed from the old model

  • Perpetual to subscription: licenses now expire and renew rather than persist.
  • Per processor to per core: counts scale with cores, not sockets.
  • Core minimum per CPU: a floor applies to every physical processor.

VMware licensing: old model versus Broadcom model (2026)

DimensionOld VMware modelBroadcom modelBuyer impact
TenurePerpetual plus supportSubscriptionRecurring cost
MetricPer processorPer coreScales with cores
MinimumPer socketCore floor per CPUPenalizes light sockets
PortfolioMany productsTwo main bundlesLess granular buying

Why did the bill rise so much for many estates?

Three changes stacked. Subscription replaced a paid up perpetual base. Per core counting raised the unit basis on dense processors. The core minimum penalized estates with many lightly used sockets.

The acquisition itself was confirmed through Broadcom investor communications, and the portfolio simplification followed quickly. For buyers, the practical result was a renewal that no longer resembled the prior quote.

Where the increase concentrates

  • High core count CPUs that now drive higher per core totals.
  • Servers with one populated socket but a full core minimum.
  • Editions bundling features the estate does not use.

How can a buyer reduce licensable cores?

The metric rewards density. Consolidating workloads onto fewer, fully populated, high utilization hosts can lower the total core count you must license, provided the workloads tolerate it.

VMware documents the platform capabilities on its vSphere product pages. Use the platform to raise consolidation ratios, then license to the consolidated footprint, not the legacy sprawl.

Levers that move core counts

  • Raise consolidation density where workloads allow.
  • Retire underused hosts and lightly populated sockets.
  • Match the edition to the features actually in use.

Is a VMware exit real leverage at renewal?

Migration alternatives exist, from other hypervisors to cloud native platforms. They are credible for some estates and a fantasy for others. The leverage is only real if the move is genuinely viable for you.

Model the true cost and timeline of an exit before you wave it at Broadcom. A bluff is easy to call. A costed, phased migration plan changes the renewal conversation because it is real. Track the portfolio direction through the VMware Cloud Foundation blog.

Where the common advice on VMware Cloud Foundation is wrong

The common reaction to the Broadcom model is to threaten an immediate exit to another hypervisor as the main negotiating lever. We disagree. In roughly 20 to 30 renewals we benchmarked, an uncosted exit threat was easily dismissed by the account team, while estates that optimized consolidation density first cut licensable cores by 15 to 35 percent before discount. The exit is real leverage only when it is a costed, phased, genuinely viable plan. The buyer side move is to license to consolidated reality, build a credible migration model in parallel, and use both together. Density that you can prove beats a migration threat you cannot execute.

Infrastructure team modeling VMware host consolidation and per core license counts
Under per core licensing, consolidation density, not socket count, is the number that decides the renewal.
2 to 5x
First renewal vs prior support
15 to 35%
Cores cut by consolidation
20 to 30
VMware renewals benchmarked

Source: Redress Compliance advisory engagement file, 2024 to 2025.

Per core licensing rewards density and punishes sprawl. The estate that consolidates before it renews controls the number. The one that does not pays the floor.

What to do next

  1. Inventory every host, its CPUs, and the populated and total core counts.
  2. Model your licensable cores under the per core metric with the CPU minimum applied.
  3. Identify lightly populated sockets and underused hosts to consolidate or retire.
  4. Raise consolidation density where workloads tolerate it, then recount cores.
  5. Match the bundle edition to the features your estate actually uses.
  6. Build a costed, phased exit model in parallel and bring both to the renewal.
Cover of the VMware Cloud Foundation Licensing Guide white paper from Redress Compliance

White Paper · Broadcom / VMware

VMware Cloud Foundation Licensing Guide

What VMware Cloud Foundation actually costs per core under Broadcom: the 16 core minimum, the embedded entitlement math, and the levers that cap it. Read it free.

Read the white paper

Frequently asked questions

How does VMware Cloud Foundation license under Broadcom?

VMware Cloud Foundation is a subscription bundle licensed per core, with a minimum core count applied to each physical CPU. Licenses now renew rather than persist as the old perpetual licenses did.

What changed from the old VMware licensing model?

Three things changed together: perpetual licensing became subscription, per processor counting became per core, and a core minimum now applies to every physical CPU regardless of how many cores are populated.

Why did my VMware bill increase so much?

The subscription model, per core counting, and the per CPU core minimum stacked together. Estates with high core count processors or many lightly populated sockets saw the largest increases at the first Broadcom renewal.

What is the core minimum per CPU?

Broadcom applies a floor on the number of cores licensed per physical processor. Even a CPU running fewer cores than the floor is licensed to that minimum, which raises counts on lightly populated sockets.

How can I reduce my VMware core count?

Consolidate workloads onto fewer, denser, fully populated hosts where the workloads allow it, retire underused hosts, and match the edition to the features in use. License to the consolidated footprint, not the legacy sprawl.

Is migrating off VMware a credible negotiation lever?

Only if the migration is genuinely viable for your estate. A costed, phased migration plan changes the conversation. An uncosted threat is easily dismissed by the account team.

What is the difference between Cloud Foundation and vSphere Foundation?

Cloud Foundation is the broader private cloud bundle, while vSphere Foundation is the smaller compute focused offer. Match the bundle to the capabilities you actually deploy rather than buying breadth you will not use.

When should I start planning a VMware renewal?

Begin well before the term ends. Inventory cores, model the new metric, optimize consolidation, and build any exit case early, so you negotiate from evidence rather than reacting to the quote.

VMware Renewal Review

The full vmware renewal review from the Broadcom VMware Practice.

VMware Cloud Foundation per core costing, subscription renewal posture, exit options, and the buyer side moves across the VMware estate.

Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.

No spam. We will only email you about this download. Privacy.
Run the software spend health check against your VMware estate in under five minutes.
Open the Tool →
Per core
New metric
Subscription
New tenure
Core floor
Per CPU
Density
The lever
100%
Buyer Side
Related reading

More from the Broadcom VMware Practice

Broadcom VMware Practice →
Talk to an advisor

Put a buyer side advisor on your side of the table.

We sit on your side when you negotiate with the major software publishers. Independent, benchmarked, and built for the renewal in front of you.

Contact Us
Newsletter

VMware Cloud Foundation licensing in 2026 and the moves that follow it.