Broadcom VMware Hub
VMware vSphere Foundation (VVF) licensing. The 2026 reference.
VVF changed how vSphere licenses, with per core minimums and a new bundle split. Read the metric before the Broadcom renewal quote sets the agenda.
VVF changed how vSphere licenses, with per core minimums and a new bundle split. Read the metric before the Broadcom renewal quote sets the agenda.
VMware vSphere Foundation licenses per core with a per core minimum, so the core count and the VVF versus VCF choice decide most of a 2026 Broadcom bill.
VMware vSphere Foundation, or VVF, is the packaged offering that bundles vSphere with management and a defined feature set under Broadcom. It sits below the larger VMware Cloud Foundation, or VCF, in scope and price.
Broadcom describes the packaging on the vSphere product page. The full stack comparison sits on the VMware Cloud Foundation product page. The key change is that licensing moved to a per core subscription, so the old per socket math no longer applies.
Perpetual licenses with optional support became subscriptions you must renew. That converts a sunk cost into a recurring commitment, which makes right sizing the core count an ongoing discipline rather than a one time exercise.
VVF licensing, how the core math works
| Element | How it bills | Buyer impact |
|---|---|---|
| Per core license | Each physical core counted | Core count is the price |
| Per core minimum | Floor applied per processor | Raises effective rate on small CPUs |
| Subscription term | Annual or multi year | Recurring spend to manage |
| Bundle choice | VVF or VCF | Scope drives the unit price |
VVF counts every physical core in each licensed processor, and Broadcom applies a minimum core count per processor. On CPUs below that floor you pay for the minimum regardless of actual cores.
The minimum lifts the effective cost on hosts with lower core processors. Broadcom sets the floor in its licensing terms, summarized through the VMware Cloud Foundation page. Estates with many small CPUs feel it most.
Pull the core inventory from the hypervisor and reconcile it against hosts you actually need. Many estates carry capacity that consolidation can retire before the count is fixed for renewal.
The standard advice is to buy VCF so you are covered for every future capability. We disagree. In roughly 30 of the VMware estates we benchmarked, VCF was bought for features used on a small slice of hosts, yet the full bundle was paid across every core. A premium bundle applied to cores that never touch the premium features is pure waste. The buyer side move is to license VVF for the general estate and add VCF only where the advanced features are evidenced, then negotiate the core count down through consolidation first.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Under Broadcom the question is no longer how many sockets you have, it is how many cores you can justify keeping switched on.
The choice is the largest single lever in a 2026 VMware deal. VVF covers the general virtualization estate, while VCF adds the full private cloud stack at a higher per core cost.
VCF fits where you run the integrated private cloud with software defined networking and storage at scale. Broadcom positions both tiers through its corporate news room, which is worth tracking for packaging changes.
VVF licenses per physical core on a subscription, not per socket or per VM. Broadcom counts every core in each licensed processor and applies a per core minimum, so the total core count is the primary driver of the bill.
Broadcom applies a minimum number of licensed cores per processor. On CPUs below that floor you pay for the minimum regardless of actual cores, which raises the effective rate on hosts with lower core processors.
VVF is the smaller bundle covering vSphere and core management, while VCF is the full VMware Cloud Foundation private cloud stack at a higher per core cost. The choice between them is the largest single cost lever.
Yes. Under Broadcom, perpetual licenses with optional support were replaced by subscriptions. That converts a one time cost into a recurring annual commitment, making ongoing right sizing of the core count essential.
Audit the physical cores from the hypervisor and consolidate workloads onto fewer, larger hosts before renewal. Many estates carry 10 to 25 percent of cores on hosts that consolidation can retire, cutting the licensed count.
Usually not across the whole estate. Buying VCF for features used on a fraction of hosts pays the premium on every core. License VVF for the general estate and add VCF only where the advanced features are evidenced.
Yes, in effective rate terms. Higher core processors spread the fixed per core minimum across more cores, lowering the effective cost, while many small CPUs each hit the floor and pay for cores they do not have.
Size it against a consolidation plan, not today's core count. A multi year term can lower the rate but locks in the cores you commit, so reduce the count first and then commit to the smaller, audited number.
Per core minimum math, the VVF versus VCF decision, core count audits, and the buyer side levers that move a Broadcom renewal.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
