Do You Need VMware Cloud Foundation? A Decision Framework

The Context: Why This Decision Matters More Than Ever

Prior to Broadcom's acquisition of VMware, the question "do you need VMware Cloud Foundation?" was largely academic. Most enterprises simply renewed their existing vSphere licences, added incremental add-ons as needed, and treated the infrastructure layer as a known, stable cost line. That world ended in 2024.

Broadcom eliminated all perpetual VMware licences and moved the entire portfolio to subscription in 2024, simultaneously consolidating the product catalogue into two primary offerings: VMware Cloud Foundation (VCF) and VMware vSphere Foundation (VVF). The channel-level messaging from Broadcom has strongly pushed customers toward VCF as the "strategic" platform — and some partners are presenting it as the only viable renewal path for enterprise customers.

This framing suits Broadcom's revenue goals but does not necessarily align with the actual capabilities requirements or budget realities of every enterprise. Understanding when VCF is genuinely the right choice — and when it represents expensive over-engineering — is the purpose of this framework.

The stakes are high. Support cost increases of 3–5× compared to pre-acquisition VMware renewal rates are now typical for enterprise accounts, with some organisations reporting even higher multiples. For a 500-server environment previously paying $2M per year in VMware support and licences, a 4× increase to $8M annually is not a rounding error — it is a budget event that demands board-level attention and rigorous evaluation of alternatives.

What VMware Cloud Foundation Actually Includes

Before applying the decision framework, it is important to understand precisely what VCF delivers — both what is included and what is notably absent from the base product.

Core capabilities included in VCF:

• VMware vSphere (the hypervisor itself, vCenter, ESXi)
• VMware vSAN (software-defined storage, replacing the need for separate SAN or NAS infrastructure)
• VMware NSX (software-defined networking, micro-segmentation, and security policy management)
• VMware Aria Suite Lifecycle (formerly vRealize Suite — automation, log management, operations monitoring)
• VMware Tanzu (Kubernetes lifecycle management for containerised workloads)
• Broadcom's SDDC Manager (fleet lifecycle management for infrastructure automation)

What is not included in base VCF:

• Hardware (VCF is software-only — you still need your own servers)
• Backup and disaster recovery solutions (third-party products like Veeam or Commvault are required)
• VMware Horizon (VDI and end-user computing) — separate subscription required
• Advanced security add-ons beyond NSX micro-segmentation

Understanding this completeness picture is important because VCF's value proposition depends heavily on how much of the included stack you will actually use. An organisation that deploys vSAN, NSX, and Tanzu across its estate realises significantly more value from VCF than one that uses vSphere but continues to rely on physical SAN infrastructure and does not require software-defined networking or Kubernetes orchestration.

VMware vSphere Foundation: The Alternative Within the VMware Estate

For organisations that need VMware's hypervisor but do not require the full-stack capabilities of VCF, VMware vSphere Foundation (VVF) is the lower-cost alternative within the Broadcom portfolio. VVF includes vSphere (vCenter, ESXi, DRS, HA), Tanzu Kubernetes, and basic Aria Operations monitoring — essentially the core virtualisation and basic management capabilities without vSAN, NSX, or advanced automation.

VVF carries a lower per-core subscription rate than VCF and is appropriate for environments where storage is provided by existing physical SAN infrastructure, networking does not require NSX micro-segmentation, and Kubernetes workloads are managed through other tooling. For many mid-market organisations and enterprises that are not actively pursuing full-stack SDDC modernisation, VVF delivers the core VMware capabilities they actually use at a meaningfully lower cost than VCF.

The important caveat is that organisations choosing VVF over VCF must be comfortable running separate point solutions for storage management, networking, and any advanced automation requirements. This is not necessarily a disadvantage — many enterprises already have best-of-breed tooling in these areas — but it does represent a departure from the integrated management story that Broadcom uses to justify VCF's premium.

The Decision Framework: Five Qualifying Questions

The following five questions provide a structured basis for the VCF vs. VVF vs. alternative platform decision. Answer each question honestly, using current operational reality rather than aspirational future-state planning.

Question 1: Are You Actively Using or Committed to Deploying vSAN?

vSAN is VMware's software-defined storage solution and one of the primary capability differentiators between VCF and VVF. If your organisation is running production workloads on vSAN or has a firm architectural commitment to deploying it across significant portions of your estate, vSAN is included in VCF and you benefit directly from the bundled pricing. If you are running a physical SAN (NetApp, Pure Storage, HPE Nimble, Dell EMC) and have no near-term plan to migrate to software-defined storage, vSAN's inclusion in VCF represents cost you are paying for capability you are not using.

VCF indicator: Yes, actively using vSAN on more than 30% of your environment, or have a board-approved migration plan in the next 12 months.

VVF or alternative indicator: No, running physical SAN with no near-term migration plan, or vSAN is used only in isolated pockets.

Question 2: Do You Require NSX Software-Defined Networking?

VMware NSX is an enterprise-grade software-defined networking and micro-segmentation platform that enables policy-based network security, automation of network provisioning, and east-west traffic inspection between VMs. NSX is powerful but also operationally complex — it requires dedicated NSX-trained networking engineers and a significant initial configuration investment. Organisations that have fully deployed NSX find it transformative for zero-trust network security; organisations that have licensed it but not fully deployed it are paying a substantial premium for unused capability.

VCF indicator: NSX is deployed across production environments with trained NSX administrators, providing active micro-segmentation value. Or you are explicitly committed to a zero-trust architecture that requires NSX capabilities.

VVF or alternative indicator: NSX is either not deployed or deployed only in proof-of-concept scope; network security is managed through physical firewalls and VLANs; no dedicated NSX expertise in the team.

Question 3: Are Kubernetes Workloads Central to Your Infrastructure Strategy?

VCF's Tanzu integration provides lifecycle management for Kubernetes clusters running on VMware infrastructure. If your organisation is running significant containerised production workloads, or has a platform engineering team building a private cloud Kubernetes platform, VCF's Tanzu capabilities have genuine value. If containers are used in development environments or for a limited number of production microservices that are well-served by a simpler Kubernetes distribution, the Tanzu integration in VCF may represent premium tooling for a modest use case.

VCF indicator: Running 20+ Kubernetes clusters in production; platform engineering team actively using Tanzu for cluster lifecycle management; private cloud Kubernetes is a strategic priority.

VVF or alternative indicator: Containers are used in dev/test; limited production Kubernetes requiring no platform-level lifecycle automation; Kubernetes managed separately from infrastructure.

Question 4: Is Infrastructure Lifecycle Automation a Priority?

VCF's SDDC Manager provides automated lifecycle management across the full infrastructure stack — patching, upgrades, configuration compliance, and capacity management. For large environments with frequent change cycles, this automation can deliver significant operational cost savings and reduced human error risk. For organisations that update infrastructure infrequently or manage changes manually, the automation premium of VCF delivers little incremental value over VVF's basic operations management.

VCF indicator: 200+ hosts across multiple clusters; frequent patching cycles (monthly or quarterly); dedicated infrastructure operations team; lifecycle automation is a defined OKR for the infrastructure function.

VVF or alternative indicator: Stable environment with infrequent changes; small infrastructure team where automation tooling adds complexity rather than reducing it; infrastructure change management handled through ITSM without automation.

Question 5: Does the VCF Per-Core Cost Fit Within Your Infrastructure Budget?

This is ultimately a financial viability question. VCF at $350 per core per year, with a 72-core minimum per CPU socket, creates billing floors that may not align with your workload density or budget constraints. For high-density deployments where most CPU cores are actively utilised, the per-unit economics are more favourable. For environments with many lightly loaded servers (common in enterprise IT), the minimum core billing can result in significant spend on unused capacity.

Run the numbers explicitly: multiply your total licensed CPU sockets by 72 (the minimum cores per socket) or your actual core count if higher, then multiply by $350 and by the number of years in your subscription term. Apply an achievable discount (20–30% for large accounts negotiated through a specialist reseller or advisory firm). Is the resulting figure within your infrastructure budget and justified by the capabilities delivered? If the answer is no, VCF is the wrong product for you at this time.

VCF indicator: High-density deployment (80%+ core utilisation); budget modelling confirms cost is justified by operational savings from the full stack; account team has confirmed achievable discount reduces total cost to within budget.

VVF or alternative indicator: Low core utilisation means minimum billing floor creates waste; cost modelling shows VVF or alternatives deliver similar operational value at significantly lower total cost.

The Alternatives in Depth: Nutanix and Azure VMware Solution

For organisations whose answers to the five framework questions point away from VCF — or who are evaluating whether to exit the VMware estate more broadly — Nutanix and Azure VMware Solution (AVS) are the two alternatives that consistently appear in enterprise shortlists.

Nutanix: The Hyperconverged Challenger

Nutanix has positioned itself explicitly as the VMware alternative for organisations seeking to avoid Broadcom's pricing escalation. Nutanix's Cloud Platform bundles its own hypervisor (AHV), distributed storage (NDFS), networking automation, and management (Prism Central) in a subscription model that is typically priced more competitively than VCF on a total-infrastructure-cost basis.

The key advantages of Nutanix over VCF for organisations considering the switch are: hyperconverged architecture that eliminates the need for separate vSAN configuration; AHV included at no incremental cost; a single-vendor support model that simplifies operations; and Nutanix's active investment in VMware migration tooling (the "Nutanix Move" utility automates VM migration from VMware environments). Nutanix Cloud Clusters (NC2) also extend the same platform to AWS and Azure, providing a genuine hybrid cloud story.

The trade-offs are real: organisations with deep VMware operational expertise face a learning curve on AHV and Prism; Nutanix's ecosystem of certified application integrations is smaller than VMware's; and some workloads with hard VMware hypervisor certification requirements cannot migrate without recertification effort. For greenfield deployments and organisations willing to invest in transition, Nutanix is a compelling alternative. For organisations with complex legacy VMware-certified configurations, the migration complexity must be honestly assessed.

Azure VMware Solution: Minimal-Disruption Cloud Migration

Azure VMware Solution (AVS) runs native VMware environments — including vSphere, vSAN, and NSX — on dedicated Azure bare-metal infrastructure. Critically, AVS is managed and supported jointly by Microsoft and Broadcom, meaning customers continue to run familiar VMware tooling without acquiring new hypervisor skills or migrating VMs to a different platform.

The primary use case for AVS is organisations that want to exit on-premises VMware infrastructure and move to a public cloud operational model, without the time and cost of re-architecting their application portfolio. AVS provides a lift-and-shift path: existing VMware VMs migrate to AVS using HCX (the VMware migration tool) with minimal changes, administrators continue using vCenter and NSX they already know, and the on-premises data centre footprint reduces over time as workloads migrate.

From a cost perspective, AVS is priced per dedicated node (bare-metal Azure hosts). While AVS is not inexpensive — dedicated node pricing runs approximately $8–10 per node-hour for AV36P nodes — the total cost of ownership comparison against on-premises VCF must include hardware refresh costs, data centre space and power, and IT operational overhead. For organisations with ageing on-premises hardware approaching refresh cycles, AVS often presents favourably in a full TCO comparison. Microsoft Azure customers with existing Commit to Consume agreements can also count AVS spend against their cloud commitment, unlocking additional discounts.

The Decision Matrix: Mapping Your Answers to an Outcome

Based on the five qualifying questions, the following decision matrix provides a directional recommendation:

VCF is the right choice if: You actively use vSAN across a large portion of your estate, NSX is deployed and operational with trained staff, Tanzu is central to your Kubernetes strategy, you have 200+ hosts with high utilisation, and the cost is within budget after achievable discounts. This profile typically applies to large, mature enterprise IT organisations with dedicated infrastructure platform teams and a genuine private cloud operating model.

VVF is the right choice if: You need the VMware hypervisor and vCenter management capabilities but do not actively use vSAN, NSX, or Tanzu at scale. You want to remain on Broadcom's support track but do not need the full-stack premium. This typically applies to mid-market organisations and enterprise teams managing VMware in a traditional (non-SDDC) operating model.

Nutanix is the right choice if: You are ready to invest in a platform transition, your workloads do not have hard VMware certification dependencies, and you want to break free from Broadcom's pricing trajectory permanently. Nutanix is particularly compelling for organisations deploying new infrastructure capacity rather than migrating existing environments.

Azure VMware Solution is the right choice if: You have a cloud-first mandate, are approaching an on-premises hardware refresh cycle, and want to migrate VMware workloads to cloud without re-architecting your application portfolio. AVS is also the right choice for organisations using it as a transitional step toward eventual cloud-native migration.

Negotiating VCF: What You Can Achieve

If your decision framework analysis concludes that VCF is the right product for your organisation, the negotiation phase is critical. Broadcom's list prices are a starting point, not a floor. The following considerations apply:

• Engage alternatives formally: Running a documented POC of Nutanix or AVS alongside the VCF evaluation gives your team credible alternatives data and signals to Broadcom that the renewal is not automatic. Account teams at Broadcom respond to competitive threat in ways they do not respond to budget pressure alone.
• Target 20–35% discount from list: Large enterprise accounts with multi-year commitments and referenceable status typically achieve 20–35% discounts from VCF list pricing. Anything below 20% should be challenged through a partner or independent advisory firm with current market benchmarks.
• Negotiate support tier and SLA separately: The default support package bundled with VCF subscriptions is not always the right fit. Enterprise production environments may require premium support with defined response times that are not in the standard agreement. Conversely, organisations with strong internal operational capability may be able to negotiate a lower support tier to reduce total cost.
• Multi-year vs. annual terms: Broadcom typically offers better per-year rates for 3-year commits. The risk is reduced flexibility if your cloud or infrastructure strategy changes during the term. Balance the discount value against your confidence in the 3-year workload forecast.

Conclusion: The Right Decision Is One You Can Justify

VMware Cloud Foundation is a technically capable and genuinely valuable product for the subset of organisations that use its full capabilities. It is not, as Broadcom's sales positioning implies, the only sensible choice for every enterprise infrastructure environment. Thousands of organisations are discovering that their actual VMware usage profile is better served by vSphere Foundation, Nutanix, Azure VMware Solution, or a combination of platforms — at a fraction of the VCF cost.

The framework presented here is a tool for making that evaluation systematic rather than reactive. Use it to produce a defensible, board-level recommendation — one that acknowledges the genuine value of VCF where it exists, but does not accept Broadcom's pricing on faith. In an environment where support cost increases of 3–5× are the norm, rigorous procurement decision-making is not optional. It is a strategic competency.