From 160+ Products to Four Bundles: A New VMware Landscape
Broadcom's acquisition of VMware in late 2023 resulted in a radical simplification of VMware's product offerings. Over 160 individual VMware products and bundles have been consolidated into four main subscriptions: VMware Cloud Foundation (VCF), vSphere Foundation (VVF), vSphere Standard, and vSphere Enterprise Plus.
This streamlined lineup folds formerly standalone products โ including vSAN (software-defined storage), NSX (network virtualisation and security), and the Aria management suite (formerly vRealize) โ into broader bundles. While the new bundles aim to reduce complexity and deliver a one-stop private cloud stack, they also limit flexibility, forcing some customers to purchase features they may not need and potentially increasing costs โ especially for smaller deployments that previously relied on entry-level offerings like vSphere Essentials Plus.
The consolidation represents a fundamental shift in how enterprises procure VMware technology. The era of ร la carte purchasing โ selecting individual products and editions to match specific requirements โ is over. In its place, Broadcom has imposed a pre-defined bundle model where customers choose one of four packages that determine which capabilities are available. Understanding exactly what each bundle includes, what has been discontinued, and how this affects your organisation's VMware costs and strategy is essential for IT, procurement, and finance leaders navigating this transition.
Bundle-Only Model
Individual VMware product purchases are no longer possible. All capabilities are delivered through one of four subscription bundles โ no mix-and-match, no standalone SKUs.
Subscription-Only
Perpetual licences have been eliminated. All VMware software is now subscription-based with annual or multi-year terms. Existing perpetual licences receive no new updates.
Per-Core Pricing
Licensing has shifted from per-socket to per-core with a minimum of 16 cores per CPU โ significantly increasing costs for modern servers with high core counts.
Products Discontinued
vSphere Essentials Plus retired. Horizon divested to Omnissa. Aria suite available only within bundles. Standalone vSAN and NSX purchases eliminated.
Inside the Bundles: What Each Package Includes
Each of the four bundles packages specific VMware components at different capability levels. Former standalone products โ vCenter, vSAN, NSX, and vRealize/Aria โ are now delivered as part of these bundles or not at all. The following comparison breaks down exactly what is included in each bundle and what is missing.
| Capability | VMware Cloud Foundation (VCF) | vSphere Foundation (VVF) | vSphere Enterprise Plus | vSphere Standard |
|---|---|---|---|---|
| Hypervisor | vSphere Ent Plus โ | vSphere Ent Plus โ | vSphere Ent Plus โ | vSphere Standard (basic) |
| vCenter Server | Standard โ | Standard โ | Standard โ | Standard โ |
| vSAN Storage | Enterprise (~1 TiB/core) โ | Enterprise (~250 GiB/core) โ | Not included โ | Not included โ |
| NSX Networking | Full NSX Data Center โ | Not included โ | Not included โ | Not included โ |
| Aria Management | Full Aria Suite Enterprise โ | Aria Ops Standard only | Not included โ | Not included โ |
| Kubernetes (Tanzu) | Tanzu Kubernetes Grid โ | Tanzu Kubernetes Grid โ | Not included โ | Not included โ |
| HCX Cloud Migration | Included โ | Not included โ | Not included โ | Not included โ |
| SDDC Manager | Included โ | Not included โ | Not included โ | Not included โ |
| DRS / HA / FT | Full advanced features โ | Full advanced features โ | Full advanced features โ | HA only (no DRS/FT) |
| Support Level | Select (premium) โ | Standard | Standard | Standard |
| Best Suited For | Complete SDDC / private cloud for large enterprises | Mid-sized environments needing compute + storage + monitoring | Enterprises needing robust virtualisation only | Basic virtualisation for small / branch deployments |
The table reveals a clear hierarchy. VMware Cloud Foundation is the all-inclusive private cloud platform โ the only bundle that includes NSX, the full Aria suite, HCX migration tools, and SDDC Manager. It is also the most expensive, priced for large enterprises building complete software-defined data centres. vSphere Foundation sits in the middle โ including vSAN and basic Aria monitoring but lacking NSX and the full management suite. vSphere Enterprise Plus and vSphere Standard are stripped-down virtualisation-only offerings that include no software-defined storage, networking, or management tools.
Mapping Your Current VMware Products to the New Bundles
If You Use: vSphere + vSAN + vRealize
Your closest match is vSphere Foundation (VVF) โ it bundles all three capabilities (though Aria Ops replaces vRealize, and vSAN storage per core is capped at ~250 GiB with add-ons available).
If You Use: vSphere + NSX + Full Aria
You need VMware Cloud Foundation (VCF) โ the only bundle that includes NSX networking and the complete Aria suite. There is no way to add NSX to VVF except through the separate "VMware Firewall" add-on.
If You Use: vSphere Only
Choose between vSphere Enterprise Plus (for DRS, FT, distributed switch) or vSphere Standard (for basic virtualisation). Neither includes storage, networking, or management tools.
Former Standalone Products: What Happened to vSAN, NSX, and Aria
A major consequence of Broadcom's bundling strategy is that many standalone VMware products are no longer sold separately. Key data centre components that were previously available as individual purchases have been absorbed into the bundle hierarchy โ or eliminated entirely.
vSAN โ Absorbed into VCF and VVF
VMware vSAN, the software-defined storage platform, can no longer be purchased independently. It is included in VMware Cloud Foundation (with ~1 TiB per core) and vSphere Foundation (with ~250 GiB per core). Customers who previously purchased vSAN licences separately must now adopt one of these bundles to continue using vSAN with current updates and support. Additional vSAN capacity beyond the bundled allocation requires purchasing add-on subscriptions at additional cost.
NSX โ Available Only in VCF (or as Firewall Add-On)
VMware NSX, the network virtualisation and micro-segmentation platform, is included only in VMware Cloud Foundation. It is not available in vSphere Foundation, vSphere Enterprise Plus, or vSphere Standard. Customers who need NSX capabilities without the full VCF stack can purchase the "VMware Firewall with Advanced Threat Protection" add-on โ Broadcom's repackaged approach to selling NSX functionality โ but this comes at additional cost and does not include all NSX features available in VCF.
Aria Suite โ Folded into Bundles, No Standalone Sales
The VMware Aria suite (formerly vRealize) โ covering operations monitoring, automation, log analytics, and cloud management โ is no longer sold as a standalone product. The full Aria Suite Enterprise is included only in VMware Cloud Foundation. A limited subset (Aria Operations Standard for monitoring) is included in vSphere Foundation. Customers who previously licensed vRealize/Aria components independently will find that their existing deployments enter maintenance mode โ no new features, security patches only โ when current support terms expire. Any expansion or renewal requires moving to one of the new bundles.
๐ซ Discontinued and Divested VMware Products
- vSphere Essentials Plus Kit: Retired entirely. The popular entry-level bundle for small environments (up to 3 hosts) is no longer available. Small customers are directed to vSphere Standard or Enterprise Plus at significantly higher price points.
- VMware Horizon (VDI): Divested to Omnissa (a separate company backed by private equity). VMware Horizon, Workspace ONE, and the entire End-User Computing division are no longer part of VMware. Existing Horizon customers will deal with a new vendor for renewals and support.
- Standalone Aria / vRealize licences: End-of-availability. Existing licences enter maintenance mode; new purchases require bundle adoption.
- Individual vSAN and NSX licences: No longer sold separately. Available only within bundles or as add-ons.
- Per-socket licensing: Eliminated. All products now use per-core pricing with a 16-core minimum per CPU.
What the Bundle Model Means for Existing Customers
For organisations currently running VMware, the transition to Broadcom's bundle model creates several distinct scenarios depending on the existing VMware footprint. Understanding which scenario applies to your organisation is essential for planning the transition and quantifying the financial impact.
Scenario 1: vSphere-Only Customers
Organisations that use VMware purely for virtualisation โ vSphere hypervisor and vCenter for VM management, without vSAN, NSX, or Aria โ have the most straightforward transition. They choose between vSphere Standard (if they only need basic virtualisation) or vSphere Enterprise Plus (if they require DRS, FT, distributed virtual switch, and other advanced features). The cost impact depends primarily on the shift from per-socket to per-core pricing and the move from perpetual licensing to subscription. For environments with modern high-core-count processors, the per-core pricing alone can represent a 2โ4ร cost increase compared to the old per-socket model.
Scenario 2: vSphere + vSAN Customers
Organisations that use both vSphere and vSAN must adopt vSphere Foundation (VVF) at minimum โ the only bundle below Cloud Foundation that includes vSAN. This means they also receive Aria Operations Standard and Tanzu Kubernetes Grid, whether they need them or not. The bundled vSAN allocation (~250 GiB per core) may be insufficient for storage-intensive workloads, requiring additional vSAN capacity add-ons at extra cost. The total cost impact combines the per-core pricing increase, the subscription model shift, and any additional vSAN capacity purchases โ often resulting in a significant overall increase compared to the previous individual licence model.
Scenario 3: Full Stack Customers (vSphere + vSAN + NSX + Aria)
Organisations that previously used VMware's complete software-defined data centre stack โ vSphere, vSAN, NSX, and the full vRealize/Aria suite โ are directed to VMware Cloud Foundation (VCF). For these customers, the bundling may actually represent reasonable value, since VCF includes all the capabilities they were previously licensing separately. The per-core pricing change still applies, but the consolidation of multiple separate licences into a single bundle can offset some of the per-unit increase. These customers should focus negotiation efforts on volume discounts, multi-year terms, and trade-in credits for their existing perpetual licences.
Scenario 4: Hybrid or Partial Adopters
The most challenging scenario is organisations that use some but not all of a bundle's capabilities โ for example, vSphere + NSX but not vSAN, or vSphere + vSAN + Aria but not NSX. These organisations are forced into a bundle that includes capabilities they don't need, with no ability to opt out of those components or receive a corresponding price reduction. The only recourse is negotiation: demonstrating to Broadcom that the bundled capabilities don't align with the organisation's requirements and requesting pricing that reflects actual usage rather than theoretical feature access.
Impact on Small Customers: The End of Essentials Plus
Broadcom's portfolio consolidation has a disproportionate impact on small and mid-sized customers. The retirement of vSphere Essentials Plus Kit โ VMware's most popular entry-level offering โ eliminates the cost-effective path that small organisations used to access enterprise virtualisation.
Under VMware's pre-acquisition model, a small manufacturer running three ESXi hosts could purchase vSphere Essentials Plus for a modest annual fee, gaining access to vSphere, vCenter Essentials, and basic high-availability features. This kit was designed specifically for small environments and priced accordingly. Under Broadcom's new model, the closest equivalent is vSphere Enterprise Plus subscription โ which includes far more features than most small organisations need (DRS, FT, distributed virtual switch) and comes with a significantly higher price tag. Additionally, the per-core licensing model with a 16-core minimum per CPU means that even small servers with modest core counts pay for at least 16 cores of licensing.
The result: small customers who previously spent a few thousand dollars annually on VMware now face subscription costs that may be 2โ5ร higher โ for capabilities they will never use. This cost increase has driven many small organisations to evaluate alternatives including Proxmox VE, Microsoft Hyper-V, KVM-based platforms, and Nutanix AHV โ platforms that offer basic virtualisation without the bundle overhead. For organisations committed to VMware, the key is to engage Broadcom early to explore any transition programmes, trade-in credits, or volume discounts that may partially offset the increase.
The Cost of Bundling: Flexibility vs. Feature Overload
Broadcom's forced bundling approach creates a fundamental trade-off between delivered value and actual need. Every customer gets a richer feature set than they may have previously purchased โ but many will pay for capabilities they have no intention of deploying.
Consider a mid-sized SaaS company that previously used vSphere Standard and vSAN to run its backend infrastructure. Under the old model, they paid for exactly what they needed. Under Broadcom's new lineup, obtaining vSAN requires adopting vSphere Foundation โ which also includes Aria Operations (they use Datadog), Tanzu Kubernetes (they run containers in AWS), and vSphere Enterprise Plus features (they don't use DRS or FT). The immediate result is a higher subscription cost for a bundle where three of four additional capabilities provide no value.
For larger enterprises, the equation may be more favourable. An organisation building a greenfield private cloud that needs compute, storage, networking, management, and Kubernetes may find VMware Cloud Foundation to be a well-integrated, competitively priced stack compared to purchasing each component separately (which is no longer possible anyway). The challenge is that most organisations don't fall neatly into VCF's "complete SDDC" use case โ they have hybrid environments where only some of the bundled capabilities are relevant.
Quantifying the Bundling Tax
The financial impact of forced bundling varies dramatically by customer profile, but the pattern is consistent: organisations pay more for capabilities they don't use. To quantify this, organisations should calculate what Redress calls the "bundling tax" โ the percentage of your subscription cost attributable to capabilities you have no plans to deploy. For a vSphere + vSAN customer forced into VVF, the bundling tax includes Aria Operations, Tanzu, and advanced vSphere features beyond what they previously licensed. For a vSphere-only customer forced into Enterprise Plus, the tax includes DRS, FT, and distributed switch capabilities they may never configure. Across Redress's Broadcom advisory engagements, bundling taxes typically range from 15โ40% of the total subscription cost โ significant overhead that can be partially mitigated through negotiation but never fully eliminated under the current bundle structure.
The per-core pricing model compounds this effect. Under VMware's legacy per-socket model, a two-socket server required exactly two licences regardless of core count. Under Broadcom's per-core model with a 16-core minimum, the same server with two 64-core AMD EPYC processors requires 128 core licences โ a 64ร increase in licence units. While the per-core price is lower than the per-socket price, the total cost for high-core-count environments is substantially higher. Organisations running modern AMD EPYC or Intel Xeon Scalable processors with 32+ cores per socket are most severely affected. Those running older hardware with lower core counts may see modest increases โ but face the paradox of needing to upgrade hardware for performance while knowing that each hardware upgrade also increases VMware licensing costs.
Evaluating Alternatives: When It Makes Strategic Sense
Broadcom's pricing changes have made platform alternatives evaluation a mainstream activity rather than a fringe exercise. Organisations that would never have considered leaving VMware are now running serious evaluations of Proxmox VE, Microsoft Hyper-V, Nutanix AHV, and KVM-based platforms โ not because these alternatives are superior to VMware, but because the cost differential has become large enough to justify the migration effort and operational risk.
The practical approach is workload segmentation. Rather than attempting a wholesale VMware replacement (which carries significant risk for mission-critical workloads), organisations identify workload tiers: Tier 1 (mission-critical, VMware-dependent features like DRS, HA, FT โ remain on VMware), Tier 2 (important but not VMware-dependent โ candidates for Hyper-V or Nutanix), and Tier 3 (development, test, non-production โ candidates for Proxmox or KVM). By migrating Tier 2 and Tier 3 workloads off VMware, organisations reduce their VMware core count and subscription costs while maintaining VMware for the workloads that genuinely require its capabilities. A 20โ30% reduction in VMware core count through selective migration can offset a significant portion of the Broadcom price increase.
โ ๏ธ Key Cost Implications of Broadcom's Bundling Strategy
- Forced feature overpayment: Organisations that previously bought only vSphere + vSAN now pay for Aria, Tanzu, and advanced features they don't use
- Per-core pricing impact: Modern servers with 32, 64, or 128 cores per socket pay significantly more than under the old per-socket model
- Subscription compounding: 3โ5 year subscription costs may substantially exceed previous perpetual licence + support costs
- Minimum commitment floors: 16-core minimum per CPU creates a pricing floor even for underutilised hosts
- Add-on cost stacking: Capabilities excluded from your bundle (NSX for VVF customers, vSAN for vSphere EP customers) require additional paid add-ons
Recommendations for IT, Procurement, and Finance Leaders
Map Your Current VMware Estate to the New Bundles
Inventory every VMware product your organisation is currently using โ hypervisor, storage, networking, cloud management, VDI, monitoring โ and map each to Broadcom's four bundles. This will clarify which bundle you need (and what you're forced to pay for that you won't use). If you use vSphere + vSAN, you need VVF at minimum. If you also use NSX, you're looking at VCF. If you only use the hypervisor, vSphere EP or Standard may suffice. This mapping is the foundation for every subsequent decision.
Model Total Cost of Ownership Under the New Pricing
Run detailed 3โ5 year cost projections under the new per-core subscription model. Count actual cores across your entire vSphere estate (remembering the 16-core minimum per CPU). Compare the projected subscription cost to your previous annual support + maintenance spend. Be prepared for significant increases in many cases โ particularly for environments with high core counts, modern processors, or previously entry-level VMware deployments. This financial analysis builds the internal case for budget approval, negotiation leverage, or platform alternatives evaluation.
Leverage Bundled Capabilities You're Already Paying For
If your required bundle includes capabilities you weren't previously using โ Aria Operations, Tanzu Kubernetes, advanced vSphere features โ consider deploying them. Got Aria Operations in VVF? Deploy it and retire your third-party monitoring tool. Gained Tanzu? Evaluate whether on-premises Kubernetes reduces your cloud container spend. Acquired NSX via VCF? Use micro-segmentation to improve security and potentially retire separate firewall investments. Extracting value from every bundled component improves ROI and helps justify the cost increase internally.
Negotiate Aggressively and Explore Transition Programmes
Broadcom's published pricing is a starting point, not a ceiling. Large enterprises should negotiate volume discounts, multi-year term incentives, and trade-in credits for existing perpetual licences. Ask about transition programmes specifically designed for customers moving from legacy VMware licensing. Engage a Broadcom contract negotiation specialist if the stakes are significant โ the difference between list pricing and a well-negotiated agreement can be 20โ40% or more.
Evaluate Alternatives for Non-Strategic Workloads
Not every workload needs to run on VMware. Evaluate whether VMware alternatives โ Proxmox VE, Microsoft Hyper-V, KVM, Nutanix AHV โ are viable for development/test environments, branch offices, or non-critical workloads. Reducing your VMware core count by migrating non-strategic workloads directly reduces subscription costs. Cloud migration may also make sense for some workloads. The goal is to right-size your VMware footprint to include only the workloads that genuinely require VMware's capabilities.
Negotiation Leverage in the New Broadcom Reality
Despite the reduced flexibility in product selection, subscription pricing remains highly negotiable โ particularly for large enterprises with significant VMware footprints. Broadcom's published list prices are starting points, and organisations that negotiate effectively consistently achieve better outcomes than those who accept initial quotes.
The strongest negotiation levers include: competitive alternatives credibility โ demonstrating that you have actively evaluated Proxmox, Hyper-V, or Nutanix and have a realistic migration plan creates genuine competitive pressure that Broadcom's sales teams take seriously; multi-year commitment potential โ offering a 3-year or 5-year commitment in exchange for significant per-core discounts locks in pricing predictability while giving Broadcom revenue visibility; total account value โ organisations that also purchase other Broadcom products (CA Technologies, Symantec, semiconductor tools) can negotiate across the entire Broadcom relationship rather than on VMware alone; and renewal timing โ Broadcom's sales organisation operates on quarterly targets, and renewals or new commitments near quarter-end carry stronger negotiation dynamics than mid-quarter discussions.
Organisations should also be aware that Broadcom has, in some cases, offered custom pricing arrangements for customers whose workload profiles don't align well with the standard bundles โ particularly when the alternative is the customer migrating significant workloads to competing platforms. These custom arrangements are not advertised and require direct negotiation, typically supported by detailed usage data demonstrating the misalignment between the bundle's capabilities and the organisation's actual requirements.
โ Checklist: 5 Actions to Take Now
- Audit your current VMware deployment: Count products, hosts, cores, and feature usage โ know exactly what you're running
- Run the bundle comparison: Determine which bundle covers your requirements and what you're forced to pay for additionally
- Model 3โ5 year subscription costs: Compare to historical perpetual + support costs to quantify the budget impact
- Identify negotiation leverage: Multi-year commitment potential, competitive alternatives, renewal timing, and strategic significance to Broadcom
- Engage independent advisory: A vendor-neutral Broadcom licensing specialist can identify cost optimisation opportunities and negotiate from a position of expertise
"Broadcom's bundling strategy is designed to drive higher average revenue per customer โ and it works. The customers who fare best in this transition are those who understand exactly what they're paying for, extract maximum value from bundled capabilities, negotiate aggressively on pricing, and right-size their VMware footprint by migrating non-strategic workloads to alternatives. The customers who fare worst are those who accept list pricing without negotiation, don't audit their actual usage, and continue paying for VMware across their entire estate without evaluating alternatives."
โ Fredrik Filipsson, Co-Founder, Redress Compliance