VMware vSphere Foundation lists at $135 per core per year in 2026, sold by subscription with a 16-core-per-CPU minimum, which makes it roughly 61 percent cheaper per core than VMware Cloud Foundation while still bundling vSphere with operations management. For the large share of estates that run standard server virtualization without software-defined networking, vSphere Foundation is the correct edition, and assigning cores to it instead of VCF is one of the fastest cost reductions available under the Broadcom model. This page sets out the rate, the minimum, the add-ons, and the edition decision.
Inside This Guide
What vSphere Foundation is
vSphere Foundation, often written VVF, is Broadcom's mid-tier subscription bundle. It pairs the vSphere hypervisor with VCF operations management and a modest vSAN capacity entitlement, sitting above the bare vSphere Standard edition and below the full VMware Cloud Foundation stack. It is the edition most former vSphere Enterprise Plus customers map onto when they renew under subscription, because it preserves the core hypervisor capabilities they used without the NSX and Aria components they did not.
Like every Broadcom edition, it is licensed per physical core, term-based, and lapses at term-end with no perpetual fallback. The structural shift away from perpetual licenses is explained in the VMware by Broadcom licensing guide, and the per-core counting rules are set out in VMware per-core licensing.
vSphere Foundation 2026 list pricing
The headline rate is a single per-core figure. The numbers below reflect Broadcom's 2026 rate card and net outcomes seen on advised renewals.
| Item | Metric | List per core per year | 3-year list per core |
|---|---|---|---|
| vSphere Foundation | Per physical core | $135 | $405 |
| vSAN add-on (per TiB beyond entitlement) | Per TiB per year | $2.50 to $3.00 | $7.50 to $9.00 |
| Production support (included) | Bundled | $0 incremental | $0 incremental |
A dual-socket host with two 32-core CPUs, 64 cores, lists at $8,640 per year on vSphere Foundation. The same host on VCF would list at $22,400. Across a four-host, 256-core cluster the annual list cost is $34,560 on vSphere Foundation against $89,600 on VCF, a $55,040 yearly difference driven solely by edition. That gap is the reason edition assignment is the first cost lever to pull.
Negotiation lever: Broadcom sales motions default to quoting VCF for the whole estate. Insist on a per-cluster edition map that assigns vSphere Foundation to every workload that does not consume NSX or large-scale vSAN. On a mixed 1,000-core estate, moving 600 cores from VCF to vSphere Foundation cuts annual list cost by roughly $129,000 before any discount.
The 16-core minimum
vSphere Foundation carries a 16-core-per-CPU minimum rather than the 72-core-per-order floor that applies to VCF. Any physical CPU with fewer than 16 cores is still billed as 16. This is the original Broadcom subscription minimum and it is far gentler than the VCF floor, which is part of why small and edge clusters land more cheaply on vSphere Foundation.
| CPU configuration | Physical cores | Billed cores | List cost per CPU per year |
|---|---|---|---|
| 1 CPU x 8 cores | 8 | 16 (minimum applies) | $2,160 |
| 1 CPU x 16 cores | 16 | 16 | $2,160 |
| 1 CPU x 32 cores | 32 | 32 | $4,320 |
| 1 CPU x 48 cores | 48 | 48 | $6,480 |
Because the minimum is per CPU rather than per order, a small two-socket edge host with 16-core CPUs is billed for 32 cores, not the 72 a VCF order would impose. For distributed retail or branch estates running many small hosts, that difference compounds quickly, and it is the main reason edge sites belong on vSphere Foundation. The trade-offs across site types are covered in VMware subscription pricing 2026.
The vSAN add-on
vSphere Foundation includes a small vSAN capacity entitlement, commonly 0.25 TiB per core, far less than the 1 TiB per core bundled with VCF. Estates that run vSAN at scale must buy additional capacity by the TiB, and that add-on cost can erode the edition savings if the storage footprint is large.
| Estate | Included vSAN (0.25 TiB/core) | Add-on if 200 TiB needed |
|---|---|---|
| 256 cores | 64 TiB | 136 TiB at $2.50 to $3.00 per TiB |
| 512 cores | 128 TiB | 72 TiB at $2.50 to $3.00 per TiB |
| 1,024 cores | 256 TiB | 0 TiB (within entitlement) |
The rule of thumb: if your vSAN requirement exceeds roughly 1 TiB per core, model VCF and vSphere Foundation side by side, because the larger VCF storage entitlement can close the gap. If you run external storage arrays or modest vSAN, vSphere Foundation wins clearly. The storage entitlement math is one of the items we model in a software licensing advisory review.
vSphere Foundation versus Standard and VCF
Three editions cover most estates. The choice is a function of which capabilities the workload actually consumes.
| Capability | vSphere Standard | vSphere Foundation | VCF |
|---|---|---|---|
| List per core per year | $50 | $135 | $350 |
| Hypervisor and vMotion | Yes | Yes | Yes |
| Operations management | No | Yes | Yes |
| vSAN entitlement | None | 0.25 TiB/core | 1 TiB/core |
| NSX and Aria | No | No | Yes |
vSphere Standard suits simple clusters that need only the hypervisor. vSphere Foundation suits the broad middle that wants operations management and modest storage. VCF suits private-cloud and self-service platforms that genuinely consume networking and automation. The full VCF rate and bundle teardown sits in the VMware VCF pricing guide.
Discount bands by deal size
Discount on vSphere Foundation scales with committed cores and term, on the same pattern as VCF but typically a few points lower in absolute percentage because the starting rate is already lower. The bands below reflect net outcomes on advised renewals.
| Committed cores | Typical discount off list | Effective per-core rate |
|---|---|---|
| 16 to 500 | 0 to 12 percent | $119 to $135 |
| 500 to 2,000 | 12 to 28 percent | $97 to $119 |
| 2,000 to 10,000 | 25 to 42 percent | $78 to $101 |
| 10,000+ | 40 to 58 percent | $57 to $81 |
As with VCF, a credible migration alternative moves the number. Buyers who hold a costed Proxmox migration plan or Nutanix migration plan reach the upper bands more reliably than those who renew without one.
When to choose vSphere Foundation
Assign cores to vSphere Foundation when the workload needs the hypervisor and operations management but not NSX micro-segmentation or VCF-scale vSAN, which describes most general-purpose virtualization. Move to VCF only for the specific clusters that run a private-cloud platform or consume network virtualization. Drop to vSphere Standard for the simplest clusters that need nothing beyond compute. The discipline of mapping each cluster to the lowest sufficient edition is the single largest controllable lever in a Broadcom estate, and it is the starting point of the work in VMware renewal negotiation and the VMware by Broadcom hub.
vSphere Foundation total cost of ownership
Like VCF, vSphere Foundation replaced a perpetual license and annual support with a recurring subscription that lapses at term-end. The lower $135 per-core rate softens the increase, but the multi-year arithmetic still favors active management. A 256-core estate on vSphere Foundation lists at $34,560 a year, or $172,800 across five years, before discount. The same estate negotiated at a 30 percent discount lands near $120,960 over five years.
| Scenario, 256 cores | Per year | 5-year total |
|---|---|---|
| vSphere Foundation list | $34,560 | $172,800 |
| vSphere Foundation at 30% discount | $24,192 | $120,960 |
| Same cores on VCF list | $89,600 | $448,000 |
The lower row shows why edition assignment dominates the total. Moving general-purpose cores from VCF to vSphere Foundation, then discounting the result, is a far larger saving than any single discount negotiation on VCF alone.
Common vSphere Foundation pricing mistakes
The errors that inflate vSphere Foundation cost differ from the VCF set, because the edition is already the cheaper bundle.
- Underestimating the vSAN add-on. The 0.25 TiB-per-core entitlement is small. Storage-heavy estates buy extra TiB that can erase the savings versus VCF, so model storage before committing the edition.
- Leaving cores on VCF that belong here. The most expensive mistake is the reverse of the edition map: keeping general-purpose workloads on VCF when vSphere Foundation would serve them at 39 percent of the cost.
- Splitting CPUs below 16 cores. The 16-core-per-CPU minimum means an 8-core CPU is billed as 16. Populating CPUs to at least 16 cores removes wasted floor.
- Skipping the multi-year commitment. One-year terms forgo the better discount bands and the price protection that a three-year commitment secures against annual uplift.
vSphere Foundation for edge and branch estates
Distributed estates with many small hosts are where vSphere Foundation pulls furthest ahead of VCF. Because the minimum is 16 cores per CPU rather than 72 cores per order, a small branch host with two 16-core CPUs is billed for 32 cores at $4,320 a year, against the $25,200 a VCF order would impose. Across 50 branch sites that difference is over $1 million a year. Retail, banking, and manufacturing estates with dozens of edge locations should default every site to vSphere Foundation or vSphere Standard, reserving VCF for the central data center alone. The site-by-site modeling that produces this split is part of a software licensing advisory review and is set out further in the VMware by Broadcom hub.
Negotiating the vSphere Foundation renewal
The vSphere Foundation renewal is where edition discipline turns into cash. The first move is to fix the core count, retiring hosts that no longer run workloads and confirming that every CPU is populated to at least the 16-core minimum so no floor is wasted. The second is to confirm the edition map still holds, because workloads migrate over time and a cluster that needed VCF networking last year may now run plainly on vSphere Foundation, or the reverse. The third is to commit for three years in exchange for a discount band uplift and a written cap on annual increases, which converts an open-ended subscription into a known multi-year cost. The fourth is to bring a costed alternative to the table, because even on the cheaper edition Broadcom responds to a credible migration plan. A documented Proxmox or Nutanix model for a defined slice of the estate is the single most reliable way to reach the upper discount bands. Buyers who renew on the quoted terms typically accept a 10 to 15 percent uplift, while buyers who renew with a fixed core count, a clean edition map, a multi-year commitment, and an alternative in hand routinely hold the increase flat or secure a reduction. The full renewal sequence sits in VMware renewal negotiation, and the migration models are in migration to Nutanix.
One further discipline closes the loop on vSphere Foundation cost: review the edition assignment on a fixed schedule rather than only at renewal. Workloads change, hosts are added and retired, and a cluster that was correctly placed on vSphere Foundation a year ago can drift into needing more, or less, than the edition provides. A semiannual edition review catches that drift while it is still cheap to correct, and keeps the estate sitting on the lowest sufficient edition every quarter rather than only on renewal day.
Renewing under subscription? Our advisors build the per-cluster edition map that minimizes your core spend, on a VMware negotiation engagement.