VMware Cloud Foundation vs vSphere Foundation: Licensing, Features and Pricing Comparison

Context: Why This Comparison Matters Now

Before November 2023, enterprises buying VMware infrastructure could mix individual product licences — purchasing vSphere, vSAN, NSX, and the vRealize Suite independently, selecting only the components required. That flexibility ended with Broadcom's acquisition and the 2024 portfolio consolidation. All perpetual VMware licences were moved to subscription in 2024, and the product catalogue was collapsed to four primary bundles.

Today, the choice for enterprises deploying VMware on-premises infrastructure is essentially binary: VMware Cloud Foundation (VCF) or VMware vSphere Foundation (VVF). Understanding the differences between these two products in precise detail — components included, licensing terms, subscription economics, upgrade paths, and total cost of ownership — is the starting point for every VMware investment decision.

Support cost increases of 3 to 5 times compared to the pre-Broadcom perpetual plus maintenance model are typical regardless of which bundle is chosen. The question is not whether Broadcom's subscription model costs more — it does, for almost all customers — but which bundle configuration represents the most rational investment given each organisation's infrastructure requirements.

Complete Feature Comparison: VCF vs VVF

The following covers every significant component or capability dimension between the two products.

Compute Virtualisation

Both VCF and VVF include VMware vSphere Enterprise Plus — the highest tier of the vSphere hypervisor platform. This includes ESXi, vCenter Server, vSphere Distributed Switch (VDS), vMotion, Storage vMotion, High Availability (HA), Distributed Resource Scheduler (DRS), Fault Tolerance, and vSphere Replication. Both also include vSphere Lifecycle Manager (vLCM) for image-based host patching and firmware management.

There is no meaningful differentiation in compute virtualisation capability between VCF and VVF. Both deliver enterprise-grade hypervisor functionality. The differentiation is entirely in the surrounding stack: networking, storage, management, automation, and security.

Networking: NSX

This is the most consequential difference. VCF includes NSX fully — network virtualisation, micro-segmentation, distributed firewall, layer 4-7 load balancing, VPN services, and the overlay network fabric that enables software-defined networking independent of physical infrastructure. VVF does not include NSX.

NSX requirements are determined by compliance mandates and architectural design, not product preference. PCI DSS requirement 1.3.2 (restricting inbound traffic to authorised communications) is most effectively implemented through NSX distributed firewall rules. HIPAA's security rule requirement for access controls and audit controls benefits significantly from NSX's per-workload policy enforcement. ISO 27001 controls for network segregation and monitoring align directly with NSX capabilities. Organisations subject to these frameworks that choose VVF will either need to purchase NSX separately or rely on physical network segmentation, which is significantly less granular and operationally flexible.

Storage: vSAN

Both bundles include vSAN, but at different capacity entitlements. VCF includes vSAN at 1 TiB of raw capacity per licensed core. VVF includes vSAN at 250 GiB per licensed core — one-quarter of the VCF entitlement. A 400-core environment on VCF receives 400 TiB of vSAN raw capacity; the same environment on VVF receives 100 TiB. Both include a separate vSAN licence key, and both support the full range of vSAN storage policies including RAID-1, RAID-5/6, and all-flash configurations.

vSAN is optional in the sense that organisations with existing SAN or NFS storage can use those as their primary datastore. However, the vSAN entitlement is included in both bundles regardless — organisations are paying for it whether or not it is deployed. For environments where hyper-converged storage makes operational sense, the 4x vSAN capacity difference between VCF and VVF is frequently the factor that tips the economics in VCF's favour.

Management and Automation: Aria Suite

VVF includes Aria Suite Standard — basic operations monitoring (vCenter-level metrics), log management with limited retention and analytics, and a simplified management console. VCF includes Aria Suite Enterprise — the fully capable version of Aria Operations (with application-aware monitoring, custom dashboards, capacity planning, and cost management), Aria Operations for Logs (with full log analytics, alerting, and long-term retention), Aria Automation (infrastructure-as-code with multi-cloud extensibility, self-service catalogue, and configuration management), and Aria Operations for Networks (network analytics and troubleshooting, formerly vRealize Network Insight).

The Aria Automation component in VCF Enterprise is a significant operational capability. It provides a policy-driven infrastructure deployment framework that enables self-service provisioning of VMs, Kubernetes clusters, and multi-cloud resources through a unified catalogue. Organisations with DevOps or platform engineering teams actively managing infrastructure-as-code will find Aria Automation one of the compelling VCF value propositions. Organisations without those operational capabilities may find it underdeployed.

Lifecycle Orchestration: SDDC Manager

VCF includes SDDC Manager; VVF does not. SDDC Manager is the central control plane that orchestrates deployment, patching, configuration management, and lifecycle operations for the entire VCF stack. It manages the Management Domain, Workload Domains, and cross-component upgrade coordination. In a multi-domain VCF deployment, SDDC Manager eliminates the need to manually sequence upgrades across vCenter, ESXi, NSX, vSAN, and Aria Suite components — a significant operational risk reduction for large environments.

For organisations running a single vSphere cluster with standard workloads, the operational overhead that SDDC Manager addresses may not be a pain point. For organisations with multiple clusters, mixed workload types, or strict change management requirements, SDDC Manager delivers genuine operational efficiency that is difficult to replicate through manual processes.

Kubernetes: Container Support

VVF includes one Tanzu Kubernetes Grid cluster. VCF includes vSphere Kubernetes Services (VKS, the updated Kubernetes platform in VCF 9.0) with support for multiple Kubernetes clusters across Workload Domains. Both products support running container and VM workloads on the same infrastructure.

For organisations with a defined Kubernetes strategy, VCF's multiple cluster support and Aria Operations integration provide better operational coverage. For organisations with minimal container requirements, VVF's single cluster inclusion is adequate.

Hybrid Cloud Migration: HCX

VCF includes VMware HCX for hybrid cloud migration; VVF does not. HCX provides live workload migration between vSphere environments — including to Azure VMware Solution, Google Cloud VMware Engine, and AWS VMware Cloud on AWS — with network extension, bulk migration, and replication capabilities. For organisations planning phased cloud migrations, HCX is a significant operational tool. For organisations with no current hybrid cloud migration agenda, its value in the current term is limited.

Licensing Terms: Subscription Structure

Both VCF and VVF are subscription-based products available on one-year, three-year, or five-year terms. Perpetual licensing was eliminated for all VMware products effective 2024 — no new perpetual licences are available, and existing perpetual licences will require transition to subscription at their next renewal.

The per-core licensing model applies to both products. Every physical processor core in every licensed vSphere host requires a licence, subject to a minimum of 16 cores per physical CPU socket. The 72-core minimum order quantity, effective April 2025, applies to both VCF and VVF. Longer subscription terms (three years and five years) typically deliver better per-core pricing through negotiation and Broadcom's standard discount tiers.

All subscriptions include mandatory Broadcom Maintenance Support as of May 2024. Premium support tiers — Mission Critical and Premier — are available at additional cost and are not bundled into either VCF or VVF base subscriptions. The 20 percent late renewal penalty for subscriptions that lapse applies to both products equally and cannot be waived by account teams.

Pricing: List and Enterprise Negotiated

VCF list price: $350 per core per year. VVF list price: $135 per core per year. Enterprise negotiated rates range from $140 to $180 per core per year for VCF and $80 to $120 per core per year for VVF. These are real negotiated rates observed across enterprise engagements — not theoretical minimums achievable only in exceptional circumstances.

The economics of the VCF premium versus VVF depend heavily on whether NSX is a deployment requirement. For NSX-requiring environments at 300+ cores, VCF is typically more cost-effective than VVF plus standalone NSX. For environments without NSX requirements, VVF at enterprise negotiated rates delivers 40 to 60 percent cost savings versus VCF with equivalent compute and storage functionality.

Upgrade Paths from VVF to VCF

Broadcom has defined four upgrade paths for organisations that start on VVF and need to migrate to VCF. Understanding these paths is critical for organisations that choose VVF as an initial entry point with a future VCF roadmap.

Path A — SDDC Manager Import (Recommended): The preferred upgrade path. Deploy SDDC Manager and import the existing VVF environment as a VCF Workload Domain. This approach preserves all existing VMs and workloads without migration, adds NSX incrementally, and brings the VVF environment under VCF lifecycle management. Timeline: one to three weeks. Downtime: zero for running VMs. This is the path Broadcom's implementation guides recommend for most organisations.

Path B — SDDC Manager Conversion: Deploy SDDC Manager directly into the VVF environment and convert it to a VCF Management Domain. More disruptive than Path A but provides full VCF domain structure including Management Domain separation. Timeline: two to four weeks. Downtime: minimal with planning.

Path C — Greenfield VCF with Workload Migration: Deploy a new VCF environment alongside the existing VVF deployment and migrate workloads phased over time. The highest effort approach but provides the cleanest resulting architecture. Timeline: eight to twelve weeks. Downtime: per-workload during migration windows.

Path D — vSphere Upgrade to VVF 9, then to VCF 9: For organisations still running older vSphere releases, the path is to upgrade to vSphere 8 and activate a VVF 9.0 licence, then subsequently import or convert to VCF. This is a sequenced upgrade rather than a direct conversion.

The upgrade paths are contractual events as well as technical ones. Upgrading from VVF to VCF mid-subscription term requires a contract amendment with Broadcom, not simply activating additional licence capacity. Timing upgrades to renewal events produces the most favourable commercial treatment.

Five Scenario Pricing Comparison

Scenario 1: 200 Cores, No NSX, External Storage

VVF at $100 per core: $20,000 per year. VCF at $160 per core: $32,000 per year. Annual difference: $12,000 in favour of VVF. Three-year difference: $36,000 in favour of VVF. Recommendation: VVF. No NSX requirement, no vSAN need, external storage in place. VCF adds no functional value for this profile.

Scenario 2: 400 Cores, NSX Required, vSAN in Use

VVF at $100 per core plus NSX add-on for 20 sockets at $4,000 per socket: $40,000 VVF plus $80,000 NSX = $120,000 per year. VCF at $160 per core: $64,000 per year. Annual difference: $56,000 in favour of VCF. Three-year savings with VCF: $168,000. Recommendation: VCF is significantly more economical once NSX is required.

Scenario 3: 800 Cores, Multi-Tenant, NSX, High Storage

VCF is the only viable choice at this scale with NSX and multi-tenant isolation requirements. VCF at $155 per core (volume discount): $124,000 per year. VVF plus NSX equivalent cost: $195,000 to $250,000 per year depending on NSX scope. VCF is preferred by $70,000 to $125,000 annually.

Scenario 4: 300 Cores, No Current NSX, Compliance Horizon Risk

An organisation without current NSX requirements but with a known compliance audit in 18 months that may mandate network segmentation. VVF today at $100 per core: $30,000 per year. VCF today at $160 per core: $48,000 per year. Annual premium for VCF: $18,000. If NSX is required within 18 months and added to VVF at $4,000 per socket for 15 sockets, the annual cost jumps to $90,000 — three times VCF's initial cost. The risk of needing NSX mid-subscription often justifies choosing VCF at the outset.

Scenario 5: 1,500 Cores, Full Enterprise Stack, SDDC Manager Value

A large enterprise where SDDC Manager lifecycle orchestration, Aria Automation, and multi-cluster Kubernetes are operationally deployed and actively used. VCF at $150 per core (large volume enterprise rate): $225,000 per year. VVF equivalent with NSX, extended Aria, and comparable management: $350,000+ per year including standalone component licences. VCF provides consolidated value at lower total cost plus superior architectural coherence.

Alternatives: Nutanix and Azure VMware Solution

No comparison of VCF and VVF is complete without accounting for the two alternatives that have emerged as the primary competitive threat to Broadcom's VMware portfolio. Both should be evaluated before committing to either VCF or VVF at renewal.

Nutanix Cloud Infrastructure provides hyperconverged compute, storage, and networking (through Nutanix Flow) in a modular subscription model at $100 to $150 per core per year for the Pro tier. It does not require forced bundling — organisations purchase only the components they deploy. Migration from VMware to Nutanix requires workload re-platforming from the vSphere hypervisor to Nutanix AHV, which adds migration cost and operational change management. Enterprises that have completed the migration consistently report total cost savings of 40 to 60 percent compared to post-Broadcom VCF pricing.

Azure VMware Solution (AVS) provides a VMware-native cloud environment running VCF workloads on dedicated Azure hardware. It uses a portable VCF subscription from Broadcom plus Azure infrastructure consumption charges. AVS is particularly relevant for organisations reducing on-premises footprint, requiring Azure ecosystem integration, or with workloads that benefit from Azure-native services. Reserved Instances on Azure can reduce the infrastructure component by 30 to 50 percent for predictable workloads.

Including Nutanix or AVS as documented competitive alternatives in Broadcom renewal negotiations improves the discount achievable on both VCF and VVF. A credible migration assessment with either platform represents the most effective preparation for any VMware commercial negotiation.