VMware VCF Licensing Explained

VMware Cloud Foundation, abbreviated VCF, is the flagship Broadcom bundle. It is the largest commercial proposition in the Broadcom VMware catalogue and the one Broadcom most prefers to sell. For customers operating a multi-product VMware estate or building a private cloud, VCF is the licensing vehicle that consolidates vSphere, vSAN, NSX, and the Aria management stack into a single subscription. For customers whose primary VMware use is the hypervisor alone, VCF is typically over-buying.

The complexity of VCF licensing has produced significant confusion in the customer base. The bundle contains many components, the edition matrix has changed across catalogue revisions, the pricing mechanics interact in non-obvious ways, and the minimum-commitment provisions are unfamiliar to customers who operated under the pre-acquisition catalogue. This guide is the practical explainer.

What VCF actually contains

VCF is a bundle of four principal product families.

vSphere (the compute hypervisor)

vSphere is the foundational component — the bare-metal hypervisor and management layer that runs virtual machines. Inside VCF, customers receive the current vSphere release with full Enterprise-class functionality, including features such as DRS, HA, vMotion, and the storage and network integrations expected of a production hypervisor. This is the same vSphere available to VVF customers and the same vSphere available historically as Enterprise Plus.

vSAN (the software-defined storage layer)

vSAN aggregates the storage from the physical hosts into a single distributed storage pool. Inside VCF, vSAN is included at full capacity — that is, vSAN can be deployed across the entire licensed core count without an additional per-host or per-GB charge. This is a material difference from VVF, where vSAN is included only at 100 GB per core, suitable for workload-adjacent storage but not for primary storage tier replacement.

NSX (the network and security virtualisation layer)

NSX provides software-defined networking, micro-segmentation, and east-west traffic security. Inside VCF, NSX is included with full functionality. NSX is the component most often cited by VCF buyers as the reason for the bundle choice — standalone NSX has been progressively more constrained in availability outside VCF, and NSX functionality is essential for customers running zero-trust or micro-segmentation security postures.

Aria (the management and automation stack)

The Aria suite is the post-acquisition rebrand of the vRealize tooling: Aria Operations (formerly vRealize Operations), Aria Automation (formerly vRealize Automation), Aria Logs (formerly vRealize Log Insight), and Aria Networks (formerly vRealize Network Insight). The full Aria suite is included inside VCF; VVF includes a restricted Aria subset. The full Aria stack is meaningful for customers building self-service private cloud, performing capacity planning at scale, or operating large multi-cluster deployments.

The edition matrix

VCF has been offered in multiple editions across the catalogue's lifetime. The current structure has settled on three principal editions, though the specific feature set in each has been adjusted in catalogue revisions and is likely to continue to shift.

VCF Standard

The entry-level VCF edition contains the four product families with reduced NSX functionality and reduced Aria functionality. For customers acquiring VCF principally for the vSphere-plus-vSAN combination, Standard can be sufficient. The lower headline price makes Standard the typical starting point in negotiations even when the eventual deployment uses Advanced features.

VCF Advanced

The mid-tier edition contains full NSX functionality and most Aria components. Advanced is the commercial centrepiece — most enterprise VCF deployments are licensed at Advanced. The combination of full NSX and substantive Aria functionality is what makes the bundle economic for multi-product use.

VCF Enterprise

The top-tier edition adds the remaining Aria components, advanced automation tooling, and various enterprise-grade extensions. Enterprise is the edition customers acquire when building substantive private-cloud platforms with self-service, advanced capacity planning, and multi-site governance.

Pricing mechanics

VCF is priced per physical core, on subscription terms typically of three or five years. The mechanics are simple in principle and material in practice.

Per-core unit pricing

The unit of pricing is the physical core. A server with two sockets and twenty cores per socket requires forty core licenses. A minimum of sixteen cores per socket applies even on smaller sockets — a server with two sockets and eight cores per socket still requires thirty-two cores. Customers running high-core-count modern servers should price under the actual core count; customers running smaller older hardware should price under the sixteen-core-per-socket minimum.

Subscription term

Three years is the most common term; five years is offered at deeper headline discounts. The choice is a trade-off between commitment certainty and pricing protection. Five-year terms lock in pricing and avoid one renewal event, which has historically been a meaningful inflation point. Three-year terms preserve flexibility, particularly for customers actively evaluating migration alternatives.

Minimum commitment

VCF carries a minimum core commitment that has shifted across the catalogue. Recent SKUs have carried minimum commitments in the range of sixteen-to-thirty-two cores per host or a defined minimum per environment. For larger environments the minimum is rarely the binding constraint; for small-to-mid environments the minimum can substantially affect the unit economics.

List versus negotiated pricing

Negotiated discounts against list vary widely. Mid-size customers typically see discounts in the twenty-to-forty per cent range; larger customers see deeper discounts. The principal levers are deal size, term length, competitive alternatives credibly under evaluation, and timing relative to Broadcom's fiscal year-end. Customers who do not negotiate against list typically pay materially more than necessary.

What is included that is easy to miss

Some components inside VCF are valuable but get overlooked because they were less prominent in the pre-acquisition catalogue.

Tanzu Standard within VCF

A Tanzu Standard entitlement is included in VCF in current SKUs — allowing customers to run Kubernetes workloads on the licensed cores without a separate Tanzu purchase. For customers running mixed VM and container workloads, this is a non-trivial bundled value.

Aria Operations and Aria Logs

The bundled monitoring and logging components are operational tooling many customers historically bought separately. Inside VCF they are included at the licensed core count.

Site Recovery Manager equivalents

VCF includes capabilities for site recovery and workload mobility that historically were licensed as separate add-ons. The exact functionality varies across editions and catalogue revisions but is worth examining at purchase time.

What is not included

Several products customers expect to be included are not in VCF or are available only as add-ons.

Workload extensions such as VMware Cloud Disaster Recovery, certain Tanzu Application Platform components, and some industry-specific extensions are licensed separately. Carbon Black Workload — the Broadcom-owned workload security product — is licensed under Carbon Black, not VCF. Some legacy products such as Workspace ONE and Horizon are licensed under separate End-User Computing arrangements. Customers building a complete VMware-based platform should identify which components they need that are not bundled into VCF and price the full stack rather than the VCF subscription alone.

The VCF-versus-VVF decision

The single most consequential decision for most customers in the current catalogue is VCF or VVF. Our complete VMware licensing guide covers the framework in detail; the summary for this guide is as follows.

VCF is the right answer for customers who deploy or plan to deploy two or more of: full vSAN as primary storage, NSX for software-defined networking or security, and substantial Aria-managed private-cloud infrastructure. VVF is the right answer for customers whose primary use is vSphere as a hypervisor with traditional shared storage and conventional network architecture.

The price differential is meaningful — VCF per core is typically two-to-three times VVF per core, depending on edition. The bundled functionality has to be used to justify the differential. Customers who commit to VCF and then deploy only the vSphere component end up paying for substantial unused entitlement.

Audit considerations specific to VCF

VCF deployments carry their own audit-risk profile, distinct from vSphere-only environments. Three areas drive audit findings in VCF deployments.

First, the core count claimed under the subscription has to match the cores running VCF workloads in production. Customers using VCF entitlements on hosts running non-VCF workloads, or running VCF software on more cores than entitled, are the typical first audit finding.

Second, the bundled components must be deployed within the entitlement. NSX deployed across more cores than licensed VCF, vSAN deployed beyond the VCF entitlement, or Aria components deployed without the corresponding VCF coverage are findings that surface in audits.

Third, edition compliance matters. Customers licensed at VCF Standard cannot deploy VCF Advanced functionality. The product itself enforces some of this but not all, and audit findings on edition mismatch are common.

What VCF customers should do at renewal

The renewal decision for an existing VCF customer turns on whether the current bundle still matches deployment patterns and where the pricing has landed relative to alternatives.

Audit your actual deployment against the bundle components. If the deployment uses primarily vSphere, with limited NSX or Aria, consider whether VVF is now the better fit. If the deployment uses the full stack as intended, VCF remains the right vehicle; the focus shifts to negotiating renewal pricing, securing price-protection language, and managing the commitment volume.

Compare VCF renewal pricing to the cost of standalone or alternative-vendor equivalents for the components you actively use. For customers using only a subset of VCF, the cost-of-substitution analysis is a meaningful negotiating tool — not because most customers will actually rebuild around alternatives mid-VCF, but because the credible alternative changes the negotiating posture.

How VCF is procured: typical commercial motion

The commercial motion for acquiring VCF differs in important ways from the pre-acquisition VMware purchase process. Understanding the typical motion helps customers prepare effectively.

The deal originates either with Broadcom directly — for larger and named-account customers — or with a Broadcom Advantage Program partner for smaller and mid-market deals. The named-partner channel is now the principal route for most enterprise deals; the choice of partner is largely determined by territory and segment assignment, with limited customer ability to choose. Once the deal is in motion, the commercial discussion typically involves a Broadcom account executive, a Broadcom technical specialist for VCF, and the partner's commercial counterpart. Customer-side participation typically pulls in procurement, IT leadership, and (for any meaningful deal) external advisory.

The deal cycle is longer than pre-acquisition VMware deals were. The increased complexity of the VCF bundle, the conversion-from-perpetual arithmetic for legacy customers, and the contract-template complexity all extend the typical cycle to three-to-six months for a substantive engagement. Customers running tighter cycles than this typically accept worse-than-achievable terms in exchange for closure.

VCF deployment patterns we see in 2026

Three deployment patterns dominate among VCF customers as of mid-2026.

Full private cloud

The pattern Broadcom most prefers: VCF Advanced or Enterprise deployed as a fully integrated private cloud, with vSphere as the hypervisor, vSAN at substantive capacity, NSX for software-defined networking and security, and Aria for management and self-service. Adoption sits with customers who have committed to VMware as their strategic infrastructure platform and who deploy the bundle as a coherent stack.

Bundle for compute, alternatives for adjacency

Customers who acquire VCF for the vSphere and partial-vSAN inclusion but who deploy alternative tooling for networking (relying on the underlying physical network rather than NSX) and management (using non-Aria operations platforms). This pattern wastes the NSX and Aria entitlements but is observed where the customer's existing operational tooling investment is substantial.

Reluctant VCF

Customers who would prefer VVF or standalone but who are pushed into VCF by deal structure, partner pricing, or strategic-account dynamics. This pattern is observed particularly in larger named accounts where the deal-economics gap between VCF and VVF is closed by aggressive discounting on VCF. The pattern produces meaningful unused entitlement and is the source of significant renewal-time dissatisfaction.

The Tanzu question inside VCF

VCF current SKUs include a Tanzu Standard entitlement, providing Kubernetes runtime on the licensed cores. For customers running mixed VM and container workloads, this is meaningful bundled value — the alternative is acquiring a separate Tanzu or other Kubernetes-platform licence at additional cost.

The Tanzu inclusion has limits. Tanzu Application Platform — the higher-tier Tanzu offering with developer-experience tooling, application templating, and platform-engineering features — is licensed separately under the Tanzu Platform business unit's own commercial structure. Customers requiring the full Application Platform should not assume it comes inside VCF.

For customers acquiring VCF principally for the VM workloads with Tanzu Standard as a side benefit, the inclusion is value. For customers building a substantive Kubernetes-centred platform, the standalone Tanzu Platform commercials should be evaluated independently of the VCF deal.

Related reading

For deeper detail on adjacent topics, see the VMware licensing complete guide, vSphere licensing changes, vSAN licensing after Broadcom, and NSX licensing changes. For audit defence in VCF deployments, see our VMware audit defence guide.