VMware Cloud Foundation (VCF) is Broadcom's primary enterprise subscription offering following its 2023 acquisition and restructuring of the VMware product portfolio. Understanding what VCF actually includes — and how it compares to its companion product VMware vSphere Foundation (VVF) — is essential before entering any commercial discussion with Broadcom's sales team.
The product packaging and naming changes that Broadcom has introduced since the acquisition have created significant confusion in the enterprise buyer market. Many organisations are paying for components they do not use, or failing to negotiate tier selection appropriately because they lack a clear picture of what each product delivers.
This guide provides the product knowledge foundation that enterprise buyers need. For the commercial context and negotiation tactics, see our complete VMware Broadcom licensing guide and our dedicated article on negotiating Broadcom VMware contracts.
What Is VMware Cloud Foundation?
VMware Cloud Foundation is a comprehensive hyperconverged infrastructure (HCI) platform that bundles the core components of VMware's private cloud stack into a single subscription product. It is designed to provide everything required to build and operate a software-defined data centre — compute virtualisation, storage virtualisation, network virtualisation, and management tooling — from a single vendor subscription, licensed on a per-physical-core basis.
The VCF architecture is built around four primary technology pillars. vSphere provides the hypervisor layer — the compute virtualisation that has been VMware's foundational product for over two decades. vSAN delivers software-defined storage, eliminating dedicated SAN infrastructure by pooling server-attached storage. NSX provides network virtualisation and micro-segmentation, enabling software-defined networking overlays. Aria (formerly vRealize) delivers management, operations, automation, and cost management capabilities across the VCF environment.
The critical commercial implication of this bundling is that VCF subscribers pay for all four pillars regardless of utilisation. An organisation that uses vSphere and vSAN but has not deployed NSX or Aria is still paying for those components in their per-core subscription cost.
What Is VMware vSphere Foundation?
VMware vSphere Foundation (VVF) is the simplified entry-level subscription introduced alongside VCF. It provides the hypervisor and vCenter management components without the integrated vSAN, NSX, and Aria layers. It is appropriate for organisations that have separate storage infrastructure (traditional SAN, NAS, or alternative software-defined storage), do not require software-defined networking from VMware, and have simpler operational management requirements.
VVF carries approximately 30–40% lower per-core list pricing than VCF, making it significantly cheaper for qualifying infrastructure. The question of whether VVF or VCF is the right tier for a given organisation is one of the most commercially significant decisions in the Broadcom transition — and one that Broadcom's account teams are, predictably, not incentivised to help buyers get right.
VCF vs VVF: Feature Comparison
| Component | VCF | VVF | Notes |
|---|---|---|---|
| vSphere Hypervisor | ✓ Included | ✓ Included | Core compute virtualisation |
| vCenter Server | ✓ Included | ✓ Included | Management infrastructure |
| vSAN (HCI Storage) | ✓ Included | ✗ Not included | Software-defined storage virtualisation |
| NSX (Network Virt.) | ✓ Included | ✗ Not included | Micro-segmentation and overlay networking |
| Aria Operations | ✓ Included | Limited | Operational management and analytics |
| Aria Automation | ✓ Included | ✗ Not included | Infrastructure-as-code and workflow automation |
| SDDC Manager | ✓ Included | ✗ Not included | Automated deployment and lifecycle management |
| List price (approx.) | $130–150/core/yr | $40–55/core/yr | Pre-discount list prices |
Licensing Rules and Compliance Requirements
All Cores Must Be Licensed
VCF and VVF subscriptions require licensing of all physical cores on all servers running VMware software. There is no capacity-based licensing, no per-VM licensing, and no exclusion for test or development servers. If a server has VMware hypervisor software installed, all physical cores on that server must be included in the subscription.
This rule has significant implications for organisations that previously managed their licensing with a mixture of licensed production servers and unlicensed development infrastructure. Under Broadcom's subscription model, the full physical estate must be in scope.
Minimum Core Requirements
Broadcom has established minimum core count thresholds for VCF subscriptions. These minimums vary by agreement type and are subject to commercial negotiation, but buyers should be aware that very small deployments may face minimum purchase requirements that make per-core pricing less relevant than the minimum fee.
True-Up Frequency
VCF and VVF agreements include true-up provisions for core count changes during the subscription period. Broadcom's standard contract language requires annual true-ups at list price for any overage — meaning organisations that add servers during the subscription year may face true-up charges that are calculated at full list price rather than at the negotiated agreement discount. This is a negotiable contract term, and sophisticated buyers should ensure their agreement extends agreement-level discounts to true-up quantities.
Key Compliance Risk: vSAN OSA (Original Storage Architecture) and ESA (Express Storage Architecture) licences are no longer available separately. Organisations that previously purchased vSAN separately and are now on perpetual vSAN licences must include vSAN in their VCF subscription if they intend to maintain supported vSAN functionality. Running perpetual vSAN on an unsupported version while paying for VCF hypervisor only is not a supported configuration.
Selecting the Right Tier: VCF or VVF?
The tier selection decision should be driven by current utilisation and the 3-year roadmap for each component, not by Broadcom's commercial preference. The key questions are: Does your organisation actively use or plan to deploy vSAN within the next 18 months? Does your organisation use or plan to deploy NSX within the next 18 months? Is Aria automation and operations tooling part of your current or near-term infrastructure management approach?
If the honest answer to all three questions is no, VVF is almost certainly the appropriate tier. The organisations that genuinely benefit from VCF are those using the integrated HCI stack — vSphere, vSAN, and NSX together — where the management integration and unified support model provide real operational value.
A common pattern we observe is organisations defaulting to VCF because Broadcom's sales team presents it as the "enterprise standard" or because VCF was in the previous solution bundle, when a detailed utilisation analysis would support VVF at significantly lower cost. The savings from correct tier selection — on a large enterprise estate — can be $500K–$2M+ annually.
Multi-Cluster and Hybrid Environments
Many enterprise organisations operate mixed-purpose clusters — some running HCI workloads (vSAN), others running traditional storage-attached workloads. In these environments, it may be commercially appropriate to licence HCI clusters at VCF and storage-attached clusters at VVF, if Broadcom's agreement terms permit this split.
This is a commercially complex position to negotiate, and Broadcom's standard contract structure pushes buyers toward a uniform tier across the estate. Independent advisory support is particularly valuable in these scenarios — advisors with active VMware experience know which combinations are achievable and how to structure proposals that Broadcom will engage with commercially.
VCF and Cloud Integration
One component of VCF's value proposition is its integration with VMware Cloud on AWS, Azure VMware Solution, and Google Cloud VMware Engine — managed VMware environments on hyperscaler infrastructure. These cloud services are separately priced from on-premises VCF subscriptions, but having VCF on-premises simplifies hybrid cloud workload management and supports consistent tooling across the estate.
For organisations evaluating cloud migration alongside their VCF transition decision, it is worth modelling the cost of VCF on-premises plus cloud extension versus a full migration to hyperscaler-native services. In many cases, the cloud extension path preserves operational familiarity while providing a credible migration pathway that reduces long-term on-premises infrastructure commitment.
For cloud contract context, our cloud contracts guide provides the commercial framework for evaluating hyperscaler alternatives to on-premises VCF.
Common Licensing Mistakes
The most frequent VCF licensing mistakes we encounter in advisory engagements are paying for VCF when VVF is appropriate for the actual workload profile; licensing cores without completing an infrastructure audit, resulting in over-purchase of 15–30%; accepting standard true-up language that prices overages at list rate rather than contracted discount; failing to include escalation cap provisions in multi-year agreements; and not challenging bundled add-ons (Aria Advanced, NSX Advanced) that are included in higher-tier SKUs but have no near-term utilisation.
Each of these mistakes has a quantifiable cost impact. An enterprise running 8,000 cores in an environment where VVF is appropriate but VCF has been selected is paying approximately $720K–$960K per year in unnecessary subscription cost at list price — and $430K–$580K at market negotiated price. This scale of preventable waste is common and correctable.
Working With Independent Advisors on VCF Licensing
The combination of technical complexity (tier selection, compliance requirements, hybrid configurations) and commercial complexity (discount structures, true-up mechanics, contract terms) makes VCF licensing one of the scenarios where independent advisory adds most sustained value.
Advisory firms like Redress Compliance approach VCF engagements with a structured methodology: infrastructure audit to establish correct core count and tier, commercial benchmarking to establish market reference pricing, negotiation management to close the deal at or below market price, and contract review to ensure protective terms are in place. This end-to-end approach consistently delivers outcomes that in-house teams managing their first or second VCF transition cannot replicate independently.
Our software licensing advisory practice provides specialised VCF licensing and negotiation support. See also our analysis of Broadcom VMware market prices for current benchmarking reference, and our VMware Broadcom Buyer Guide for comprehensive guidance on the full commercial engagement process.