A structured assessment for determining whether VCF, VVF, vSphere Standard, or an alternative platform is the right choice for your environment. Based on what you actually use, not what Broadcom wants to sell you. Four technical dependency tests plus scope-split economics that typically reduce VMware spend by 25 to 60%.
Broadcom’s account teams are incentivised to sell VMware Cloud Foundation. VCF is the flagship product, it carries the highest per-core price, and Broadcom has structured its entire go-to-market around positioning VCF as the “strategic platform” for every enterprise. The sales narrative is compelling: VCF includes everything (vSphere, vSAN, NSX, Aria, SDDC Manager, HCX, Kubernetes) so you never have to worry about missing a feature or purchasing an add-on.
The problem with this narrative is that most VMware environments do not use most of VCF’s components. Industry data and our own advisory engagements consistently show that 60 to 70% of VMware customers were running vSphere with external storage (not vSAN) before the Broadcom acquisition. The majority had never deployed NSX. Most did not use Aria Suite beyond basic monitoring. And very few had implemented SDDC Manager for lifecycle automation.
These customers are now being quoted VCF at $350/core for a platform stack they have never used and may never need.
“This framework provides the structured assessment that Broadcom will not: an honest evaluation of which VMware product, or which non-VMware alternative, actually fits your environment, your technical requirements, and your budget.”
| Path | Product | List Price (per core/yr) | Best For | Version Access |
|---|---|---|---|---|
| 1 | VMware Cloud Foundation (VCF) | $350 | Full-stack private cloud with NSX, vSAN, lifecycle automation | vSphere 9.x |
| 2 | vSphere Foundation (VVF) | $135 | Enterprise virtualisation with basic vSAN and operations | vSphere 9.x |
| 3 | vSphere Standard | ~$50 | Basic virtualisation, small/edge environments | vSphere 8.x only |
| 4 | Alternative platform (Nutanix, Hyper-V, Proxmox) | Varies | Cost reduction, vendor diversification, VMware exit | N/A |
| 5 | Cloud migration (AVS, Azure-native, AWS) | Varies | Data centre exit, infrastructure outsourcing | N/A |
The remainder of this framework provides the decision criteria for choosing between these five paths. The assessment is structured as four technical dependency tests followed by an economic evaluation. If you pass all four dependency tests (meaning you genuinely require each VCF-specific capability), then VCF is the right product. If you fail one or more tests, a lower-cost path is likely more appropriate.
Our independent advisory team helps CIOs assess their VMware environment, classify clusters by actual capability requirements, build scope-split cost models, evaluate alternatives, and negotiate with Broadcom from a position of data-driven precision. Fixed-fee engagements with no vendor relationships.
Broadcom/VMware Advisory →NSX is the single most important differentiator between VCF and VVF. VCF includes NSX networking (overlay segments, distributed routing, Tier-0 and Tier-1 gateways). VVF does not include NSX at all. If your environment depends on NSX, VCF is effectively mandatory.
| Criterion | You Have an NSX Dependency | You Do NOT Have an NSX Dependency |
|---|---|---|
| Network virtualisation | Workloads communicate through NSX overlay segments rather than (or in addition to) traditional VLANs. Removing NSX means workloads lose connectivity. | Networking uses traditional VLANs and port groups managed through vSphere Distributed Switches or standard vSwitches. |
| East-west routing | Traffic between VMs in different subnets is routed by NSX distributed logical router at the hypervisor level. Removing NSX requires re-routing all inter-subnet traffic through physical equipment. | Inter-VM routing goes through physical routers or dedicated virtual firewall appliances (Palo Alto, Fortinet, Cisco). |
| Container networking | Tanzu Kubernetes Grid uses NSX-T for pod-to-pod networking, service load balancing, and network policy enforcement. Removing NSX requires replacing the CNI layer. | No Kubernetes networking dependency on NSX. Containers use Calico, Cilium, or another CNI, or no Kubernetes at all. |
| Firewalling | NSX Distributed Firewall for microsegmentation (note: DFW is a separate vDefend add-on at $120/core, not included in VCF base) | Firewalling handled by perimeter firewalls. No NSX-V or NSX-T deployed. |
If you have no NSX dependency, you have eliminated the primary technical justification for VCF. Even if you use NSX Distributed Firewall for microsegmentation, the DFW is not included in VCF base pricing. It is a separate vDefend add-on at $120/core. So NSX networking dependency drives the VCF requirement, but NSX security is a separate cost either way.
Both VCF and VVF include vSAN, but at different entitlement levels: VCF provides 1 TiB per core, VVF provides 0.25 TiB per core. The question is not whether you use vSAN, but how much vSAN capacity you need relative to your core count.
| Scenario | Storage Configuration | Recommended Path | Annual Impact (1,000 cores) |
|---|---|---|---|
| A: External SAN/NAS (no vSAN) | VMs on datastores backed by Pure Storage, NetApp, Dell PowerStore, HPE Nimble, etc. No vSAN clusters. | VVF at $135/core. vSAN entitlement is irrelevant. Same vSphere Enterprise Plus hypervisor without VCF premium. | Saves $215,000/year |
| B: vSAN within 0.25 TiB/core | vSAN clusters but total consumption below 0.25 TiB per licensed core. Compute-heavy environment with modest storage footprints. | VVF at $135/core. VVF’s 0.25 TiB/core entitlement is sufficient. | Saves $215,000/year |
| C: vSAN between 0.25 and 1.0 TiB/core | vSAN consumption exceeds VVF entitlement but within VCF’s 1 TiB/core. Moderate storage density. | Calculate both: VVF ($135/core) + vSAN add-on ($210/TiB) vs VCF ($350/core). Breakeven ~0.75 to 0.85 TiB/core. | Depends on actual consumption |
| D: vSAN exceeds 1.0 TiB/core | vSAN consumption exceeds even VCF’s entitlement. Add-on capacity required under either edition. | vSAN alone does not justify VCF. Re-evaluate storage architecture: external storage or hybrid approach may reduce overall TCO. | Evaluate storage strategy |
SDDC Manager is VCF’s automated lifecycle management tool. It orchestrates deployment, configuration, patching, and upgrades of the entire VCF stack (ESXi, vCenter, NSX, vSAN) across multiple workload domains. Powerful at scale, but an operational paradigm that requires commitment.
| You Need SDDC Manager If | You Do NOT Need SDDC Manager If |
|---|---|
| You operate 10+ hosts across multiple clusters or workload domains and patching/upgrading is a significant operational burden | You operate a small environment (3 to 10 hosts) where manual lifecycle management through vCenter is manageable |
| You require standardised, repeatable deployments across multiple environments (production, DR, development) | Your upgrade cadence is conservative (annual or less frequent) |
| You are building a private cloud with self-service provisioning for internal teams | You use third-party tools for configuration management and compliance (Ansible, Puppet, Terraform) |
| Compliance requirements mandate documented, automated change management for infrastructure updates | You have never deployed SDDC Manager and your current operational model works acceptably |
SDDC Manager is exclusive to VCF. If you genuinely need automated multi-domain lifecycle management and do not have equivalent third-party tooling, this is a VCF requirement. If your operational model works without it, this is not a justification for the VCF premium. Most sub-20-host environments manage lifecycle effectively without SDDC Manager.
VCF is the only VMware product that can be deployed on certified public cloud services: Azure VMware Solution (AVS), Elastic VMware Service (EVS) on AWS, Google Cloud VMware Engine (GCVE), and Oracle Cloud VMware Solution (OCVS). VVF and standalone vSphere are restricted to on-premises deployments.
| You Need VCF Portability If | You Do NOT Need VCF Portability If |
|---|---|
| You are actively using or planning to deploy VMware workloads on a hyperscaler (AVS, EVS, GCVE) | Your VMware workloads will remain on-premises for the foreseeable future |
| You require licence portability between on-premises and cloud environments using a single VCF subscription | Your cloud strategy uses Azure-native, AWS-native, or other non-VMware cloud services |
| Your hybrid cloud strategy depends on consistent VMware tooling with HCX for workload mobility | You are considering cloud migration as an exit from VMware, not as an extension of VMware |
If you do not need to run VMware on a hyperscaler, cloud portability is not a VCF justification. The vast majority of VMware customers run exclusively on-premises and do not need this capability.
Use our free Broadcom/VMware assessment tools to inventory your VMware estate, classify clusters by capability requirements, model scope-split economics, and benchmark your Broadcom pricing against comparable enterprises.
Start Free VMware Assessment →| NSX | vSAN (>0.25 TiB/core) | SDDC Manager | Cloud Portability | → Recommended Path | List Price |
|---|---|---|---|---|---|
| ✓ | ✓ | ✓ | Any | VCF | $350/core |
| ✓ | ✗ | ✗ | ✗ | VCF (NSX alone forces VCF) | $350/core |
| ✗ | ✓ | ✗ | ✗ | VVF + vSAN add-on (calculate breakeven) | $135/core + vSAN |
| ✗ | ✗ | ✓ | ✗ | VCF (SDDC Manager forces VCF) | $350/core |
| ✗ | ✗ | ✗ | ✓ | VCF (cloud portability forces VCF) | $350/core |
| ✗ | ✗ | ✗ | ✗ | VVF or vSphere Standard | $50 to $135/core |
| Any profile with cost reduction as primary driver | Evaluate alternative platform | Varies | |||
| Data centre exit required | Evaluate cloud migration | Varies | |||
If none of the four tests produces a “yes,” VCF is not justified. The last row of the matrix (no NSX, no vSAN above 0.25 TiB/core, no SDDC Manager, no cloud portability) describes the majority of VMware environments. These organisations should be on VVF ($135/core) or vSphere Standard ($50/core), saving $200 to $300/core/year compared to VCF.
Most enterprises do not have uniform environments. Production clusters running the full VMware stack coexist with development/test clusters, ROBO sites, and edge deployments that use only basic vSphere. The highest-impact cost optimisation is matching the VMware edition to each cluster’s actual requirements rather than licensing the entire estate at the highest tier.
| Cluster Type | Typical Configuration | Recommended Edition | Annual Cost (1,000 cores total) |
|---|---|---|---|
| Production (full stack) | vSAN + NSX networking + Aria + SDDC Manager | VCF ($250 negotiated) | $100,000 (400 cores) |
| Production (vSphere + SAN) | vSphere Enterprise Plus + external storage | VVF ($110 negotiated) | $33,000 (300 cores) |
| Development / Test | vSphere Standard features only | vSphere Standard ($45 negotiated) | $9,000 (200 cores) |
| ROBO / Edge | 2 to 3 host clusters, basic virtualisation | vSphere Standard ($45 negotiated) | $4,500 (100 cores) |
| Scope-split total | $146,500 | ||
| Uniform VCF (same 1,000 cores at $250) | $250,000 | ||
| Annual savings from scope-splitting | $103,500 (41%) |
In this worked example, scope-splitting reduces the annual VMware subscription cost by 41%. The savings come entirely from licensing each cluster at the appropriate edition rather than defaulting to VCF across the board.
This approach requires a precise inventory of which clusters use which VMware capabilities. But the payoff is substantial and repeatable at every renewal. Scope-splitting is technically supported (different clusters can run different editions) and contractually negotiable (a single Broadcom agreement can include VCF + VVF + vSphere Standard at different core counts and rates).
The decision framework so far has assumed VMware is the right platform. That assumption should be questioned when cost reduction is the primary objective, when Broadcom’s pricing trajectory creates unacceptable budget uncertainty, or when the organisation’s VMware investment is shallow (basic virtualisation without deep ecosystem integration).
| Alternative | Evaluate When | Key Considerations |
|---|---|---|
| Nutanix | vSphere-only environment (no deep NSX, no SDDC Manager) facing a VCF quote for unused capabilities. Budget requires 20 to 60% reduction over 5 years. Value operational simplicity. | Multi-hypervisor flexibility (AHV, ESXi, Hyper-V). Licence portability via NC2 (on-premises, AWS, Azure). See Nutanix vs VMware licensing comparison. |
| Microsoft Hyper-V / Azure Local | Microsoft-first shop with deep Azure and Windows Server investment. Primarily Windows-based workloads. Can leverage existing Windows Server Datacenter licences for unlimited Hyper-V virtualisation. | Small to mid-market (10 to 50 hosts). Eliminates VMware licensing entirely. vMotion, DRS, HA equivalents exist but with different capabilities. |
| Proxmox | SMB with strong internal Linux/open-source expertise. Small environment (3 to 15 hosts). Budget cannot absorb Broadcom per-core pricing. | Community-supported. Live migration, HA, storage replication exist but with different maturity levels. Investment in internal expertise rather than vendor support. |
Deep NSX networking dependency that has no direct equivalent on other platforms.
Large VMware-certified team (10+ engineers) with extensive automation built on vSphere APIs, PowerCLI, and the VMware ecosystem.
Regulatory or compliance requirements that specifically mandate VMware certification.
Applications certified only on VMware (SAP HANA on VMware, for example, with vendor-specific support requirements).
For full alternatives analysis, see VMware Alternatives 2026: Complete Comparison Guide.
Cloud migration answers a fundamentally different question: “should I own and operate virtualisation infrastructure at all?” This path is appropriate when the primary driver is data centre exit rather than VMware cost reduction.
| Cloud Path | How It Works | Best For |
|---|---|---|
| Azure VMware Solution (AVS) | Full VCF stack on dedicated bare-metal hosts in Azure. VMs migrate with minimal modification via HCX. Separate Broadcom VCF subscription required since October 2025 plus Azure infrastructure. | Immovable data centre exit deadlines with large VMware estates that cannot be re-platformed in time. See AVS licensing guide. |
| Azure-Native / AWS Migration | Migrate workloads to Azure VMs, AWS EC2, or cloud PaaS services. Eliminates VMware licensing entirely. Per-VM cloud cost typically 40 to 60% lower than equivalent AVS node pricing. | Organisations with technical capacity and timeline for proper migration engineering. Standard Windows/Linux workloads without VMware-specific dependencies. |
| Hybrid Approach | Migrate cloud-ready workloads to Azure-native or AWS. Keep VMware-dependent workloads on right-sized on-premises VVF or VCF. Use AVS as DR or burst capacity. | Reduces VMware footprint without requiring complete platform migration. Reduced core count improves negotiation leverage. |
Step 1: Inventory your VMware estate. Run VMware’s KB 95927 inventory script or use RVTools to capture: every ESXi host (with CPU model, socket count, core count), every cluster (with storage type: vSAN vs external SAN/NAS), every NSX deployment (overlay segments, distributed firewall rules, load balancers), and every management tool in use (SDDC Manager, Aria Operations, Aria Automation, HCX).
Step 2: Classify each cluster. For each cluster, determine which VCF-specific capabilities are in active use. Mark each cluster as VCF-required (uses NSX networking + vSAN + SDDC Manager), VVF-appropriate (uses vSphere Enterprise features + basic vSAN or external storage), vSphere Standard-appropriate (uses basic virtualisation only), or migration candidate (workloads that could move to cloud or alternative platform).
Step 3: Calculate licensable cores per cluster. Apply the 16-core-per-CPU minimum to each host. Sum the licensable cores for each cluster classification. Multiply by the respective per-core rate to produce the cost model. See VCF cost guide for detailed pricing benchmarks.
Step 4: Model the alternatives. For clusters classified as migration candidates, obtain competitive pricing from Nutanix, Microsoft, or cloud providers. For clusters remaining on VMware, model the scope-split cost (VCF + VVF + vSphere Standard) against a uniform VCF quote.
Step 5: Negotiate with data. Enter the Broadcom negotiation with your classified inventory, your scope-split model, and your competitive alternatives. This data eliminates the information asymmetry that Broadcom relies on to push VCF uniformly. A well-prepared customer with a defensible scope-split proposal and credible alternative pricing achieves 25 to 50% better outcomes than a customer who accepts the default VCF proposal.
| Mistake | What Happens | Better Approach |
|---|---|---|
| 1. Buying VCF “for the future” | VCF costs $215/core/year more than VVF. For 1,000 cores, that is $215,000/year in premium for capabilities you are not using. | Pay for what you use today. Migrate from VVF to VCF at renewal when the need materialises. |
| 2. Assuming NSX is required because it is “best practice” | NSX is complex to deploy, requires specialised skills, and adds operational overhead. Many enterprises operate successfully with VLAN-based networking. | If security and networking requirements are met by current architecture, NSX is an enhancement, not a requirement. Evaluate on ROI. |
| 3. Licensing entire estate at VCF because some clusters need it | If 30% of clusters need VCF and 70% need only VVF or vSphere Standard, licensing everything at VCF wastes 70% of the premium. | Scope-split: different clusters run different editions. Contractually standard, technically supported, significant savings. |
| 4. Ignoring vSAN storage economics | Comparing headline per-core rates without factoring vSAN entitlements. VCF includes 1 TiB/core; VVF includes 0.25 TiB/core. | Model total cost (edition + add-ons) rather than comparing headline rates. The vSAN breakeven is approximately 0.75 to 0.85 TiB/core. |
| 5. Treating the Broadcom proposal as final | Customers who accept the first proposal pay 20 to 40% more than those who negotiate with benchmark data and alternatives. | A 2 to 4 week assessment typically yields 6 to 7 figures of annual savings. See case study: $3.5M reduced to $1.8M. |
“The time and effort invested in a proper VMware assessment, typically 2 to 4 weeks, yields 6 to 7 figures of annual savings on mid-to-large environments. A well-prepared customer with a defensible scope-split proposal and credible alternative pricing achieves 25 to 50% better outcomes than a customer who accepts the default VCF proposal.”
No. If your environment runs vSphere with external SAN/NAS storage, does not use NSX networking, does not use SDDC Manager, and does not require cloud portability, VVF at $135/core or vSphere Standard at $50/core provides the capabilities you need at 61 to 86% lower cost than VCF. This is the most common scenario we encounter in advisory engagements. The savings are $215 to $300 per core per year at list price.
Yes. Different clusters can run different VMware editions. A production cluster using the full VCF stack can coexist with a development cluster running VVF and a ROBO cluster running vSphere Standard. Each cluster is licensed independently based on its core count and edition. A single Broadcom agreement can cover all editions with separate line items and rates.
VCF is not the only path to vSphere 9. VVF also provides access to vSphere 9 features. The accurate statement is: vSphere 9 is only available through VCF or VVF subscriptions, not through standalone vSphere Standard or Enterprise Plus. If a Broadcom representative tells you VCF is the only option for vSphere 9, they are either misinformed or upselling. VVF at $135/core includes full vSphere 9 capabilities.
Compare: (VVF rate × cores) + (vSAN add-on rate × excess TiB) vs (VCF rate × cores). The vSAN breakeven is approximately 0.75 to 0.85 TiB per core at typical negotiated pricing. If your vSAN consumption is below this threshold, VVF + add-on is cheaper. If above, VCF may be more cost-effective for the vSAN component, but only if you also need NSX or SDDC Manager.
Before. Competitive evaluation provides the strongest negotiation leverage with Broadcom. A customer who has completed a Nutanix proof of concept or obtained Azure-native migration pricing negotiates from a position of genuine optionality. Even if you ultimately decide to stay on VMware, having a credible alternative on the table produces 10 to 20% better pricing.
Yes. Our Broadcom/VMware advisory service includes the full assessment process: inventory validation, cluster classification, scope-split modelling, competitive alternative pricing, and end-to-end negotiation support. We work on a fixed-fee basis with no commercial relationship with Broadcom, VMware, Microsoft, Nutanix, or any vendor.
Most enterprises can reduce their VMware subscription cost by 25 to 60% through proper edition selection and scope-splitting alone, before negotiation even begins. Redress Compliance provides the independent assessment, benchmark pricing, and negotiation support to ensure you pay for what you need and nothing more.