Author : Kinshuk Tripathi, Priyanka Matadh
When teams evaluate VMware Cloud Foundation (VCF) 9.0, the discussion often starts with features and ends with licensing. What’s frequently missed in between is the Bill of Materials (BoM)—not just what components are included, but why they are tightly integrated and how they shape the private cloud operating model.
VCF 9.0 is not a loose bundle of VMware products. It is a curated, lifecycle-aligned platform stack, designed to behave like a cloud—on-premises.
This blog walks through the core BoM of VCF 9.0 and explains the role each component plays in building a modern private cloud.
vSphere: The Compute Foundation (Still Critical, No Longer Central)
vSphere remains the compute backbone of VCF 9.0. ESXi and vCenter provide:
- Virtual machine execution
- Resource scheduling
- Core availability and resilience
What has changed is its role.
In traditional environments, vSphere was the platform. In VCF 9.0, vSphere becomes a foundational service consumed by the cloud platform. You don’t design around vSphere clusters anymore—you design around domains and services.
This shift matters because it:
- Reduces over-customization
- Enables predictable lifecycle
- Aligns compute with platform-level operations
vSphere is still essential—but it no longer operates alone.
NSX: Networking and Security as Platform Capabilities
NSX is not optional in VCF 9.0. It is a core architectural pillar.
NSX provides:
- Software-defined networking
- Load balancing
- Distributed firewalling
- Microsegmentation
- Policy-based security
The real value of NSX in VCF 9.0 is not individual features—it’s how networking and security become native cloud services.
Instead of:
- Ticket-based VLAN provisioning
- Perimeter-only security models
VCF 9.0 enables:
- Declarative networking
- Workload-level security
- Zero Trust-aligned designs
NSX ensures that every workload domain is cloud-ready by default.
VMware Aria: The Cloud Control Plane
If vSphere and NSX provide infrastructure, VMware Aria provides intent.
VCF 9.0 integrates Aria to deliver:
- Self-service provisioning
- Policy-based governance
- Monitoring and observability
- Capacity and performance analytics
Aria transforms infrastructure from something you build into something you consume.
Key architectural implications:
- Automation is assumed, not optional
- Operations become proactive instead of reactive
- Capacity planning becomes predictive
Without Aria, VCF would still be a platform.
With Aria, VCF becomes a cloud operating model.
SDDC Manager: The Glue That Makes VCF a Platform
SDDC Manager is often underestimated—but it is arguably the most critical component in the VCF BoM.
SDDC Manager is responsible for:
- Deployment orchestration
- Lifecycle management
- Version and dependency alignment
- Domain management
This is what allows VCF 9.0 to offer:
- End-to-end upgrades
- Reduced lifecycle risk
- Consistent environments at scale
In many private clouds, lifecycle is a people problem.
In VCF 9.0, lifecycle becomes a platform capability.
If SDDC Manager is removed, VCF collapses back into a collection of tools.
vSAN (or External Storage): Integrated by Design
VCF 9.0 supports both:
- vSAN as the default integrated storage
- Approved external storage solutions
vSAN fits naturally into the VCF model because:
- It follows the same lifecycle orchestration
- It scales with workload domains
- It reduces external dependencies
Regardless of storage choice, the key point is this:
storage lifecycle is aligned with the platform, not managed separately.
That alignment is what enables predictable operations.
Why the BoM Matters More Than Individual Products
Looking at the VCF 9.0 BoM as a checklist misses the point.
The value comes from:
- Validated interoperability
- Synchronized lifecycle
- Prescriptive architecture
- Platform-level operations
VCF 9.0 is opinionated by design. It trades flexibility for:
- Stability
- Scalability
- Operational sanity
For many enterprises, that trade-off is exactly what modern private cloud requires.
Final Thoughts
VCF 9.0’s Bill of Materials is not about assembling the “best” tools—it’s about eliminating architectural ambiguity.
Each component:
- Has a clearly defined role
- Operates within platform constraints
- Supports continuous lifecycle and automation
If you approach VCF 9.0 as a set of products, it will feel restrictive.
If you approach it as a cloud platform, the BoM starts to make perfect sense.
