What is the difference between VMware VVF and VCF?

VMware vSphere Foundation (VVF) is Broadcom’s subscription for running virtual machines and Kubernetes on vSphere, with vSAN storage at 0.25 TiB per licensed core and VCF Operations for monitoring. VMware Cloud Foundation (VCF) is the full private cloud platform: it adds NSX networking, VCF Automation, HCX for migrations and private AI services, and raises the vSAN entitlement to 1 TiB per core. Both are licensed per physical CPU core, with a minimum of 16 cores per CPU, and both are at version 9.1 as of November 2026.

What each subscription includes

ComponentVVF 9.1VCF 9.1
HypervisorvSphere Enterprise PlusvSphere
ManagementvCenter StandardvCenter
KubernetesvSphere Kubernetes Service (VKS)vSphere Kubernetes Service (VKS)
OperationsVCF Operations, including logs and diagnosticsVCF Operations
StoragevSAN, 0.25 TiB raw capacity per licensed corevSAN, 1 TiB per licensed core, with snapshots and replication
NetworkingStandard vSphere networkingNSX software-defined networking
Self-service and automationNot includedVCF Automation
MigrationNot includedHCX
AINot includedVCF Private AI Services

Sources: the VVF FAQ and the VCF FAQ. Broadcom sells advanced services for VCF separately, including Avi Load Balancer, vDefend Firewall and VMware Live Recovery. Broadcom announced VCF 9.1 on May 5, 2026, and the VVF FAQ gives the same date for VVF 9.1 general availability.

Below VVF, Broadcom’s vSphere page lists vSphere Express for smaller environments: ESX Standard, vCenter Standard and the vSphere Distributed Switch, without vSAN or VKS.

How per-core licensing works

Both subscriptions follow the same counting rules, set out in Broadcom KB 313548:

  • You license every physical core on every ESXi host you run.
  • Each CPU counts as at least 16 cores, even if it has fewer.
  • A host with two 8-core CPUs therefore needs 32 core licenses, and a host with two 24-core CPUs needs 48.

The vSAN entitlement follows the core count. A 48-core VCF deployment includes 48 TiB of vSAN capacity, and the same cluster on VVF includes 12 TiB. Broadcom’s licensing documentation treats the entitlement as a pool across the environment, and capacity beyond it is bought as a vSAN add-on. Holders of perpetual licenses must move to a subscription before they can upgrade to 9.1.

Broadcom does not publish list prices; quotes come from Broadcom sales or partners. The difference in price per core between VVF and VCF, multiplied by every core in the estate, is usually the number that decides the choice.

Who each one is for

VVF fits organizations that run VMs, and some Kubernetes, on a few vSphere clusters with standard networking. Typical buyers have modest storage needs per core, use physical firewalls and VLANs rather than NSX, and do not need a self-service portal.

VCF fits organizations that run vSphere as a private cloud: many clusters, NSX micro-segmentation or overlay networks, self-service provisioning for internal teams, or service providers hosting tenants. Broadcom positions its multi-tenant features for “enterprise and service provider organizations.” A storage-heavy vSAN cluster can also favor VCF, because the fourfold vSAN entitlement offsets add-on capacity that a VVF customer would buy.

Availability varies by region

VVF is not sold everywhere. In December 2025 Broadcom confirmed to The Register that it had withdrawn VVF in some EMEA countries, while it stays available in most, and said that customers have to ask sales or partners what is available in their region. Check this before you plan a renewal around VVF, because the alternative offered may be VCF.

Choosing at renewal

  1. Count the physical cores on every host, applying the 16-core minimum per CPU.
  2. List the components you use today: NSX, Aria or VCF Operations, vSAN capacity, HCX, automation.
  3. If you use none of the VCF-only components, price VVF first, if it is offered in your country.
  4. Compare the vSAN entitlement with your raw capacity, since add-on capacity changes the result.
  5. Price the alternatives for workloads that could leave VMware at the same renewal.

Many teams use the renewal to move part of the estate elsewhere. VMware alternatives after the Broadcom acquisition covers the four paths, from another hypervisor to containers. For a closer look at two common replacement hypervisors, see Nutanix vs Proxmox, and for applications that move into containers, running Kubernetes on-premises.

How Cloudfleet fits

Cloudfleet Kubernetes Engine (CFKE) accepts VMware vSphere virtual machines, bare-metal servers and Proxmox VE VMs as self-managed nodes, next to nodes in public clouds. Teams can run containerized applications on their existing vSphere hosts without VKS, and the Terraform provider includes a vSphere example.

On this page