This is Part 1 of a 10-part series that takes VMware Cloud Foundation from first principles all the way to a working lab build. If you have landed here cold, start at the top. Everything after this assumes the groundwork we cover below.
The Short Answer
VMware Cloud Foundation (VCF) is Broadcom’s flagship private cloud platform. Strip away the enterprise marketing, and it boils down to a single objective: VCF bundles the entire VMware software stack, spanning compute, storage, networking, security, and cloud management, into an automated platform that you deploy, patch, and operate as a unified system.
If you have worked with traditional vSphere, you already know the core building blocks. What VCF adds is the orchestration layer that binds them together, driven by lifecycle automation. Instead of upgrading individual products by hand and crossing your fingers that the versions interoperate smoothly, you manage the complete environment through a centralized control plane. That structural shift is exactly why the platform exists.
The Underlying SDDC Model
VCF is a highly structured, opinionated realization of the Software-Defined Data Center (SDDC). Rather than purchasing discrete hardware for compute, dedicated storage arrays, and standalone physical firewalls, you run all of these operational functions in software on top of standard x86 server hardware.
Your compute resource is virtualized by the underlying hypervisor. Your storage is aggregated into a shared pool using local disks inside those same servers. Your network topologies and security policies are pushed into a software overlay running on top of basic physical switches. Because the entire topology lives in software, it can be provisioned via APIs, standardized into templates, and scaled out on demand.
Engineers have spent years manually building custom SDDCs by installing vSphere, bolting on vSAN, and manually configuring NSX. While that manual strategy works, it introduces massive operational overhead, making every major lifecycle upgrade an extensive research project. VCF solves this by handling the underlying integration and keeping the entire stack within a strictly tested, fully supported state.
Core Components
A modern VCF deployment relies on several primary products working together under the 9.x architecture.
| Component | Function |
|---|---|
| VCF Installer | A dedicated engine used to plan, validate, and execute the initial deployment. |
| vSphere | The core virtualization layer, where ESX hosts provide compute resources managed by vCenter. |
| vSAN | The software-defined storage layer that pools local server drives into a unified datastore. |
| NSX | The networking layer providing software-defined switching, routing, and distributed firewalls. |
| VCF Operations | The central platform console for health monitoring, log analytics, and global operations. |
| VCF Automation | The self-service delivery layer used to provision virtual machines and containerized workloads. |
VCF 9.x updates several familiar branding elements:
- Aria Rebranding: The Aria brand has been retired. The management tools previously known as Aria Operations and Aria Automation are now natively embedded as VCF Operations and VCF Automation.
- ESX Nomenclature: Broadcom has officially updated the hypervisor nomenclature to ESX for the 9.x generation, removing the trailing “i” from product documentation.
- VCF Management Services: Version 9.1 introduces a containerized Management Services layer. This architectural change consolidates lifecycle, identity management, and orchestration engines into a unified runtime, moving away from fragmented standalone appliances.
Platform Architecture in 9.x
The logical hierarchy of VCF 9.x uses distinct nesting boundaries:
- VCF Instance: The physical infrastructure framework encompassing your compute, storage, and networking layers. An instance is built out using logical domains.
- VCF Domains: Every domain includes its own vCenter, clustered ESX hosts with distributed configurations, and integrated NSX management.
- Management Domain: Automatically provisioned first to host infrastructure management components like the VCF operational tools.
- Workload Domain: Dedicated clusters deployed afterward to isolate actual business workloads from the primary management plane.
- VCF Fleet: A macro-management boundary containing multiple VCF instances or standalone vCenter environments orchestrated by a single deployment of VCF Operations and Automation.
- VCF Private Cloud: The highest container tier, capable of unifying multiple distributed fleets under a global organizational umbrella.
VCF 9.x reshapes how you interact with these layers. While SDDC Manager remains an essential backend appliance for triggering infrastructure workflows, deployment pathways, and online depot connections, day-to-day configuration and workload domain monitoring are heavily integrated into the VCF Operations interface.
When to Choose VCF
VCF is optimized for organizations requiring an enterprise-grade private cloud that operates identically across core data centers, edge environments, and public cloud targets. It is built for teams running a mixed environment of traditional VMs, containerized platforms, and modern AI/ML datasets. If your goal is to let application teams provision infrastructure via self-service catalogs without logging manual service tickets, the automated single-lifecycle architecture delivers immediate value.
Conversely, VCF represents a heavyweight architecture with demanding minimum resource thresholds and a comprehensive software licensing model. For smaller environments running static workloads on a handful of hosts, the full automated platform is usually unnecessary. For those footprints, Broadcom offers vSphere Foundation (VVF), providing virtualized compute, storage, and intelligent operations without the complete multi-tenant cloud automation framework.
I plan labs and upgrades around this distinction all the time. Reaching for the biggest platform by default is how budgets and complexity quietly balloon. Match the tool to your actual requirement.
The Bottom Line
VCF 9.x represents a major shift in how VMware environments are built and managed. By shifting day-to-day operations into a unified interface and automating full-stack lifecycle management, Broadcom is pushing hard toward true private cloud infrastructure. If you are planning an upgrade to 9.x, standardizing these new logical concepts (fleets, instances, and domains) is your essential first step.