VMware Cloud Foundation Components
VCF is sold as a single SKU but ships as a bundle of vSphere, vSAN, NSX, Aria, and Tanzu. Knowing which components are bundled, which are sold separately, and how the edition matrix gates feature scope is the single most useful piece of VCF knowledge a buyer can have.
VMware Cloud Foundation is sold as a single SKU but ships as a bundle of multiple distinct product lines. For licensing, procurement, and audit-defence purposes, the customer who treats VCF as a monolithic black box will miss the levers that actually determine value, compliance, and renewal cost. The customer who understands the component breakdown can right-size the deployment, defend the audit, and negotiate the renewal effectively.
This article maps the VCF component stack as it stands in mid-2026, explains what each component does, where it overlaps with separately-sold Broadcom products, and where the licensing entitlement boundaries fall. It is the reference we use with clients during VCF evaluation, deployment design, and renewal planning.
The four principal pillars of VCF
VCF organises its content into four functional pillars: compute, storage, networking, and management. Each pillar contains one or more named products. The bundle ships current-release versions of each, with the interoperability matrix maintained centrally by Broadcom.
Compute — vSphere
vSphere is the hypervisor pillar. VCF includes the current major release of vSphere with full enterprise functionality: DRS, HA, vMotion, Storage vMotion, Fault Tolerance, distributed virtual switching, and the full storage and network adapter integration set. The vSphere included in VCF is functionally equivalent to what was historically sold as vSphere Enterprise Plus, with the addition of the post-acquisition vSphere with Tanzu Kubernetes integration.
The vSphere licence inside VCF covers all cores in the VCF subscription. Customers cannot license fewer vSphere cores than VCF cores; the bundle does not unbundle at the component level.
Storage — vSAN
vSAN is the software-defined storage pillar. Inside VCF, vSAN is included at full capacity — meaning vSAN can be deployed across the entire licensed core count without an additional per-host, per-TB, or per-GB charge. This is the principal commercial differentiation between VCF and VVF, where vSAN is bundled at only 100 GB per core.
vSAN deployment inside VCF supports the full feature set: stretched clusters, fault domains, file services, deduplication and compression, encryption, and the data-services integrations expected of a production storage layer.
Networking — NSX
NSX is the network and security virtualisation pillar. VCF includes NSX with the feature set historically marketed as NSX Advanced — covering software-defined networking, distributed firewalling, load balancing, and the principal automation and observability features of the NSX stack. The standalone NSX Enterprise tier — including advanced security features such as IDS/IPS, the full advanced threat prevention stack, and certain federation features — is positioned outside the bundled VCF entitlement and is sold separately as an add-on.
Management — Aria
Aria is the management and operations pillar — the rebranded vRealize portfolio. VCF Advanced and Enterprise editions include the Aria Suite covering operations, automation, logs, and a defined subset of the broader Aria capability stack. The composition of the Aria suite has been adjusted across catalogue revisions; the current scope as of mid-2026 covers Aria Operations, Aria Automation, Aria Logs, and Aria Operations for Networks at defined capacity.
Components inside Aria
Aria warrants its own component breakdown because it spans the broadest scope of the bundle.
Aria Operations (formerly vRealize Operations)
Aria Operations is the principal monitoring, capacity, and performance management product. Inside VCF, it is licensed for the cores covered by the VCF subscription. It provides health monitoring, capacity planning, performance analytics, and the principal cost-of-ownership reporting expected at the operations layer.
Aria Automation (formerly vRealize Automation)
Aria Automation is the self-service automation and infrastructure-as-code product. It provides catalogue-driven provisioning, blueprint authoring, multi-cloud orchestration, and the policy framework that governs self-service consumption. Inside VCF, it is included; the standalone Aria Automation product is sold separately for customers not on VCF.
Aria Logs (formerly vRealize Log Insight)
Aria Logs is the log management and analysis product. It is included in VCF Advanced and above. Its capacity is bounded by the log volume associated with the VCF deployment; customers ingesting logs from outside the VCF estate at substantial volume should validate scope.
Aria Operations for Networks (formerly vRealize Network Insight)
The networking observability and analytics product, included in VCF Advanced and above. Provides traffic visibility, flow analysis, and the application-mapping capabilities that complement NSX deployment. Scope is bounded by the VCF-licensed cores.
What is bundled vs. what is sold separately
The VCF bundle inclusion list is precise, and the boundary between bundled and separately-sold is the area most customers misunderstand.
Bundled in VCF Advanced or Enterprise
vSphere current release; vSAN at full capacity; NSX at the Advanced feature tier; Aria Operations, Automation, Logs, and Operations for Networks at the deployment scope of the VCF cores; Tanzu Standard for Kubernetes runtime on licensed cores; basic Tanzu Mission Control for TKG-provisioned clusters; HCX for migration use cases at defined scope.
Sold separately, despite Aria/VMware branding
The standalone Aria SaaS offerings (Aria Hub, Aria Guardrails) which sit outside the on-premises Aria suite; NSX Enterprise advanced security features (full ATP, federation, certain advanced features); Tanzu Platform application-platform features; Tanzu Application Service (formerly Pivotal Cloud Foundry); the full Tanzu Mission Control covering non-TKG Kubernetes; advanced HCX scope beyond migration use cases; VMware Live Recovery (formerly Site Recovery Manager and the new VMware Live Cyber Recovery); Workspace ONE for end-user computing.
The phrase "VMware product" no longer maps cleanly to "in VCF." Several products are VMware-branded but sold outside VCF. Validate every component on which you are taking dependency against the current Broadcom catalogue rather than assuming bundle coverage.
The VCF Standard, Advanced, and Enterprise edition matrix
VCF ships in three principal editions, with the component scope progressively expanded across editions.
VCF Standard
The base edition covers vSphere, vSAN at full capacity, NSX at a reduced feature set, and a limited Aria entitlement. Suitable for customers wanting the unified bundle proposition but operating at simpler functional requirements. The principal limitation is the constrained NSX and Aria scope.
VCF Advanced
The mid-tier edition is the most common selection in our client base. Covers vSphere, vSAN at full capacity, NSX at the Advanced feature tier (the most common production NSX scope), the full bundled Aria suite, and the Tanzu Standard entitlement. This is the edition that delivers the principal VCF value proposition for typical enterprise deployments.
VCF Enterprise
The top tier adds expanded scope around advanced workload management, additional Aria scope, and certain advanced features in the management plane. The pricing premium over Advanced is substantial; the justification needs to map to specific Enterprise-only features the customer actually uses. We see meaningful over-buy at the Enterprise tier; right-sizing back to Advanced is a common renewal-time finding.
Capacity considerations across components
The VCF licence covers the licensed cores uniformly across all components, but the practical capacity of each component depends on the workload profile.
vSphere capacity
vSphere scales with the licensed cores. There is no per-VM or per-workload limit within the entitlement. Customers should align core counts to host count and core density.
vSAN capacity
vSAN inside VCF has no per-GB ceiling within the licensed cores. The practical limit is host physical storage capacity. Customers running vSAN-heavy deployments (storage-density-driven sizing) benefit most from the VCF bundle relative to component-level alternatives.
NSX capacity
NSX scope inside VCF Advanced supports the standard production scope. Customers running large-scale NSX deployments with extensive federation, multi-site stretched fabrics, or advanced security workloads should validate scope against the catalogue.
Aria capacity
Aria capacity inside VCF is bounded by the cores covered. Customers monitoring or automating non-VCF estate need to validate whether the bundled Aria entitlement covers the additional scope or whether standalone Aria licensing is required.
How component breakdown affects audit defence
VCF audits typically test three component-level claims, and the customer who understands the component structure is materially better placed to defend each.
First, are the bundled components deployed only within the entitlement? NSX deployed across hosts that exceed the VCF core count, vSAN deployed beyond entitlement, Aria managing outside-scope estate — each is a typical audit finding. The audit team will reconcile deployed-capacity against entitled-capacity for each component independently.
Second, are separately-sold features deployed under the assumption of bundle coverage? NSX Enterprise advanced security features, Tanzu Platform application-platform features, and full Tanzu Mission Control across non-TKG Kubernetes are the three areas where customers most commonly deploy beyond entitlement under the misapprehension that VCF covers them.
Third, is the edition tier matched to the deployed feature set? Customers licensed at VCF Standard cannot use Advanced-tier features. The product enforces some of this technically; some is enforced only at the audit reconciliation. Edition-mismatch findings are common.
Component-level negotiation levers
The unified-bundle pricing of VCF reduces the per-component negotiation surface, but several component-level levers remain available.
NSX scope. The Advanced-vs-Enterprise NSX boundary is negotiable in some cases — particularly the inclusion of specific advanced security features that may or may not be required.
Aria scope. The breadth of bundled Aria components has been adjusted across catalogue revisions; the current scope is the negotiating baseline, with expansion possible for specific features.
Tanzu scope. The boundary between bundled Tanzu Standard and separately-sold Tanzu Platform is the most actively-negotiated component boundary in current VCF deals. Customers building platform-engineering capability inside VCF need to validate scope carefully.
HCX scope. HCX inclusion in VCF is bounded; customers running HCX-heavy migration programmes may need to negotiate expanded scope.
Practical guidance for VCF evaluation
For customers evaluating VCF, the component-breakdown discipline produces three practical recommendations.
Map each VCF component to a deployment intention before signing. If a component will not be deployed, the bundled inclusion is not value — it is an item that may produce future audit findings if deployed outside entitlement, and it does not change the unit price of the bundle.
Validate the boundary between bundled and separately-sold for every component you intend to use. The boundary has moved across catalogue revisions and continues to be adjusted; assumptions based on pre-acquisition VMware knowledge are unreliable.
Negotiate edition selection on the deployed feature set, not on aspirational future state. Enterprise-tier features that will not be used in the contract term do not justify the Enterprise-tier premium.
VCF component interactions and dependencies
VCF components are designed to operate as an integrated stack, with several inter-component dependencies that affect deployment design.
vSphere as the foundation
Every other VCF component depends on vSphere as the underlying hypervisor. vSAN runs on the vSphere kernel; NSX integrates at the vSphere distributed-switching layer; Aria depends on vCenter as a data source. Customers cannot deploy any other VCF component without vSphere underneath.
vSAN and host design
vSAN deployment requires specific host hardware characteristics: a specific cache-and-capacity disk configuration, network connectivity meeting vSAN bandwidth requirements, and host CPU and memory sizing supporting vSAN overhead. The vSAN-Ready Node programme identifies hardware configurations validated for vSAN deployment.
NSX and vSphere version dependencies
NSX requires specific vSphere versions and produces version-pinning effects across the estate. Upgrading vSphere may require parallel NSX upgrade, and the upgrade sequencing matters for production deployments.
Aria and the data-collection layer
Aria components depend on data collection from vCenter, vSAN, NSX, and the workload layer. The data-collection layer needs to be sized adequately for the Aria components to operate at scale; under-sized data collection produces degraded Aria operation.
How VCF SDDC Manager affects deployment
VCF SDDC Manager is the integrated lifecycle-management layer that orchestrates deployment, upgrade, and operation of the VCF stack. Its presence changes the operational model relative to standalone-component deployment in several ways.
Deployment is templated. SDDC Manager orchestrates the deployment of vSphere, vSAN, NSX, and Aria components against validated reference architectures. Customers benefit from the consistency this produces; they sacrifice some flexibility relative to standalone-component deployment where each component is independently provisioned.
Upgrade is coordinated. SDDC Manager manages the cross-component upgrade sequencing, validating compatibility before applying upgrades. The coordination simplifies upgrade operation; it also constrains the customer's ability to selectively upgrade individual components outside SDDC Manager's cadence.
Lifecycle management is centralised. The integrated lifecycle approach centralises patch management, configuration management, and certificate management across the VCF stack. The centralisation benefits operational consistency; it also concentrates operational dependency on SDDC Manager.
Customer profiles and component priorities
The right VCF component priorities depend on the customer's deployment profile. Three profiles cover most enterprise VCF deployments.
Infrastructure-modernisation customers, replacing legacy vSphere estates with current VCF, prioritise the vSphere and Aria components for the operational continuity benefits. vSAN and NSX features are secondary; the principal value is the modernised vSphere foundation with integrated lifecycle management.
Private-cloud-build customers, constructing a self-service private cloud from VCF, prioritise the full VCF stack with NSX, Aria Automation, and Tanzu features. The integration of the stack is the principal value; selective component deployment defeats the private-cloud-build pattern.
Cost-optimisation customers, consolidating workload onto VCF for the cost-of-density benefits, prioritise the vSphere and vSAN components for the consolidation economics. NSX and Aria features are secondary; the principal value is the workload-density and storage-density benefits.
Related reading
For deeper detail on adjacent topics, see the VCF licensing explainer, the VMware licensing complete guide, vSAN licensing, NSX licensing, Aria/vRealize licensing, and Tanzu licensing.