VMware Cloud Foundation (VCF) is the full private cloud platform — compute, storage, networking and automated lifecycle management in one stack. VMware vSphere Foundation is the virtualization tier: VMware ESXi, vCenter, a smaller vSAN entitlement and basic operations tooling, without NSX. Both are sold per physical core on subscription under the same VMware licensing model. The practical dividing line is networking: if you need NSX, you need VCF.
Yes, it is still available — one of the surviving offerings in the simplified portfolio, not a discontinued product. For a great many virtualized workloads it remains the right answer.
VMware Cloud Foundation vs vSphere Foundation: What Each Tier Includes
| Component | VVF | VCF |
|---|---|---|
| vSphere Enterprise Plus (VMware ESXi) | ✅ | ✅ |
| vCenter Server Standard | ✅ | ✅ |
| vSAN entitlement | 0.25 TiB per core | 1 TiB per core |
| Aria Operations and Operations for Logs | ✅ | ✅ |
| Tanzu Kubernetes Grid / vSphere Kubernetes Service | ✅ | ✅ |
| NSX networking | ❌ | ✅ |
| Aria Automation, Aria Operations for Networks | ❌ | ✅ |
| HCX | ❌ | ✅ |
| SDDC Manager (automated lifecycle management) | ❌ | ✅ |
Two things about VMware Cloud Foundation vs vSphere Foundation surprise people side by side.
The lower tier includes Kubernetes. Tanzu Kubernetes Grid ships in it, so you do not need the full-stack platform to run containers on vSphere. A lot of teams adopt VCF for a capability they already have.
VCF is not simply "the lower tier with a bigger allowance". The additions are whole product categories — software-defined networking, automation, disaster recovery and migration tooling, and a manager that patches the stack as a unit. If you would not deploy them, you are paying for a private cloud experience to run a virtualization platform.
VMware Cloud Foundation vs vSphere Foundation: The Real Dividing Line
Work through it in this order.
Do you need NSX? Micro-segmentation, distributed firewalling, overlay networking, or security features that a compliance requirement names explicitly. If yes, stop — you need VCF. This is the single most common reason to move up, and there is no partial option.
How much vSAN capacity do you need per core? The 0.25 TiB per core is a real allowance, not a token one, but it is a quarter of what the top tier grants. A data center with heavy storage and modest processing demand can exhaust it and pay again for add-on capacity. Storage economics catch people out more often than the CPU sizing does — do the arithmetic against your actual footprint first.
Do you want the stack patched as a unit? SDDC Manager is the quiet differentiator. Automated lifecycle management across ESXi, vCenter and NSX is genuinely valuable at scale, and genuinely constraining if you like upgrading components independently on your own deployment schedule.
How many hosts is this? Full-stack automation and self-service IaaS earn their keep across dozens of hosts, where scalability and agility are the point. On a handful of hosts the overhead can exceed the operational saving.
Are you extending into public cloud? HCX matters for hybrid cloud migration and for disaster recovery between sites. If your workloads stay on-premises and always will, it is capability you are unlikely to use.
Can you start with VVF and move up later?
Yes — the transition to VCF is a normal commercial motion, and starting lower while you evaluate is a reasonable strategy. The upgrade from VMware vSphere Foundation to the full platform is a supported path.
Going back down is the problem. Once you are on the top tier, reverting to a legacy SKU is not a supported path. We watched a public-sector customer discover exactly that mid-negotiation: they wanted to step back to what they had been running, and the option simply was not on the table. Whatever leverage they had disappeared with it.
So the asymmetry is the thing to plan around. Moving up later is easy. Moving back down is not a lever you should assume you hold. When the decision is close, starting lower preserves optionality that starting high does not.
The mixed-estate problem
Most renewals we see are not a clean single-product decision. A typical estate carries several legacy SKUs bought at different times — vSphere Essentials Plus on some hosts, vSphere Enterprise Plus on others, perhaps a block of perpetual licenses nobody has touched in years.
One customer came to us with 144 cores split across two different legacy products, a contract expiring in under a month, and no clear picture of where each SKU landed in the new portfolio. That is not unusual and it is not incompetence — Broadcom collapsed a catalogue of more than 160 products, and the mapping was never obvious from the outside.
Two practical consequences. First, audit what you actually hold before anyone quotes you, because a renewal quote built on an assumed inventory is a quote for the wrong thing. Second, a mixed estate does not have to renew as a single tier — splitting workloads across both is legitimate where the requirements genuinely differ. A workload running plain virtualization and a workload needing integration and management across cloud environments are different problems, and the VMs can be licensed accordingly.
Facing a renewal and unsure which tier fits? AceMQ handles VMware licensing and renewal quotes, including estate audits that establish what you hold before anyone prices anything. Request a renewal quote.
How the licensing models compare
VMware's new licensing model applies the same mechanics to both: per physical core, subscription only, with a minimum of 16 cores charged per CPU and a 72-core minimum on any order. Perpetual licenses are no longer sold, and since 2025 the order minimum has been the binding constraint for smaller estates.
They differ on rate, not method. VCF costs materially more per core, which is why right-sizing usually saves more than negotiating the rate does. For how the core counting and minimums actually work, see how VMware licensing cost is calculated — and for the wider portfolio changes, what Broadcom changed about VMware licensing.
Because pricing is quoted under agreement rather than published, the only way to settle VMware Cloud Foundation vs vSphere Foundation against your own estate is to have both quoted.
FAQ
What is the difference between VMware Cloud Foundation vs vSphere Foundation?
VCF is the full private cloud platform — it adds NSX Enterprise networking, Aria Automation, HCX and lifecycle management, plus a four-times-larger storage entitlement. The lower tier covers VMware ESXi, vCenter, Kubernetes and basic operations tooling. If you need software-defined networking, you need VCF.
Is vSphere Foundation still available?
Yes. It survived the portfolio simplification and is actively sold.
What is VMware Cloud Foundation?
An integrated, unified platform that bundles processing, storage, networking and management into a single subscription, with SDDC Manager handling upgrades across the whole stack rather than component by component. It is designed to simplify and streamline operations at data center scale and to deliver a self-service, cloud-like consumption model on-prem.
Does vSphere Foundation include Tanzu?
Yes. Tanzu Kubernetes Grid, now delivered as vSphere Kubernetes Service, is included. You do not need the full-stack platform to run Kubernetes on vSphere.
Is VCF subscription-only?
Yes. Both tiers are subscription. Perpetual licensing was retired across the portfolio — existing perpetual licenses keep running but receive no support or updates.
Can I upgrade from vSphere Foundation to VCF later?
Yes, and it is a routine motion. Plan carefully in the other direction: moving back down to a legacy SKU once you are on the top tier is not a supported path.
How much vSAN capacity do I get?
0.25 TiB per core on the lower tier and 1 TiB per core on the top tier. Entitlements aggregate across licenses of the same tier, and additional capacity can be bought as an add-on.
Is VCF replacing vSphere?
No. VMware vSphere is the hypervisor and remains the foundation of both. VCF is a platform built around it, not a replacement for it.
