VMware Cloud Foundation vs vSphere Foundation: Cost Comparison

The Decision Framework: VCF vs VVF

Broadcom's 2024 consolidation of the VMware portfolio created two principal on-premises compute bundles. VMware Cloud Foundation (VCF) is the full software-defined data centre stack — compute, networking, storage, management, and orchestration in a single per-core subscription. VMware vSphere Foundation (VVF) is the entry-level bundle — compute and storage, without software-defined networking (NSX) or the enterprise management capabilities (SDDC Manager, Aria Suite Enterprise) included in VCF.

The choice between VCF and VVF is not simply a per-core price comparison. It requires understanding the three dimensions where the bundles fundamentally differ: NSX inclusion, vSAN capacity entitlement, and management stack depth. In many enterprise deployment scenarios, the apparent 2.6x per-core premium for VCF collapses when the included capabilities are compared against their standalone cost.

All perpetual VMware licences were moved to subscription in 2024. Both VCF and VVF are subscription-only products available on one-year, three-year, or five-year terms. The choice between them must account for the full subscription economics including support costs, which run 3 to 5 times higher than the pre-Broadcom perpetual maintenance model for equivalent functionality.

What Each Bundle Includes: The Critical Differences

VVF Component Summary

VMware vSphere Foundation includes vSphere Enterprise Plus (with ESXi and vCenter Server), vSphere Lifecycle Manager for patching and image management, Aria Suite Standard (basic operations monitoring), one Tanzu Kubernetes cluster for container workloads, and vSAN at 250 GiB of raw capacity per licensed core.

What VVF does not include is equally important: no NSX (software-defined networking and micro-segmentation), no SDDC Manager (the lifecycle orchestration platform for multi-domain VCF deployments), no Aria Suite Enterprise (advanced automation and network analytics), no HCX (hybrid cloud migration), and no vDefend (ransomware prevention).

VCF Component Summary

VMware Cloud Foundation includes everything in VVF plus NSX (full network virtualisation and distributed firewalling), SDDC Manager, Aria Suite Enterprise (Operations, Operations for Logs, Automation, and Operations for Networks), HCX for hybrid cloud migration, vDefend for lateral security, vSphere Kubernetes Services (multiple clusters), and an expanded vSAN entitlement of 1 TiB per licensed core — four times the VVF allocation.

The NSX Dividing Line

The most consequential difference between VCF and VVF is NSX. NSX provides software-defined networking capabilities that enable micro-segmentation, distributed firewalling, overlay network virtualisation, and software-defined load balancing at the hypervisor layer. For environments subject to PCI DSS, HIPAA, ISO 27001, or SOC 2 compliance requirements that mandate network segmentation at granular levels, NSX is frequently not optional.

Organisations that need NSX and start on VVF will need to add NSX as a separate licence. NSX adds approximately $3,000 to $4,000 per year per licensed CPU (rough estimate based on available pricing information). At that add-on cost, VVF plus NSX for a 500-core environment (approximately 25 to 30 CPU sockets) adds roughly $75,000 to $120,000 per year to VVF's base cost, substantially narrowing the gap with VCF — and often making VCF the more economical choice.

Pricing Comparison: List and Enterprise Negotiated

Understanding both list pricing and achievable enterprise negotiated rates is essential for accurate cost modelling. List pricing establishes the ratio; negotiated pricing determines actual spend.

List Pricing

VVF list price: $135 per core per year. VCF list price: $350 per core per year. The ratio is 2.59x — VCF costs 159 percent more than VVF on a per-core list basis. For an organisation licensing 500 cores, the annual cost difference at list is $107,500 per year, or $322,500 over a three-year subscription.

Enterprise Negotiated Pricing

In practice, large enterprise customers achieve significant discounts from list on both products. Typical enterprise negotiated ranges: VVF at $80 to $120 per core per year; VCF at $140 to $180 per core per year. At the midpoints of these ranges ($100 for VVF and $160 for VCF), the negotiated ratio narrows to 1.6x — VCF costs 60 percent more on a per-core basis, not 159 percent. For a 500-core enterprise deployment, the annual cost difference at negotiated pricing is approximately $30,000 per year, or $90,000 over three years.

This narrowed ratio fundamentally changes the VCF vs VVF decision calculus. At list pricing, VVF appears compelling for organisations that do not immediately need NSX. At negotiated enterprise pricing, the incremental cost of VCF over VVF is much smaller — and the included capabilities (NSX, Aria Enterprise, SDDC Manager) are much easier to justify.

Three Scenario Cost Comparisons

Scenario A: Small Compute-Focused Deployment (300 Cores, No NSX, Low Storage)

An organisation with 300 licensed cores, standard enterprise workloads, no compliance-mandated network segmentation requirement, and existing SAN storage infrastructure. VVF at $100 per core per year costs $30,000 annually. VCF at $160 per core per year costs $48,000 annually. Annual difference: $18,000 in favour of VVF. Over three years: $54,000 saved on VVF.

In this scenario, VVF is clearly the right choice. The NSX, SDDC Manager, and extended Aria Suite capabilities in VCF provide no value for this deployment profile, and the storage entitlement advantage (1 TiB vs 250 GiB per core) is irrelevant with existing SAN infrastructure.

Verdict: VVF is the correct choice. Three-year savings: $54,000.

Scenario B: Medium Enterprise with NSX Requirement (500 Cores, NSX Required, Moderate Storage)

An organisation with 500 cores, a PCI DSS compliance requirement that mandates network micro-segmentation, and hyper-converged storage running on vSAN. VVF at $100 per core is $50,000 annually. Adding NSX as a standalone licence for 25 CPU sockets at $4,000 per socket per year adds $100,000, for a total of $150,000 annually on VVF plus NSX.

VCF at $160 per core is $80,000 annually — $70,000 less than VVF plus NSX, and VCF includes all NSX capabilities plus SDDC Manager, Aria Enterprise, and four times the vSAN storage entitlement. Over three years, VCF saves $210,000 versus VVF plus NSX.

Verdict: VCF is significantly more cost-effective once NSX is required. Three-year savings versus VVF+NSX: $210,000.

Scenario C: Large Storage-Intensive Enterprise (1,000 Cores, NSX, High Storage)

An organisation with 1,000 licensed cores, NSX required for multi-tenant isolation, and heavy vSAN usage for hyper-converged storage running primary application workloads. VVF provides 250 GiB per core — 250 TiB of vSAN capacity at 1,000 cores. VCF provides 1 TiB per core — 1,000 TiB (1 PiB) of vSAN capacity. If the storage requirement is 600 TiB, VVF would require purchasing additional vSAN capacity at $0.08 per GiB per year (approximate), adding $28,000 per year to the VVF cost.

Adding NSX to VVF for 50 CPU sockets at $4,000 per socket: $200,000 annually. Total VVF plus NSX plus additional vSAN: $100,000 (VVF) plus $200,000 (NSX) plus $28,000 (extra vSAN) = $328,000 per year. VCF at $160 per core: $160,000 per year — saving $168,000 annually versus the equivalent VVF-based configuration. Over three years: $504,000 saved by choosing VCF.

Verdict: VCF is substantially more economical at scale with NSX and storage needs. Three-year savings: $504,000.

The vSAN Storage Entitlement Difference

The four-times difference in vSAN capacity between VCF (1 TiB per core) and VVF (250 GiB per core) is frequently the decisive economic factor in storage-intensive environments. Understanding this difference requires converting core counts to raw storage capacity.

A 400-core environment on VVF receives 100 TiB of raw vSAN capacity. The same environment on VCF receives 400 TiB. If the required usable storage (after vSAN's RAID-1 or RAID-5/6 overhead) exceeds what the VVF entitlement provides, the cost of additional vSAN capacity quickly erodes VVF's per-core price advantage. Organisations with storage growth trajectories — database workloads, file services, large virtual machine environments — frequently find that VCF's storage entitlement makes it the lower total cost option within 12 to 24 months of deployment.

When to Choose VVF

VVF is the appropriate choice when all of the following conditions apply: no current requirement for NSX-level network segmentation (and no compliance mandate that will require it within the contract term), existing external storage infrastructure (SAN, NAS, NFS) that makes the vSAN entitlement difference irrelevant, relatively small deployment scale (below 400 cores) where the incremental VCF cost per core is material, and no requirement for Aria Suite Enterprise automation or SDDC Manager orchestration capabilities.

Organisations that choose VVF with a plan to add NSX later should model the total cost carefully before committing. Switching from VVF to VCF mid-subscription is a contract renegotiation event with Broadcom, not a simple licence upgrade, and timing this transition to a renewal event produces the best commercial outcome.

When to Choose VCF

VCF is the appropriate choice when any of the following conditions apply: NSX is required or planned within the contract term, the vSAN storage requirement exceeds the VVF entitlement at current or projected core counts, the organisation benefits from SDDC Manager lifecycle orchestration at scale, the Aria Suite Enterprise capabilities (automation, network analytics) will be actively deployed, or the deployment is part of a hybrid cloud strategy requiring HCX migration capabilities.

The economic threshold at which VCF becomes more cost-effective than VVF plus NSX is approximately 300 to 400 cores for organisations that genuinely need NSX coverage across the full environment. Below this threshold, VVF plus selective NSX licensing for specific clusters may be more economical. Above it, VCF's consolidated pricing almost always wins the total cost calculation.

Alternatives Beyond the Broadcom Portfolio

Both VCF and VVF should be evaluated against two significant alternatives that offer competitive functionality at lower total cost in many enterprise scenarios. Nutanix Cloud Infrastructure provides hyperconverged compute and storage with modular networking at $100 to $150 per core per year for the Pro tier — comparable to VVF pricing without forced bundling, and significantly lower than VCF. Azure VMware Solution runs VMware workloads natively in Azure with HCX for workload migration, eliminating on-premises hardware investment at the cost of cloud consumption charges.

These alternatives should be evaluated seriously before committing to either VCF or VVF at renewal. The cost savings achievable through Nutanix migration have been documented at 40 to 60 percent by multiple enterprises that have completed the migration. Even if migration is ultimately not pursued, the documented competitive comparison strengthens the negotiating position with Broadcom's account team and directly improves the discount achievable on either VCF or VVF.