VMware vSphere Foundation Licensing

VMware vSphere Foundation (VSF) is one of two main VMware platform SKUs in the post-Broadcom era, sitting between vSphere Standard (basic vSphere only) and VMware Cloud Foundation (the full stack). For many customers who do not need the complete VCF feature set but want more than basic vSphere, VSF is the intended landing point. The way VSF is licensed has direct implications for cost, compliance, and audit exposure. This article walks through the structure of vSphere Foundation licensing, what is included, what is not, and what to watch for during sizing, renewal, and audit.

What vSphere Foundation actually is

vSphere Foundation is a subscription bundle that combines vSphere Enterprise Plus capabilities with vSAN entry-level capacity (1 TiB per core), Aria Operations basic edition, and Tanzu Kubernetes Grid for container workloads. It is positioned as the platform for customers running mid-tier production workloads who need full vSphere features plus integrated storage and basic operations management — but who do not need the full software-defined networking, advanced automation, or extensive Kubernetes capabilities that VCF bundles include.

VSF replaced what would have been vSphere Enterprise Plus, vSphere Standard with vSAN, and vSphere Enterprise Plus with Operations Management in the pre-Broadcom catalogue. The bundling decision was deliberate: Broadcom wants customers either at the Standard tier (basic vSphere only, limited capability) or at the Foundation/VCF tier (substantial functionality, substantially higher prices). The middle ground of "vSphere Enterprise Plus with selective add-ons" no longer exists in the catalogue.

Licensing structure

Per-core pricing with minimums

vSphere Foundation is licensed per physical CPU core, with a 16-core minimum per CPU. A server with two 8-core CPUs is licensed as if it had two 16-core CPUs (32 cores total minimum). A server with two 32-core CPUs is licensed at its actual 64 cores. The minimum applies independently to each CPU, not to the host total, which catches some customers off guard when they assume the minimum is per server.

vSAN capacity inclusion

VSF includes 1 TiB of vSAN capacity entitlement per licensed core. A 64-core licensed host has 64 TiB of vSAN entitlement. Capacity above the entitlement requires additional vSAN capacity licences purchased separately. This is the single most consequential detail for capacity planning: customers who size VSF based on compute needs and assume vSAN capacity follows automatically can end up under-licensed on storage. Always size on the binding constraint, not on cores alone.

Subscription term and renewal

VSF is sold as one-year, three-year, or five-year subscriptions. Multi-year terms typically offer modest list-price discounts, but the operational implication of a longer term is loss of negotiation flexibility — once you commit five years, you lose the leverage that comes with renewal cycles. Most customers find that three-year terms balance pricing protection against negotiation flexibility most reasonably.

What is included in vSphere Foundation

The included components, in detail:

• vSphere Hypervisor (ESXi) with all Enterprise Plus features — DRS, HA, FT, vMotion, Storage vMotion, distributed switches, host profiles, Storage DRS, NIOC, Storage I/O Control
• vCenter Server Standard — single instance, managing up to 2,500 hosts and 40,000 VMs per vCenter
• vSAN Enterprise edition — full vSAN feature set including deduplication, compression, encryption, stretched clusters, file services — but with capacity entitlement limited to the 1 TiB/core inclusion
• Aria Operations (basic edition) — capacity monitoring, performance metrics, basic alerting; not the full Aria Operations capabilities included in VCF
• Tanzu Kubernetes Grid (entry edition) — basic Kubernetes runtime; not the full Tanzu Mission Control or advanced Tanzu features

What is NOT included

The features customers most often expect to find in VSF but that are not actually included:

• NSX-T or NSX Advanced Load Balancer — included only in VCF, not in VSF
• Aria Automation (formerly vRealize Automation) — included only in VCF
• HCX — sold separately or included only at higher VCF tiers
• Site Recovery Manager / VMware Live Recovery — sold separately
• Workspace ONE / Horizon — separate product lines
• Tanzu Mission Control, Tanzu Application Platform — only basic Kubernetes is included; advanced Tanzu capabilities require VCF or separate Tanzu subscriptions

The frequent surprise for customers migrating from older licensing is the absence of NSX in VSF. Pre-Broadcom, NSX-T was available as a separate purchase or as part of VCF. Post-Broadcom, the practical message is: if you want NSX, you go to VCF. There is no "VSF plus NSX" path in the current catalogue.

Pricing in practice

Public list pricing for VSF as of early 2026 sits around $135 per core per year on the published tariff, though effective enterprise pricing varies materially with negotiation, volume, and term. A 1,024-core estate at list price is roughly $138,000 per year for VSF alone, plus any additional vSAN capacity, plus any separately licensed products (NSX, HCX, SRM, etc.) layered on top.

Compared with what the equivalent capability cost under pre-Broadcom perpetual licensing plus SnS, VSF is typically 2.5–4× more expensive on a multi-year basis. The increase is the central reason VSF customers are the most active group exploring alternatives — Proxmox, Nutanix AHV, Azure Stack HCI, Hyper-V — across the industry today.

Audit implications

VSF customers are not exempt from Broadcom audits. The audit risk profile for VSF customers actually has some specific characteristics worth understanding.

vSAN capacity claims

The 1 TiB per core entitlement is the single most common audit-finding driver for VSF customers. Broadcom's discovery process will measure actual vSAN consumption against licensed core count. Customers who provisioned vSAN aggressively, or whose workloads grew beyond the entitlement, can face material claims. Track vSAN consumption against entitlement continuously — not just at renewal.

Per-CPU minimum compliance

The 16-core minimum per CPU catches customers running mixed hardware. A licence pool sized on the total core count may be short on a per-CPU basis. The audit will calculate licence requirements per-CPU and apply the minimum independently per CPU. Always do per-CPU sizing, not just total core count.

Feature usage in non-VSF tiers

VSF customers who consume features that belong to VCF — NSX, Aria Automation, Tanzu advanced capabilities — without the corresponding VCF licence will be flagged. This sometimes happens unintentionally; a VSF customer may install NSX components for evaluation, fail to remove them, and find that the audit treats this as unauthorised use. Periodic inventory of installed components is essential.

vCenter scope

VSF includes vCenter Standard. Customers who attached additional vCenter instances or who deployed Linked Mode in configurations that exceed the included entitlement may have exposure. The included vCenter scope is generous but not unlimited; verify your deployment matches the licence.

Optimising VSF cost and compliance

Right-size before renewing

Most VSF estates were originally sized on pre-Broadcom assumptions. Many have substantial unused capacity. A right-sizing exercise — actual production utilisation, removal of decommissioned-but-not-deleted VMs, consolidation of underutilised hosts — typically yields 15–30 percent licence reduction. Do this before signing a new subscription term, not after.

Track vSAN usage actively

vSAN consumption is the variable that most often pushes VSF customers into licence true-up at renewal. Monitor consumption monthly. When usage approaches 80 percent of entitlement, plan for additional capacity licences or for migration of cold data to lower-cost storage tiers.

Validate feature usage

Run a quarterly inventory of installed VMware components. Confirm that everything installed is included in your licence. Remove anything that is not. This protects against audit findings from inadvertent product installation.

Consider VCF only when the math works

Many VSF customers are pushed toward VCF by their account team, often before the customer's actual feature usage justifies it. Move to VCF only when you have validated, documented usage of the additional capabilities VCF includes. Do not move to VCF based on the assumption that you will eventually need it.

Strategic positioning of VSF in the catalogue

Understanding VSF's role in Broadcom's commercial strategy helps customers make better decisions about whether to stay there. Broadcom designed the catalogue with two preferred end-states: customers either consolidate up to VCF (the high-value bundle) or step down to vSphere Standard (where the basic functionality limits effectively force them to consider migration). VSF is the middle tier, and Broadcom's pricing trajectory tends to compress the gap between VSF and VCF over time, encouraging customers to move up.

For customers, this means VSF is a useful current-state landing point but not a strategic destination. Plan for either upward movement to VCF (if your feature requirements justify it) or for downward movement to vSphere Standard and partial migration (if cost optimisation is the priority). Treating VSF as a long-term equilibrium is generally a mistake.

Frequently asked questions

Can we still buy vSphere Foundation as a perpetual licence?

No. All VSF licences are subscription-only. Customers with existing perpetual vSphere Enterprise Plus licences plus SnS can continue running those licences as long as SnS is current, but new VSF entitlements are subscription only.

What happens to existing perpetual vSphere licences at renewal?

Broadcom is no longer selling new perpetual SnS renewals. Existing perpetual licences whose SnS lapses lose access to support and updates but the licences themselves continue to function. Most customers either renew SnS at increased rates while in transition, or migrate to alternatives, or move to VSF/VCF subscription within one to two renewal cycles.

Is the 1 TiB per core vSAN capacity raw or usable?

The included capacity is raw (before deduplication, compression, and erasure coding overhead). Usable capacity depends heavily on the workload mix and the vSAN configuration. Plan for usable capacity of 50–75 percent of raw, depending on configuration.

Does VSF include vSphere Replication?

Basic vSphere Replication is included with vCenter. Site Recovery Manager (the orchestrated DR product) is separate and not included in VSF. Customers using SRM need a separate SRM subscription.

How aggressive is Broadcom's audit activity around VSF entitlements?

Quite aggressive. The vSAN capacity entitlement is a frequent audit trigger because it is straightforward to measure and frequently exceeded by customers who did not appreciate the per-core scope. The per-CPU minimum is another common trigger. Customers should treat VSF audit risk as comparable to enterprise-level audit risk despite the smaller catalogue footprint.