VMware vSphere Foundation (VVF) Licensing Guide 2026: Pricing, Components, Rules and Strategy

What Is VMware vSphere Foundation?

VMware vSphere Foundation — abbreviated VVF — was introduced as part of Broadcom's portfolio restructuring following its acquisition of VMware. It replaced a landscape of named products including vSphere Enterprise Plus, vRealize Suite, and vSAN Enterprise, consolidating them into a single subscription with a defined set of bundled components. VVF sits below VMware Cloud Foundation (VCF) in the portfolio and above vSphere Standard, and it is designed for organisations that require a capable enterprise hypervisor platform without the full software-defined data centre stack that VCF provides.

The decision to introduce VVF as a distinct tier was driven by commercial necessity: many enterprises were not prepared to absorb the full VCF price point — approximately $350 per core per year at list price — especially those with existing third-party storage and networking infrastructure. VVF provides a commercially defensible migration path from perpetual vSphere licensing at a price point that, when negotiated, can represent a reasonable progression from legacy spend levels, even accounting for the support cost increases of 3 to 5 times that Broadcom's subscription model has imposed compared to the previous VMware support structure.

VVF Components: What You Get

Understanding VVF requires mapping each included component against its predecessor product and understanding the licensing mechanics that apply to each.

vSphere Hypervisor (ESXi) and vCenter

VVF includes the full vSphere 8 hypervisor with all enterprise features enabled: vMotion for live VM migration without workload interruption, vSphere High Availability (HA) for automated VM restart on host failure, Enhanced vMotion Compatibility (EVC) for cross-generation cluster migration, and Fault Tolerance (FT) for zero-downtime protection of critical VMs through continuous shadow execution on a secondary host.

Distributed Resource Scheduler (DRS) is included in VVF. DRS automates VM placement decisions across cluster hosts based on resource utilisation metrics, configured policies, and maintenance mode requirements. It continuously rebalances workloads to prevent hot spots and maintain performance SLAs. DRS is absent from vSphere Standard and represents a meaningful operational capability difference between the two tiers for clusters larger than four hosts.

vCenter is included in the VVF subscription with the Standard vCenter licence. vCenter provides centralised management of ESXi hosts, VM lifecycle management, cluster configuration, and the management interface for all other VVF components. There is no separate vCenter licensing cost within VVF — it is bundled.

vSphere Distributed Switch

VVF includes the vSphere Distributed Switch (vDS), replacing the per-host standard switch with a centralised network configuration object managed through vCenter. vDS enables consistent network policy enforcement across all hosts in a cluster from a single configuration point, QoS traffic marking, port mirroring for network analysis, and network I/O control for workload traffic prioritisation. vDS is not included in vSphere Standard, which is limited to the per-host Standard Switch.

Neither VVF nor vSphere Standard includes NSX. Network virtualisation with overlay networking, micro-segmentation, distributed firewalling, and load balancing are exclusive to VMware Cloud Foundation. Organisations that require NSX capabilities must either upgrade to VCF or procure NSX as a standalone subscription, which carries a significant additional cost.

vSAN and the Storage Entitlement Model

VVF includes vSAN with a storage entitlement of 0.25 TiB of vSAN raw capacity per VVF core licensed. This entitlement is applied at the cluster level — vSAN TiB entitlements from all VVF cores in a cluster are aggregated and applied to that cluster's storage pool. The entitlement cannot be transferred between clusters or applied to external storage infrastructure.

The practical calculation is straightforward. A four-node VVF cluster with 48 physical cores per host — yielding 192 VVF cores under the 48-core-per-CPU counting rule — includes 48 TiB of vSAN entitlement (192 cores × 0.25 TiB). For organisations building vSAN clusters with moderate storage density, this entitlement is frequently sufficient to cover planned storage requirements without additional vSAN licences.

Where the vSAN entitlement in VVF becomes particularly significant is in the context of storage contract renewals. Organisations whose primary SAN or NAS agreements are approaching expiry should model whether the bundled vSAN in VVF — at the implied per-TiB cost derived from the VVF subscription premium over vSphere Standard — is cost-competitive with renewing standalone storage infrastructure. In many cases, the answer is yes, particularly for all-flash vSAN configurations at medium scale.

Aria Suite Standard

VVF includes Aria Suite Standard, which bundles two previously separately licensed products: Aria Operations Advanced (formerly vRealize Operations Manager) and Aria Operations for Logs (formerly vRealize Log Insight). These are not lightweight add-ons — they were previously sold as meaningful per-VM or per-CPU subscriptions in their own right.

Aria Operations Advanced provides performance monitoring, capacity analytics, workload optimisation recommendations, and predictive analytics for vSphere environments. It continuously analyses resource utilisation patterns, identifies over- and under-provisioned VMs, forecasts capacity exhaustion, and generates remediation recommendations. For environments managing hundreds or thousands of VMs, the operational value of automated capacity intelligence is significant.

Aria Operations for Logs provides centralised log collection, indexed search, and alerting across ESXi hosts, vCenter, and the broader vSphere environment. It replaces the need for a separate log management infrastructure for VMware-specific operational data. Log retention, compliance-driven audit trails, and performance correlation across log events are all supported within the bundled licence.

Organisations that previously paid for vRealize Suite products should calculate the standalone subscription value of these Aria components and include it in the VVF total cost of ownership model. Ignoring the Aria bundle — as many licence assessments do — systematically understates the commercial value of VVF relative to vSphere Standard.

Tanzu Kubernetes Grid

VVF includes Tanzu Kubernetes Grid (TKG), Broadcom's Kubernetes distribution integrated with vSphere. TKG enables provisioning and managing Kubernetes clusters directly within the vSphere environment using vSphere Namespaces and the Tanzu Kubernetes runtime. VM workloads and container workloads share the same compute infrastructure and are managed through a unified vCenter and Tanzu interface.

For organisations that have containerisation on their infrastructure roadmap, TKG in VVF provides the Kubernetes capability without requiring a separate product purchase. The practical deployment maturity required for TKG means that many VVF customers do not use it in the near term — but its inclusion ensures the capability is available when the organisation is ready without a licence change.

VVF Pricing Mechanics

List Price and Enterprise Rates

Broadcom's published list price for VVF is approximately $135 per core per year. This is the starting point for commercial discussions, not the expected outcome. Enterprise buyers with deployments of 500 or more cores and multi-year commitments typically negotiate VVF at rates between $38 and $50 per core per year. The range reflects deal size, term length, whether the customer is a competitive threat to Broadcom's revenue, and the customer's negotiating position relative to renewal timing.

VCF list pricing at approximately $350 per core per year is the reference point that makes VVF appear cost-efficient. The decision between VVF and VCF is not simply about price — the component difference (VCF adds NSX, Aria Enterprise, and the full Aria Automation suite) must be valued in the context of whether the organisation will actually use those capabilities. Paying the VCF premium for features that will not be deployed is a form of shelfware creation that should be avoided.

The 16-Core Minimum Per Physical CPU

Broadcom's licensing rules require that each physical CPU be counted as a minimum of 16 cores, regardless of actual core count. A server with two 8-core CPUs has 16 physical cores, but for VVF licensing purposes it is counted as 32 cores (two CPUs × 16-core minimum). This minimum has a significant impact on environments with older or lower-density server hardware.

For newer servers with high-core-count CPUs — 32, 48, or 64 cores per CPU — the 16-core minimum has no effect: actual core count exceeds the minimum. The impact is concentrated on servers at the lower end of the core count range. Infrastructure teams planning hardware refresh cycles should consider the licensing implication of CPU selection in the context of the VVF core minimum.

The 72-Core Minimum Order

From April 2025, Broadcom imposed a minimum purchase of 72 cores per VVF subscription order. For organisations with fewer than 72 physical cores in their environment — even after applying the 16-core-per-CPU minimum — the smallest VVF subscription they can purchase covers 72 cores. This creates a floor for the minimum annual VVF cost and particularly impacts smaller deployments, edge environments, and branch office clusters.

The 72-core minimum was not present under legacy VMware licensing and represents a structural increase in the effective per-core cost at the bottom of the market. An environment with 48 physical cores (three dual-8-core servers at 32 cores after the CPU minimum) must purchase a 72-core VVF subscription — paying for 24 more cores than physically exist.

The Late-Renewal Penalty

Broadcom charges a late-renewal penalty of 20 percent of the first year subscription cost if a VVF subscription is allowed to lapse after its anniversary date and subsequently renewed. This penalty applies regardless of the reason for the delay — contract negotiations that extend past the anniversary date, internal procurement delays, or budget approval cycles.

The practical consequence is that VVF customers must either complete renewals before the anniversary date or negotiate a grace period as part of the subscription agreement. Organisations with complex procurement processes should build renewal management calendars with 90-day lead times to avoid incurring the penalty during standard renewal cycles.

VVF Versus VCF: The Decision Framework

The most common strategic question for VMware accounts is whether to license VVF or VMware Cloud Foundation. The answer depends on five factors.

NSX Requirement

VCF includes NSX for software-defined networking. VVF does not include NSX and there is no standalone NSX add-on available for VVF. If your environment requires micro-segmentation, overlay networking, distributed firewalling, or NSX load balancing, VCF is the required tier. If your network security and segmentation requirements are met by physical network infrastructure, VVF is the appropriate choice. This is the single most important differentiating factor between the two tiers in most enterprise environments.

Aria Suite Scope

VVF includes Aria Suite Standard. VCF includes Aria Suite Enterprise, which adds Aria Automation (formerly vRealize Automation) for infrastructure-as-code provisioning, service catalogue management, and multi-cloud workload placement. Aria Automation is a material capability that justifies the VCF premium for organisations running automated self-service infrastructure delivery at scale. For organisations that provision infrastructure manually or through third-party automation platforms, the Aria Automation inclusion in VCF is shelfware.

vSAN Scope

Both VVF and VCF include vSAN entitlements. VCF's vSAN entitlement is tied to the VCF subscription — it does not add meaningfully more vSAN capacity per core than VVF. The vSAN differential between the tiers is not a decision driver for most environments.

Cost Delta

At negotiated enterprise rates, VCF typically costs two to three times more per core than VVF. For a 1,000-core environment, the annual difference between negotiated VVF ($40 per core) and negotiated VCF ($90 per core) is $50,000 per year — $250,000 over a five-year term. That delta must be justified by VCF-specific capabilities (principally NSX and Aria Automation) that will be actively deployed and operated.

Migration Complexity

Migrating from VVF to VCF requires enabling NSX on the existing vSphere environment and migrating network configuration from vDS to NSX-T. This is a material infrastructure change that requires network engineering expertise, change management, and planned downtime windows. Organisations that plan to eventually require NSX should model the migration cost as part of the VVF-versus-VCF decision and decide whether it is more cost-efficient to pay the VCF premium from the outset or absorb the migration cost later.

The Broadcom Support Cost Increase: What VVF Actually Costs

The most important number in any VVF commercial assessment is not the per-core subscription rate. It is the total all-in annual cost compared to what the organisation was paying under legacy VMware licensing before Broadcom's changes.

Under the old VMware model, an organisation with 1,000 licensed cores might have had perpetual licences with annual support running at $200,000 to $250,000 per year. Under VVF at negotiated enterprise rates of $40 per core, the same environment pays $40,000 per year in subscription fees — which appears lower on a per-line basis. But the perpetual licence value that previously sat on the balance sheet is now gone, replaced by an annual obligation. The effective support cost increase — from support-only fees under perpetual to all-in subscription — runs at 3 to 5 times the prior annual support spend for most environments.

This is the number that enterprise finance teams need to understand. Broadcom's negotiating teams frequently present VVF quotes as representing a contained cost increase. The realistic assessment requires comparing against what the organisation was paying, not against Broadcom's list price or VCF pricing.

VVF Negotiation Strategy

Establish Credible Alternatives Before Negotiating

The single most effective lever in VVF negotiations is a documented, credible evaluation of alternatives. Nutanix AHV eliminates the VMware hypervisor licence cost entirely. Azure VMware Solution provides a VMware-native cloud environment with per-host pricing that avoids Broadcom's subscription model. Documenting these alternatives — with cost models — changes the negotiating dynamic from managed urgency to competitive optionality.

Broadcom's renewal teams are aware that migration away from VMware involves real cost and complexity. But they are also aware that some organisations will proceed with migration if the economics are sufficiently unfavourable. A customer that can demonstrate it has completed a Nutanix pilot or obtained an AVS sizing and pricing quote is a customer that negotiates from a different position than one that has not.

Negotiate Term Length for Rate Reduction

Broadcom offers improved per-core rates for three-year and five-year VVF subscriptions. The rate reduction for a five-year term compared to a one-year annual subscription typically ranges from 15 to 25 percent on the per-core annual cost. Organisations with stable infrastructure footprints and no near-term migration plan should model the total five-year cost of a long-term VVF subscription against the flexibility premium of annual renewals. In most scenarios, a three-year commitment offers the best balance of rate and optionality.

Negotiate Core Count Reduction Through Infrastructure Review

Broadcom's licensing rules require licensing for every physical core in the managed environment, subject to the 16-core CPU minimum. But organisations often carry decommissioned servers, under-utilised hosts, and end-of-life hardware in their vCenter inventory. A thorough physical infrastructure audit before the renewal negotiation — identifying hosts that can be decommissioned or consolidated — directly reduces the core count that is subject to the VVF subscription. In environments that have not performed a formal hardware rationalisation, this audit can reduce the licensable core count by 10 to 30 percent.

Model the Subscription Window Carefully

VVF subscriptions are renewed at the anniversary date with a 20 percent late-renewal penalty. Organisations approaching their first Broadcom renewal — many of which were initiated in 2024 when perpetual licences were discontinued — should begin the renewal process 90 to 120 days before the anniversary date. This provides sufficient time to complete the alternatives assessment, build the negotiating position, and conclude the commercial process before the penalty clock starts.

VVF in the Context of the Alternatives Landscape

For enterprises making a VMware licensing decision in 2026, VVF is one option in a landscape that now includes credible alternatives at every level of the market.

Nutanix continues to be the most evaluated VMware alternative for enterprises seeking to eliminate the hypervisor licence cost. Nutanix AHV is bundled within the Nutanix Cloud Infrastructure (NCI) subscription, and Nutanix has invested heavily in migration tooling (Nutanix Move), competitive positioning, and financial incentives including promotional licensing for VMware customers converting their environments. For organisations whose vSAN deployments are central to their storage strategy, Nutanix's equivalent hyperconverged model provides a direct substitution.

Azure VMware Solution remains relevant for enterprises with strong Microsoft Azure footprints. AVS provides the VMware operational model — ESXi, vSphere, vSAN, NSX — on dedicated Azure hardware, eliminating Broadcom's on-premises subscription while preserving the existing operational procedures, runbooks, and skills of VMware-trained infrastructure teams. The economics of AVS depend heavily on Azure Reserved Instance pricing and the extent to which existing hardware refresh costs can be eliminated.

These alternatives do not make VVF wrong. For many enterprises, the combination of operational continuity, existing VMware skills, vSAN storage integration, and the Aria Suite management capabilities justify the VVF subscription at negotiated rates. The key is ensuring that VVF is chosen because of a reasoned commercial and operational assessment, not because the renewal process created urgency that foreclosed the evaluation of alternatives.

Ten Key Facts Every VVF Customer Needs to Know

1. All perpetual VMware licences were discontinued in 2024. There is no option to maintain perpetual VMware licences going forward. All new deployments and renewals require a subscription.

2. Support costs have increased 3 to 5 times. The all-in VVF subscription cost versus pre-Broadcom annual support fees represents a 3 to 5× increase for most enterprises. This is the commercial reality that VVF negotiations must address.

3. VVF includes vSAN at 0.25 TiB per core. The storage entitlement is bundled and aggregated across the cluster. Model it against your storage renewal cost before concluding that VVF is expensive.

4. VVF includes Aria Operations Advanced and Aria Operations for Logs. These were previously separately licensed. Include their standalone value in your VVF cost-benefit model.

5. VVF does not include NSX. If you require NSX-based micro-segmentation or overlay networking, you must use VCF or procure NSX as a standalone subscription.

6. The 16-core minimum per CPU and 72-core minimum order apply. Adjust your core count model accordingly before entering the commercial discussion.

7. The late-renewal penalty is 20 percent of the first-year subscription. Set your renewal management calendar 90 to 120 days before your anniversary date.

8. Nutanix AHV and Azure VMware Solution are credible alternatives. Both are actively deployed at enterprise scale and represent genuine optionality that strengthens your negotiating position.

9. Term length drives rate. Three-year and five-year VVF subscriptions carry meaningful discounts over annual renewals. Model the total commitment cost carefully.

10. Independent assessment before renewal is not optional for large environments. At the scale where VVF annual costs run to millions of dollars, the ROI of an independent licensing assessment is typically 10 to 20 times the advisory fee.