VMware Cloud Foundation Licensing: Bundle Analysis

What Is VMware Cloud Foundation?

VMware Cloud Foundation (VCF) is Broadcom's primary enterprise software subscription offering for data centre infrastructure. It replaces the portfolio of standalone VMware products that organisations could previously purchase individually — vSphere, vSAN, NSX, and the vRealize/Aria management suite — with a single, bundled, per-core subscription that must be purchased for every eligible core in scope.

VCF is positioned by Broadcom as the natural successor to vSphere Enterprise Plus + add-on products, and for organisations that previously ran the full VMware stack, it represents genuine product consolidation. The commercial challenge is that VCF is the required path for almost all enterprise renewals, regardless of which VMware products an organisation actually needs. An organisation that only ran vSphere compute without vSAN or NSX will find themselves in VCF (or VVF) territory with no option to purchase a compute-only licence at a comparable price to the old vSphere Standard.

This article provides a detailed analysis of the VCF bundle, what it contains, what it forces you to purchase, and how to use the bundle structure strategically in negotiations. For the overall commercial and strategic context, see the Broadcom VMware Licensing Guide.

VCF vs VVF: Which Applies to You?

Broadcom currently offers two primary enterprise subscriptions: VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF). Understanding which applies to your environment is the starting point for any commercial analysis.

Broadcom's commercial default is to position VCF for all renewals where any vSAN or NSX was previously in use. This maximises Broadcom's per-core revenue but may not reflect the genuine product requirements of every customer. Organisations that used vSAN only in a limited capacity (e.g., a single vSAN cluster for one workload tier) should challenge whether VCF is required across their entire environment or whether a hybrid VCF/VVF or VVF-only approach can reduce costs without functional compromise.

Complete VCF Bundle Contents

The VCF bundle as of early 2026 includes the following components. This list reflects the standard VCF subscription; some components have usage or capacity limitations that require careful review in your specific contract.

The Forced Purchasing Problem

The central commercial tension in VCF licensing is that Broadcom does not permit à la carte selection within the VCF bundle. Organisations purchase VCF per core, and that per-core price includes every component in the bundle — regardless of whether you use NSX, deploy vSAN, leverage the Aria management suite, or run Tanzu workloads.

For organisations that previously ran only vSphere compute on traditional SAN storage with no NSX and no vRealize, the VCF bundle forces them to pay for features they have no operational need for. This forced purchasing is the primary driver of customer frustration with the Broadcom licensing model and is the strongest basis for migration arguments in negotiations.

There are three approaches to addressing the forced purchasing problem in practice:

Approach 1: Accept VVF as an alternative. For organisations not using vSAN, VVF (VMware vSphere Foundation) provides a lower-cost subscription that excludes vSAN, NSX, and the full Aria suite. The trade-off is loss of access to these features if requirements change. VVF pricing is typically 40–60% of VCF pricing for equivalent core counts, making it a significant cost reduction for pure-compute environments.

Approach 2: Negotiate a blended VCF/VVF estate. Some organisations can legitimately license different tiers for different host populations — for example, VCF for hosts participating in a vSAN cluster, and VVF for dedicated compute hosts with traditional storage. This blended approach reduces total cost by applying the cheaper VVF rate to the portion of the estate that does not require the full VCF stack. Broadcom's standard commercial position is to require VCF across an entire environment once any vSAN is in use, but this is a negotiating position, not an absolute technical requirement.

Approach 3: Use forced purchasing as migration leverage. If an organisation is paying for NSX and Aria functionality that it does not use, this represents a credible argument for exploring alternative platforms where à la carte purchasing is possible. Presenting this analysis to Broadcom — with evidence of evaluated alternatives — typically motivates commercial exceptions or additional discounting that would not be available absent the migration threat.

Core-Based Pricing: How Costs Are Calculated

VCF pricing is based on the number of physical CPU cores on in-scope hosts. Every physical core on every host that runs VMware workloads must be covered by a VCF subscription. Broadcom's standard approach counts all cores on all hosts in a cluster, regardless of whether specific cores are assigned to production workloads.

The Core Counting Rules

Core counting under VCF follows these principles:

• All physical cores on each host must be licensed — there is no partial-host licensing
• Minimum 16 cores per host — hosts with fewer than 16 physical cores are still licensed for 16 cores
• Hyperthreading does not affect count — only physical cores, not logical processors, are counted
• All hosts in a vCenter-managed environment must be in scope if they run ESXi, even if lightly utilised
• Development and test hosts may qualify for reduced pricing under certain commercial programmes — this must be specifically negotiated

Calculating Your VCF Core Count

The starting point for your VCF cost calculation is an accurate count of your current physical cores across all in-scope hosts. Many organisations discover that a thorough infrastructure audit produces a lower core count than Broadcom's initial proposal, because: hosts have been decommissioned but not removed from Broadcom's inventory data, dev/test hosts have been included in the production core count, and some hosts may legitimately qualify for VVF rather than VCF licensing.

In this example, securing VVF pricing for development, test, and DR hosts reduces the VCF core count from 1,408 to 1,024 — a 27% reduction in full-price VCF units. At typical VCF pricing, this approach can represent £80,000–£150,000 in annual savings, depending on negotiated per-core rates.

Strategies to Reduce VCF Costs

The following strategies are effective in reducing VCF subscription costs:

1. Right-Size Your Core Count Before Negotiating

Conduct a thorough infrastructure audit before engaging Broadcom on pricing. Remove decommissioned hosts from your inventory, segregate dev/test environments for separate commercial treatment, and identify any hosts that may qualify for VVF rather than VCF. Reducing the core count baseline by even 15–20% creates compounding savings because it reduces both the current-year cost and the baseline against which future uplift increases are applied.

2. Negotiate Dev/Test and DR Pricing Separately

Development, test, and disaster recovery environments have different operational criticality than production environments. Broadcom maintains commercial programmes that recognise this distinction — but only for organisations that specifically negotiate for separate treatment. Dev/test pricing under VVF rather than VCF for non-production workloads is a common commercial concession in well-structured deals. DR environments on cold/warm standby may also qualify for reduced subscription rates.

3. Commit to Multi-Year Terms for Price Certainty

VCF subscriptions are available on 1-year, 3-year, and 5-year terms. Multi-year commitments typically yield 15–25% pricing improvements versus annual terms and provide valuable cost certainty. The trade-off is inflexibility — evaluate your infrastructure roadmap before committing. If a cloud migration or platform consolidation is planned within the commitment window, multi-year VCF commitments become a financial liability.

4. Leverage Migration Alternatives in the Negotiation

The existence of credible migration alternatives — Nutanix AHV, Microsoft Hyper-V, Red Hat OpenShift Virtualisation — provides the strongest commercial leverage against Broadcom's initial VCF pricing. A 30% discount from list on a 3-year VCF commitment is commercially achievable when supported by evidence of a genuine migration assessment. Without this leverage, Broadcom has less incentive to discount beyond standard commercial programme rates. See our VMware Alternatives Comparison for the data to support this analysis.

5. Secure Annual Uplift Caps at Signing

This is perhaps the most important cost management action available at the time of VCF subscription signing. Negotiating a contractual annual uplift cap of 3–5% protects against unconstrained price escalation at renewal. Without a cap, Broadcom can increase your VCF subscription by any amount at annual renewal. With a cap, you establish a floor beneath which your cost certainty is protected for the subscription term.

VCF Add-Ons and Optional Components

While the core VCF bundle is comprehensive, several VMware capabilities are not included and require separate subscription purchases:

Carbon Black licensing is particularly worth noting. Many enterprise VMware customers historically purchased Carbon Black as part of their endpoint security strategy. Under the Broadcom model, Carbon Black is entirely separate from VCF and requires a separate per-endpoint subscription. Organisations consolidating endpoint security into a single vendor contract may find this creates an opportunity for overall commercial negotiation that crosses the VCF and Carbon Black product lines. For details, see our VMware Carbon Black Licensing guide.

Frequently Asked Questions