VMware Cloud Foundation Licensing: Bundle Analysis for Enterprise IT

What VCF Is and Why Broadcom Moved to It

VMware Cloud Foundation is Broadcom's mandatory infrastructure subscription that replaced the previous VMware product portfolio for most enterprise customers. Prior to the acquisition, enterprises could purchase vSphere, vSAN, NSX, and vRealize Suite as separate products, scaling each to their specific needs. VCF bundles these products together into a single per-core subscription, making the individual components unavailable for separate purchase in standard enterprise agreements.

Broadcom's rationale for the bundled model is straightforward from a commercial perspective: it eliminates the ability of enterprise procurement teams to optimise spend by buying only the components they use. Under the old model, an enterprise running only vSphere and vSAN could buy just those two products. Under VCF, they pay for the full bundle — including NSX and Aria Suite — whether they use those components or not.

What the VCF Bundle Includes

VCF consolidates four major VMware product families into a single subscription entitlement:

What VCF Does Not Include

Understanding what is excluded from VCF is as commercially important as understanding what is included. The following are not covered by a standard VCF subscription and require additional licensing:

VCF Editions Compared

Broadcom offers VCF in multiple editions, with the principal commercial distinction relating to the Aria Suite components included and the NSX tier:

How Broadcom Prices VCF Per Core

VCF is licensed by the physical core. Every physical CPU core in every host covered by the VCF subscription is counted. Broadcom's per-core pricing model has several characteristics that enterprise procurement teams need to understand:

Minimum Core Count Per Host

Broadcom requires a minimum number of cores per physical host — typically 16 cores per host — regardless of the actual physical core count of the server. This minimum has a meaningful cost impact for enterprises with older, lower-core-density servers, where the licensed core count exceeds the physical count.

All Clusters Must Be Covered

Standard VCF agreements require that all hosts running VCF components within a defined managed environment are covered. Broadcom's position is that selective cluster coverage creates compliance risk — only fully separated environments (separate vCenter instances, network segments, and management infrastructure) can be excluded from the core count. Development and disaster recovery environments are a critical negotiation point here.

Core Count Validation Is Critical

Broadcom's initial VCF proposals are built from their own records — which frequently include decommissioned hardware, double-count servers acquired through M&A, and may not reflect actual physical deployments. Independent core count validation typically identifies 15–35% fewer cores than Broadcom's initial proposal. Since VCF is priced per core with a 3-year commitment, a 20% reduction in core count translates to a 20% reduction in total contract value — compounded annually. This is the single highest-value action in any VCF negotiation.

Bundle Cost Traps to Know

The following are structural commercial risks that enterprises most frequently encounter when signing VCF agreements without independent advisory:

Paying for Unused Bundle Components

Organisations that historically ran only vSphere and vSAN — and did not deploy NSX or vRealize — are now paying for NSX and Aria Suite as part of VCF. If those components are not deployed, they represent pure cost with no operational value. The counter is to either negotiate the VCF Standard edition (which limits Aria scope) or to negotiate specific credit provisions against unused components.

Annual True-Up Exposure

Standard VCF agreements include annual true-up provisions requiring customers to pay for any additional cores deployed during the year. Without explicit contractual caps on true-up additions, hardware refreshes or server expansions can generate unexpected year-over-year cost increases. Negotiate a fixed core count with defined expansion options rather than an open-ended true-up obligation.

Escalation Clause Risk

Broadcom's standard VCF agreements include annual price escalation clauses — typically 3–6% per year on subscription pricing. Over a 3-year term, this compounds into a 9–19% total price increase built into the contract structure. Enterprise accounts have negotiated escalation caps — typically 2–3% or CPI-linked — or eliminated escalation entirely for the initial term. This is a material negotiation point that is frequently overlooked.

For the complete negotiation framework, see our VMware/Broadcom Complete Guide and the VMware Broadcom Survival Guide.

Negotiating the VCF Bundle

The most commercially effective VCF negotiation strategy addresses three dimensions simultaneously: what you buy, how many cores are licensed, and the contract terms governing future costs.

Edition Selection

Start from the lowest applicable edition and force Broadcom to justify upward. If your organisation uses vRealize Automation and vRealize Operations Advanced today, VCF Advanced may be appropriate. If you run only vSphere and vSAN, VCF Standard is the defensible starting point. Do not accept Broadcom's proposed edition without an independent component-by-component entitlement mapping against your current usage.

Core Count Negotiation

Commission an independent physical inventory before engaging Broadcom's migration team. Validate the core count against physical host records, decommission documentation, and vCenter inventory exports. Challenge every host Broadcom proposes to include, and negotiate explicit exclusion provisions for DR, dev, and test environments at reduced rates.

Contract Protections

The following contract terms should be non-negotiable in any VCF agreement: annual escalation cap (2–3% maximum), true-up cap (defined ceiling on annual additions), hardware decommission credits (ability to reduce core count when hosts are decommissioned), and technology refresh provisions (migration credits when upgrading to higher-density servers).

Related articles: VMware Subscription Migration Guide · Broadcom Support Changes · vSphere Licensing Under Broadcom