VCF looks straightforward on a slide: vSphere, vSAN, NSX, Aria, HCX. In practice each component carries its own licensing model, deployment overhead, and customer-side consumption rate. This deep dive walks through every VCF component, the entitlement detail that decides cost, and the carve-outs Broadcom commercial teams will quietly accept in a real renewal.
VMware Cloud Foundation is a single subscription SKU that bundles vSphere, vCenter, vSAN (full entitlement), NSX, Aria Operations, Aria Operations for Logs, Aria Automation, Aria Lifecycle, and HCX. The bundle is what Broadcom now sells as the upper-tier platform for customers running the full VMware stack in production. The economics of VCF only make sense for customers who consume the network virtualisation and automation layers; for customers running vSphere as a hypervisor, VCF is meaningful overspend.
The compute virtualisation foundation. VCF includes the full vSphere entitlement — ESXi, vMotion, HA, DRS, vCenter Server — with no edition gating. This is the component every customer consumes; it is the floor under any conversation about VCF value.
The largest single entitlement differentiator vs VVF. VCF includes vSAN at 1 TiB per core, where VVF includes only 100 GB per core. For a 1,000-core estate, the VCF vSAN entitlement is 1,000 TiB; the VVF entitlement is 100 TiB. Customers running vSAN at scale on dense storage configurations are the natural VCF buyers; customers running vSAN lightly or not at all are overpaying for unused capacity.
VMware's network virtualisation product, included at the Advanced edition level inside VCF. NSX consumption typically falls into three buckets: customers running NSX as a production microsegmentation platform across the estate; customers running NSX for a specific workload (typically VDI or DMZ); and customers who have NSX licensed inside VCF but have not deployed it. The third bucket is large — in our experience across 340+ engagements, somewhere between 30% and 45% of VCF customers do not have NSX deployed in production. For those customers, NSX is the strongest argument against VCF.
Component-level consumption telemetry is the difference between VCF and VVF. Without it, the bundle stays at VCF.
VMware's monitoring and capacity management platform, included in both VVF and VCF. This is the component most customers actually use, and is one reason VVF (which also includes Aria Operations) is a viable choice for monitoring-only customers. The differentiator at the Aria layer is what comes alongside Operations — Automation and Lifecycle in VCF, neither in VVF.
Self-service provisioning, policy-driven workload placement, and infrastructure-as-code orchestration. The deployment maturity required to make Aria Automation valuable is significant: a customer needs blueprint design, policy modelling, and an operational team to maintain the platform. Aria Automation is the single component most often licensed inside VCF and most often unused; it is also the most credible carve-out conversation Broadcom will quietly accept on multi-year deals.
Lifecycle management for the Aria suite components themselves — patch, upgrade, certificate management for Operations, Automation, Logs. Aria Lifecycle has no standalone value for customers who do not deploy multiple Aria components in production. It is genuinely a bundle-filler component, and Broadcom commercial teams know this.
VMware's workload migration platform — live migration of VMs between on-premises and cloud, between sites, and between vSphere versions. HCX is highly valuable during migration projects and adds little ongoing value after a migration completes. Customers in active migration cycles — cloud lift, data centre consolidation, version uplift — consume HCX heavily; customers in steady-state operations do not.
Centralised log aggregation across the VMware stack. Included in both VVF (basic tier) and VCF (full tier). Most customers either consume Aria Logs as the primary log platform for the VMware estate or run an enterprise log platform (Splunk, Elastic, Datadog) that subsumes it. The dual-tooling cost is a frequent finding in compliance assessments.
The right tool for VCF-vs-VVF analysis is Aria Operations itself, configured to report on workload distribution, network policy usage, vSAN consumption, and Aria component activity. Six months of clean telemetry produces a defensible case for either bundle. Without telemetry, the conversation defaults to whatever Broadcom proposes, and that proposal defaults to VCF. The data work is the negotiation work; the rest is paperwork.
Broadcom officially treats VCF as indivisible. In commercial practice, three carve-out patterns appear in real deals. First, a discount applied to the VCF SKU that effectively reflects unused components — not a true carve-out, but the financial result of one. Second, an Aria Automation-specific commitment-level adjustment on multi-year deals where the customer is buying VCF but documenting non-deployment of Automation. Third, a transition allowance on co-term renewals where one site consumes VCF and another VVF, before consolidation. None of these are listed on the price book; all of them require named-account commercial intervention.
Full bundle decoder with component benchmarks, telemetry checklists, and counterproposal templates.
VCF makes sense when at least three of the following are true: NSX is deployed across more than 40% of workloads; Aria Automation has production blueprints and consumption beyond pilot; vSAN consumption exceeds 200 GB per core (the VVF ceiling becomes a constraint); a credible migration use case exists in the next 24 months requiring HCX; the customer needs the lifecycle automation Aria Lifecycle provides. Customers meeting three of five conditions almost always end up financially neutral or ahead with VCF. Customers meeting one or none consistently overspend.
VVF makes sense when the customer is consuming vSphere as a hypervisor, monitoring with Aria Operations, optionally running vSAN under 100 GB per core, and not deploying network virtualisation or self-service provisioning at scale. This describes a large share of mid-market and many enterprise customers. The VVF price differential vs VCF varies by deal size but is consistently in the 30–45% range on per-core list, and the savings compound over multi-year terms.
Map the eight components against actual consumption. For each, mark the deployment state as "production at scale," "production limited scope," "pilot only," or "not deployed." VCF is justified when at least four components score "production at scale." VVF is the correct answer when three or fewer components fall into that category. Anything in between is a negotiation.
Our VMware practice is led by former VMware and Broadcom commercial veterans. We work for buyers only.
Weekly compliance intelligence for IT leaders.
