Scope VMware Cloud Foundation to the cluster, not the estate
VMware Cloud Foundation bundles compute, storage, networking and management into one per-core subscription, and Broadcom positions it as the default for every renewal. But the full software-defined stack is genuinely used on a minority of cores: NSX runs active on 22 to 38 percent of cores in a typical estate, and vSphere Foundation, the lighter bundle, covers the rest at roughly 39 percent of the VCF core rate. The saving is not in the discount, it is in putting each cluster on the tier its workloads actually need.
Prepared by Redress Compliance · August 9, 2026 · Broadcom advisory. Based on VCF tier-fit reviews across mixed VMware estates, 2025.
Executive summary
VCF is the full stack at a premium core rate, and Broadcom makes it the default renewal position.
VMware Cloud Foundation bundles vSphere for compute, vSAN for storage, NSX for networking and Aria for management into a single per-physical-core subscription at roughly $350 per core per year, with a 16-core minimum per processor and a 256-core maximum per subscription.
Broadcom positions VCF as the default for every renewal, so the opening quote usually prices the whole estate at the VCF rate. The premium is real value where the full software-defined stack runs, and pure overspend where it does not, so the tier decision, not the discount, is where the money moves.
The full stack is genuinely used on a minority of cores, so estate-wide VCF overpays.
Across mixed estates, NSX is active on only 22 to 38 percent of cores, because most clusters run standard vSphere networking rather than the full NSX overlay, and vSAN adoption is similarly partial where existing SAN or third-party storage still carries the workload.
Pricing the entire estate at the VCF rate therefore pays the premium on cores that never touch NSX or vSAN, and vSphere Foundation, the lighter bundle at roughly $135 per core, covers those workloads at about 39 percent of the VCF rate.
The tier-fit question is decided cluster by cluster, not signed estate-wide.
VVF is where the cost concentrates, so the split between tiers is the single biggest lever.
In a right-sized estate the vSphere Foundation footprint typically carries the majority of the workload while VCF carries the full-stack minority.
And getting the split right moves the bill more than any negotiated percentage: VVF-eligible workloads are about 62 percent of a typical VCF-priced estate.
A five-point discount on an all-VCF quote is smaller than moving the 62 percent of workloads that do not need the full stack onto vSphere Foundation. Scope first, discount second, because a discount on the wrong tier locks in the premium for the whole term.
Tier discipline plus a credible exit is what actually reprices VCF, by 20 to 35 percent.
Estates that mapped NSX and vSAN usage cluster by cluster, moved the full-stack minority to VCF and the rest to vSphere Foundation, and paired the scope with a costed migration option, cut the VCF-priced quote 20 to 35 percent against the opening all-VCF position.
The core minimums and the 256-core cap also reward consolidation, so a density project lowers the licensed core count inside each tier. The move is to treat VCF as a tier to be earned cluster by cluster, not a default to be discounted.
The two bundles, and what separates them
| Dimension | vSphere Foundation | VMware Cloud Foundation |
|---|---|---|
| Compute (vSphere) | Included | Included |
| Management (Aria) | Included | Included |
| Storage (vSAN) | Not bundled | Included |
| Networking (NSX) | Not bundled | Included |
| Approx core rate | ~$135 per core | ~$350 per core |
| Fits | Core virtualization | Full software-defined stack |
VMware Cloud Foundation is the full software-defined data-center stack: vSphere for compute, vSAN for storage, NSX for networking and Aria for management.
Sold as one per-physical-core subscription. vSphere Foundation is the lighter bundle covering compute and management without the bundled vSAN and NSX, the right tier for clusters that run standard storage and standard vSphere networking.
The per-core rate is the headline difference, roughly $350 for VCF against $135 for vSphere Foundation, but the real distinction is whether the full software-defined stack is actually in production on a given cluster.
Both carry the 16-core minimum per processor, so lightly used hosts still pay for populated capacity, and the 256-core maximum per subscription shapes how large clusters are licensed.
The pricing mechanics sit in the Broadcom VMware pricing guide, and the contract structure in VMware contracts after Broadcom.
Where estate-wide VCF overpays, cluster by cluster
- Is NSX actually running here? NSX is active on only 22 to 38 percent of cores in a typical estate, so most clusters run standard vSphere networking and pay the VCF premium for an overlay they never enable.
- Is vSAN carrying this workload? Where existing SAN or third-party storage still serves the cluster, the bundled vSAN in VCF is paid-for and unused, and vSphere Foundation is the correct tier.
- Map usage cluster by cluster: the tier-fit decision is made per cluster on real NSX and vSAN usage, not signed estate-wide at the VCF rate.
- Move the full-stack minority to VCF and the rest to vSphere Foundation, because VVF-eligible workloads are about 62 percent of a typical VCF-priced estate.
- Consolidate inside each tier: the 16-core minimum and 256-core cap reward density, so fewer, denser hosts lower the licensed core count. The perpetual fallback sits in the perpetual license options guide.
The VCF tier-scoping playbook
The cluster-by-cluster NSX and vSAN map, the VVF split, the core-minimum math, and the exit that reprices the tier.
Get the white paper →How the tier split and the exit reprice the quote
The saving is not in the discount, it is in the split between tiers, so scope first and discount second.
In a right-sized estate the vSphere Foundation footprint carries the majority of the workload while VCF carries the full-stack minority.
And getting that split right moves the bill more than any negotiated percentage, because VVF-eligible workloads are about 62 percent of a typical VCF-priced estate.
A five-point discount on an all-VCF quote is smaller than moving that 62 percent onto vSphere Foundation, and a discount on the wrong tier locks in the premium for the whole term.
The mechanics reward discipline in two more ways: the 16-core minimum per processor means consolidating onto fewer, denser hosts lowers the licensed core count, and the 256-core maximum per subscription shapes how the largest clusters are packaged.
Pair the scope with a credible exit, because Broadcom prices the renewal against the cost and risk of you leaving, so a named platform, a funded pilot and a migration date for a defined cluster set is what turns a scoping argument into a repriced quote.
Estates that mapped NSX and vSAN usage cluster by cluster, moved the full-stack minority to VCF and the rest to vSphere Foundation, and paired the scope with a costed migration option cut the VCF-priced quote 20 to 35 percent against the opening all-VCF position.
The alternatives detail sits in Hyper-V versus VMware, Proxmox versus VMware, and the Nutanix comparison.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What the tier-fit reviews showed
Across VCF tier-fit reviews on mixed VMware estates in 2025, the opening quote almost always priced the entire estate at the VCF full-stack rate, and the common advice concedes it. The common advice is that VCF is the only supported path and the premium is unavoidable.
We disagree, because the full stack is genuinely used on a minority of cores:
Share of cores where NSX is active in a typical estate, so pricing the whole estate at the VCF rate pays the premium on cores that never enable the overlay.
Share of a typical VCF-priced estate that vSphere Foundation covers, the workloads running standard storage and standard networking that do not need the full stack.
The opening quote priced the whole estate at roughly $350 per core, but NSX ran active on only 22 to 38 percent of cores and about 62 percent of the workloads were VVF-eligible at roughly $135 per core.
Three patterns recurred: estate-wide VCF quotes pricing standard-networking clusters at the full-stack rate, the majority of workloads fitting vSphere Foundation once NSX and vSAN usage was mapped, and buyers who split the tiers and carried a costed exit cutting the quote 20 to 35 percent.
The buyer-side move is to treat VCF as a tier earned cluster by cluster on real usage, not a default applied estate-wide, then pair the scope with a credible migration option so the split is priced rather than argued. The wider library sits in the VMware practice.
Your first five moves
- Map NSX and vSAN usage cluster by cluster, because NSX is active on only 22 to 38 percent of cores and the tier-fit decision is made per cluster, not estate-wide.
- Split the estate into VCF and vSphere Foundation, moving the full-stack minority to VCF and the roughly 62 percent VVF-eligible majority to the lighter bundle.
- Scope first, discount second, because a five-point discount on an all-VCF quote is smaller than moving the 62 percent onto vSphere Foundation, and a discount on the wrong tier locks in the premium.
- Consolidate inside each tier, because the 16-core minimum and 256-core cap reward density and fewer, denser hosts lower the licensed core count.
- Pair the scope with a costed exit for one cluster set, a named platform, a funded pilot and a migration date, the combination that repriced quotes 20 to 35 percent. The VMware practice runs the tier-fit with you.
Frequently asked questions
What is VMware Cloud Foundation?
VMware Cloud Foundation is the full software-defined data-center stack bundled into a single per-physical-core subscription: vSphere for compute, vSAN for storage, NSX for networking and Aria for management.
Broadcom positions it as the default for every renewal, at roughly $350 per core per year with a 16-core minimum per processor and a 256-core maximum per subscription. It is the premium tier, and the full stack is genuine value where it runs and pure overspend where it does not.
How is VCF different from vSphere Foundation?
vSphere Foundation is the lighter bundle covering compute and management without the bundled vSAN and NSX, at roughly $135 per core, about 39 percent of the VCF rate. VCF adds the full software-defined storage and networking stack.
The right tier depends on whether a given cluster actually runs NSX and vSAN in production, so the decision is made cluster by cluster, not signed estate-wide. Clusters on standard storage and standard vSphere networking belong on vSphere Foundation.
Do I need the full VCF stack on every cluster?
Usually not. NSX is active on only 22 to 38 percent of cores in a typical estate, and vSAN adoption is similarly partial where existing SAN or third-party storage still carries the workload. Pricing the entire estate at the VCF rate therefore pays the premium on cores that never touch NSX or vSAN.
About 62 percent of a typical VCF-priced estate is VVF-eligible, so mapping usage cluster by cluster and splitting the tiers is where the saving is.
Where does the saving on a VCF renewal actually come from?
From the split between tiers, not the discount.
Moving the roughly 62 percent of workloads that do not need the full stack onto vSphere Foundation moves the bill more than any negotiated percentage, because a five-point discount on an all-VCF quote is smaller than repricing 62 percent of the estate at 39 percent of the rate.
Scope first, discount second, because a discount on the wrong tier locks in the premium for the whole term.
How much can tier discipline cut a VCF quote?
Estates that mapped NSX and vSAN usage cluster by cluster, moved the full-stack minority to VCF and the rest to vSphere Foundation, and paired the scope with a costed migration option cut the VCF-priced quote 20 to 35 percent against the opening all-VCF position.
The core minimums and the 256-core cap also reward consolidation, so a density project lowers the licensed core count inside each tier and compounds the tier-split saving.
Does consolidation lower VCF cost?
Yes. VCF carries a 16-core minimum per processor, so lightly used hosts still pay for populated capacity, and consolidating workloads onto fewer, denser hosts lowers the licensed core count inside each tier. The 256-core maximum per subscription also shapes how the largest clusters are packaged.
Per-core pricing rewards density, so a host-consolidation project can pay for itself in licensing while you also right-size the tier each cluster sits on.
The VMware Estate After the Repackaging
Part 2 of the Negotiating Broadcom series. Two bundles, per core with a sixteen core floor, three year terms paid up front, and a support horizon in October 2027 that decides your timing more than your renewal date does. What the estate actually looks like now, and which numbers are real.
