What VMware Cloud Foundation really costs per core.
A 62 page buyer side guide to VMware Cloud Foundation licensing under Broadcom. VCF bundle anatomy, the embedded vSphere, vSAN, NSX, and Aria entitlement, the core minimum mechanic, the vSphere Foundation comparison, and the contract clauses that protect customers through the conversion programme.
500+ Enterprise ClientsIndustry Recognized$2B+ Under Advisory11 Vendor Practices100% Buyer Side Independent
VMware Cloud Foundation is the only path Broadcom offers for the full virtualisation stack. The licensing model is engineered to bundle entitlement the customer does not need into a per CPU price that the customer cannot disaggregate.
For most enterprises the VMware estate was acquired across a decade of point product purchases that combined vSphere, vSAN, NSX, Aria Operations, SRM, Tanzu, and a long tail of management plane and disaster recovery products. The Broadcom acquisition collapsed that catalogue into two SKUs: VMware Cloud Foundation, which carries the full software defined data centre stack, and VMware vSphere Foundation, which carries a narrower compute and management entitlement. Every enterprise renewal in 2026 is a choice between those two SKUs, and that choice is the single most important commercial decision the customer will make about the future of the virtualisation estate. This guide is written for that decision. It documents the VCF bundle anatomy, the embedded entitlement set, the core minimum mechanic, and the contract clauses that protect the customer through the Broadcom conversion programme. The guide pairs with the source VMware Cloud Foundation article, the Broadcom VMware Negotiation 2026 Playbook, and the Broadcom VMware Knowledge Hub.
VMware Cloud Foundation is genuinely different from the perpetual VMware licensing model that the customer is most familiar with. The bundle carries vSphere Enterprise Plus, vSAN Enterprise, NSX Enterprise Plus, Aria Suite Enterprise, HCX Enterprise, and several other components that the customer may or may not use. The per CPU pricing is layered on top of a sixteen core minimum that sets a floor above the deployed core count for many enterprises. The subscription term forces a multi year forward commitment. And the conversion of the legacy perpetual estate into the VCF subscription introduces a support entitlement transfer, a maintenance bridge consideration, and a partner channel allocation question that materially change the economics of the proposal. The buyer side response has to address every one of those mechanics while still securing a defensible position that aligns with the actual workload need. The framework pairs with our wider Broadcom advisory practice, the VCF Migration Cost Estimator, and the VMware Alternatives 2026 Guide for the substitution view.
Used in sequence, the techniques in this guide routinely deliver VCF commitment savings between twenty and thirty five percent against the opening proposal, plus structural protection against unused embedded entitlement, plus a defensible position that keeps the option open to substitute selected workloads onto vSphere Foundation, Nutanix AHV, Microsoft Hyper V, Red Hat OpenShift Virtualisation, Proxmox, or the public cloud platforms. The guide is updated quarterly to track the Broadcom price book, the VCF and vSphere Foundation bundle definitions, the partner channel structure, and the negotiated discount band we observe in live deals. Read it next to our Broadcom VMware Negotiation 2026 Playbook for the macro framing, the Broadcom advisory practice page for how Redress Compliance applies these techniques inside live engagements, and the UK media case study for a worked example.
Skip ahead. Pull the VMware Cloud Foundation licensing guide now.
The opening section deconstructs the VCF commercial model under Broadcom. We document the per CPU pricing mechanic, the sixteen core minimum, the subscription term economics, the support entitlement transfer, the partner channel allocation, and the embedded entitlement set across vSphere, vSAN, NSX, Aria, HCX, and the wider VCF software defined data centre stack. The section closes with a VCF cost model template that lets the buyer pressure test the Broadcom proposal against actual deployed core inventory, projected workload growth, and the alternative spend on vSphere Foundation and the substitution platforms.
The second section addresses the VCF versus vSphere Foundation decision. The single most important commercial choice in the Broadcom relationship is the SKU choice between VCF, which carries the full stack, and vSphere Foundation, which carries the narrower compute and management entitlement. The buyer side procedure maps the deployed workload against the actual feature usage and surfaces the populations that genuinely need VCF, the populations that should run vSphere Foundation, and the populations that should run on a substitute platform entirely. This is the same SKU rationalisation discipline we apply across the wider Broadcom advisory practice and inside the renewal program.
The third section covers the embedded entitlement audit. The VCF bundle carries vSAN Enterprise, NSX Enterprise Plus, Aria Suite Enterprise, HCX Enterprise, and several other components that the customer may or may not use. The buyer side approach identifies the embedded entitlements that the deployment is not consuming and documents the rebalancing options. The discussion connects to the audit defense kits that operationalise the evidence standard.
The fourth section addresses the core minimum mechanic. The sixteen core minimum per CPU is the single most expensive line item inside the VCF proposal for any customer whose physical CPU configuration runs below the threshold. The buyer side approach documents the deployed CPU inventory, the physical core profile, the core packing options inside the VMware cluster, and the partner channel conversations that surface alternative deployment models. We pair this with the VCF Migration Cost Estimator for the modelling.
The fifth section covers the perpetual to subscription conversion economics. The conversion mechanic carries a support entitlement transfer, a maintenance bridge consideration, and a partner channel allocation question. The buyer side procedure breaks the conversion apart into the perpetual baseline, the subscription term, the support transfer, the core minimum impact, and the bundle composition mapping, and gives a specific challenge for every component. The framework pairs with the Broadcom VMware Negotiation 2026 Playbook for the macro context.
The closing section documents the VCF renewal contract clauses Redress Compliance routinely negotiates: the core minimum grandfather clause, the bundle substitution clause that allows the customer to drop into vSphere Foundation on a defined population at renewal, the embedded entitlement substitution language, the subscription term price hold, the support entitlement transfer language, the partner channel allocation clause, and the executive escalation path that closes the deal at the Broadcom enterprise leadership level. Each clause is paired with negotiated language we have already placed inside live Broadcom enterprise contracts.
What You Will Learn
Seven outcomes this guide delivers
01
VCF commercial model decoded
A buyer side breakdown of the per CPU pricing, sixteen core minimum, subscription term, and partner channel mechanics.
02
VCF versus vSphere Foundation decision
A workload mapping procedure that surfaces the populations that need VCF and the populations that should run vSphere Foundation.
03
Embedded entitlement audit
An identification procedure for the embedded entitlements that the deployment is not consuming and the rebalancing options.
04
Core minimum mechanics
A defensible approach to the sixteen core minimum that documents the deployed CPU profile and surfaces the packing options.
05
Perpetual to subscription conversion
A line by line procedure for breaking the conversion exposure into baseline, term, support, core, and bundle components.
06
Renewal contract levers
Core grandfather, bundle substitution, entitlement substitution, term price hold, support transfer, and escalation language inside live contracts.
07
Multi year virtualisation portfolio strategy
A planning framework that aligns the VCF commitment with vSphere Foundation, the substitution platforms, and the public cloud estate.
Who This Is For
Built for the executives accountable for VMware
Chief Information Officer
Owns the Broadcom commercial relationship and the virtualisation strategy. The guide gives a defensible VCF versus vSphere Foundation decision and a renewal procedure.
VP IT Procurement
Runs the Broadcom renewal cycle. The guide supplies the bundle scenarios, embedded entitlement analysis, and clause language that convert proposals into outcomes.
VP Infrastructure
Operates the VMware estate. The guide formalises the workload mapping procedure and the core profile audit.
Chief Financial Officer
Approves the Broadcom commitment and the multi year capital plan. The guide provides the VCF cost model and the substitution economics.
Table of Contents Preview
What is in the guide
Chapters
Why VCF is the only Broadcom path for the full virtualisation stack
The VCF bundle anatomy: vSphere, vSAN, NSX, Aria, HCX, and the wider entitlement set
VCF versus vSphere Foundation: the workload mapping decision
Embedded entitlement audit and the rebalancing options
The sixteen core minimum and the deployed CPU profile
Multi year virtualisation portfolio strategy and the substitution roadmap
“
We dropped a third of the deployed workload into vSphere Foundation, surfaced an unused NSX Enterprise Plus entitlement that the original VCF bundle assumed, and locked in a defensible core minimum through a grandfather clause negotiated with Broadcom executive leadership.
VP Infrastructure, Global Financial Services
Twenty four thousand vSphere cores and a multi million dollar VCF commitment
Free · Read on this page
VMware Cloud Foundation Licensing Guide
Two fields and the full guide opens on this page. No PDF to wait for, no inbox follow up unless you ask.
Free · Read in your browser
Read the full guide now
Two fields, then it opens on this page.
Unlocked. You are reading the full VMware Cloud Foundation Licensing guide.
VMware Cloud Foundation is the only path Broadcom offers for the full virtualisation stack. The licensing model is engineered to bundle entitlement the customer may not use, then price it per core on a subscription.
This guide walks the VCF commercial model, the VCF versus vSphere Foundation decision, and the levers that hold a Broadcom renewal accountable.
How does Broadcom price VMware Cloud Foundation?
Broadcom prices VCF per core on a subscription, with a sixteen core per CPU minimum. The model bundles the full stack, so you license the whole platform even where a workload needs only part of it.
Per core subscription: the unit the whole quote is built on.
Sixteen core minimum: the per CPU floor that inflates small hosts.
Bundled stack: the full set of components priced as one.
Where does the per core minimum inflate the quote?
It inflates any host with fewer than sixteen cores per CPU, because you pay the minimum regardless. Document the deployed core profile so you only license what runs.
VCF or vSphere Foundation, which does each workload need?
Map workloads to the lightest edition that covers them. VCF carries the full stack, but many estates run workloads that vSphere Foundation covers at a materially lower cost.
How do you run the workload mapping?
List each cluster, the components it actually uses, and the edition that covers them. The populations that do not need the full stack are the savings, and they are usually larger than expected.
Inventory clusters: capture the deployed core and component profile.
Match the edition: assign VCF only where the full stack is used.
Surface the gap: quantify the workloads over licensed by a VCF default.
VCF versus vSphere Foundation, where each one fits
Factor
VCF
vSphere Foundation
Stack scope
Full private cloud
Compute and core management
Best for
Integrated cloud platform
Standard virtualisation
Cost posture
Highest per core
Lower where stack is unused
How do you handle perpetual to subscription conversion?
Break the conversion into baseline, term, and support components, then price each line. Broadcom presents conversion as a single number, which hides where the exposure sits and removes your leverage.
What does the embedded entitlement audit find?
It finds the components in the bundle the deployment does not consume. Identifying them lets you substitute or drop entitlement instead of paying for the full stack by default.
Where the common advice on VMware Cloud Foundation licensing is wrong
The standard advice since the Broadcom acquisition is to accept VCF as the only viable path and renew on its terms. We disagree.
Across the renewals I have benchmarked, a workload mapping moved 30 to 60 percent of the estate to vSphere Foundation or to substitution without losing capability. Accepting the VCF default is how the unused stack gets paid for.
The buyer side move is to map workloads, document the core profile, and price the conversion line by line. A mapped estate beats a default VCF quote by a wide margin.
The deployed core profile per host, not the VCF list bundle, sets the defensible licensing baseline.
What renewal levers hold a Broadcom VCF quote accountable?
Five levers carry the value on a VCF renewal. Each is a contract position, so it has to be documented before the renewal date closes the window.
Core grandfather: hold the prior core basis as the floor.
Bundle substitution: swap unused stack for the edition you run.
Entitlement substitution: drop components the deployment does not consume.
Term price hold: protect the per core rate across the subscription.
Support continuity: price support as its own line, not a hidden uplift.
A VCF quote priced on the full stack and a sixteen core minimum is an opening position, not the licensing your workloads require.
How do you build a multi year virtualisation portfolio position?
Align VCF, vSphere Foundation, and any substitution path into one plan. A portfolio view keeps the Broadcom commitment matched to the workloads you actually run, term over term.
Track the product scope on the Cloud Foundation page and plan the estate against it before each renewal.
What governs the renewal timeline?
Time the workload mapping to land before the renewal window closes. Compare the full stack against standard virtualisation on the vSphere product page before you commit to a VCF default.
Want this run against your VMware estate?
Fredrik Filipsson wrote this guide from the VMware estate work he has led. He will walk your position and your three biggest levers in a 30 minute call. No pitch.
One letter a month. Negotiation moves, audit signals, and price book shifts.
Before you go
Get the buyer side monthly briefing.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
