VCF Pricing Tiers Explained
VMware Cloud Foundation is sold in three editions: Standard, Advanced, and Enterprise. The price gap between them is large; the feature gap, for most deployments, is meaningfully smaller. Picking the right tier is one of the highest-leverage decisions in any Broadcom VMware renewal.
VMware Cloud Foundation has three principal editions under Broadcom: Standard, Advanced, and Enterprise. Customers approaching a renewal under the post-acquisition catalogue almost always receive a first-proposal quote at VCF Advanced — the middle tier — regardless of which tier their deployment actually justifies. The default assumption embedded in the proposal is rarely the most cost-effective answer.
This guide walks through what each tier contains, what the price gap between them is, and how to map a specific deployment to the right tier. The decision frequently moves the deal by 25-40% on the annual run-rate; over a three-year term, the cumulative impact on an enterprise commercial regularly runs to seven figures.
The three VCF tiers at a glance
The three VCF tiers share the same core: vSphere, vSAN, NSX, SDDC Manager, and the Lifecycle Manager. The differentiation is in the breadth of NSX advanced features, the breadth of the Aria management suite, and the inclusion (or not) of Aria for Logs, Aria for Operations for Networks, and the security-focused features at the top of the stack.
VCF Standard
VCF Standard is the entry-level bundle. It includes vSphere Foundation as the compute stack, vSAN Enterprise for storage, NSX (without advanced security and load-balancing features), SDDC Manager for lifecycle, and a baseline Aria management capability. The bundle is positioned for customers who need the integrated VCF lifecycle benefits but do not require the full Advanced or Enterprise feature set.
Working list price band: $400-460 per core per year. The Standard tier is sometimes overlooked in commercial proposals because it has been re-positioned multiple times since acquisition close; customers should explicitly ask whether VCF Standard meets their requirement before defaulting to Advanced.
VCF Advanced
VCF Advanced is the principal enterprise SKU. It adds NSX Advanced (full distributed firewall, advanced load balancing), additional Aria management capabilities (Aria for Operations including capacity planning and cost analysis, Aria for Automation, Aria for Logs), Tanzu Standard (for Kubernetes workload management), and HCX (for hybrid migration). The bundle is positioned as the default enterprise VCF tier.
Working list price band: $520-600 per core per year. This is the tier most enterprise customers receive in the first-proposal quote, and it is the tier the right-sizing analysis most often challenges.
VCF Enterprise
VCF Enterprise is the top tier. It adds Aria Operations for Networks (network visibility and troubleshooting), advanced Aria features for compliance and security, and additional Aria suite components for the full operational lifecycle. The bundle is positioned for customers with full Aria suite use cases.
Working list price band: $700-850 per core per year. The Enterprise tier is appropriate only for customers genuinely using the full Aria suite; very few customers we engage with have a defensible case for Enterprise rather than Advanced.
The feature gap, decoded
The Broadcom datasheets describe the feature differences between tiers in marketing language that obscures the practical decision. Let us decode the principal differences in plain terms.
NSX Advanced features (Standard vs Advanced/Enterprise)
NSX in VCF Standard includes the basic distributed firewall, basic load balancing, and the standard NSX networking primitives. NSX Advanced (in VCF Advanced and Enterprise) adds the full distributed firewall (including Layer 7 inspection, FQDN-based rules, identity-based rules), advanced load balancing (full Avi feature set including web application firewall), and additional segmentation capabilities.
For customers running flat network segmentation with simple firewall rules and basic load balancing, the Standard NSX capability is typically sufficient. For customers running micro-segmentation, identity-based security policies, or Avi-based application delivery, the Advanced capability matters and the tier upgrade is justified.
Aria management breadth (Standard vs Advanced)
The Aria suite components included scale across the tiers. Standard includes baseline Aria Operations (capacity reporting, basic alerting). Advanced adds Aria Operations full capability (capacity planning, cost analysis, what-if scenarios), Aria for Automation (self-service catalogue, blueprint-based provisioning), and Aria for Logs (centralised logging).
For customers using only baseline Aria capabilities for capacity reporting, the Standard tier may be sufficient. For customers using Aria for Automation as the self-service interface for application teams, or Aria for Logs as the centralised log aggregation tier, the Advanced capability is required and the tier upgrade is justified.
Aria for Operations for Networks (Advanced vs Enterprise)
Aria for Operations for Networks is the network-visibility and troubleshooting tier. It is included in Enterprise but not in Advanced. Customers using this capability (typically large NSX deployments with complex troubleshooting requirements) need Enterprise; customers without this requirement do not.
Tanzu and HCX
Tanzu Standard (Kubernetes workload management on vSphere) is included in Advanced and Enterprise. HCX (hybrid migration capabilities) is included in Advanced and Enterprise. Customers without Kubernetes-on-vSphere requirements or without ongoing hybrid migration needs do not need these capabilities and should consider whether the tier upgrade is justified for capabilities that will not be used.
The price gap between tiers
Taking the working list price bands above, the inter-tier gaps are substantial.
Standard to Advanced: typically 25-35% incremental on per-core list. For a 1,000-core deployment at the mid of the bands, this is roughly $130-170 per core annually, or $130-170K per year on the deal.
Advanced to Enterprise: typically 35-45% incremental on per-core list. For the same 1,000-core deployment, this is roughly $180-250 per core annually, or $180-250K per year on the deal.
Standard to Enterprise (the full span): typically 70-85% incremental on per-core list. The cumulative cost of moving from Standard to Enterprise on a 1,000-core deployment is roughly $310-400 per core annually, or $310-400K per year.
The volume-tier and other discount stack components apply uniformly across tiers; the tier decision is principally about the underlying list-price differential rather than about discount eligibility.
Across our 2026 client portfolio, the average enterprise VCF deal where edition right-sizing was applied moved from VCF Advanced to either VCF Standard or VVF by 30-45% on annual run-rate. The work to perform the right-sizing is light; the decision discipline is the harder part. Customers should not accept the first-proposal edition without performing the analysis.
How to map your deployment to the right tier
The right-sizing analysis is methodical rather than judgemental. Walk through the following questions for the deployment.
NSX usage profile
Does the deployment use distributed firewall beyond basic source-destination rules? Does it use identity-based or FQDN-based firewall rules? Does it use micro-segmentation as a security primitive? Does it use Avi-based load balancing with web application firewall? If yes to any of these, NSX Advanced is required and VCF Advanced or higher is justified. If no, NSX Standard (included in VCF Standard) is typically sufficient.
Aria automation usage
Is Aria for Automation deployed as the self-service catalogue for application teams or for infrastructure provisioning? If yes, VCF Advanced is required. If no (i.e., self-service is handled outside Aria, or the deployment does not run a self-service model), the Aria for Automation capability in VCF Advanced is unused and the tier upgrade for this reason is not justified.
Aria operations usage
Is Aria for Operations being used beyond basic capacity reporting? Are the capacity planning, cost analysis, and what-if scenario features in active use? If yes, the Advanced-tier Aria Operations capability is required. If the deployment uses only basic reporting, the Standard-tier Aria capability is typically sufficient.
Aria logs usage
Is Aria for Logs being used as the centralised log aggregation tier? Or is logging being handled by a different platform (Splunk, Elastic, a hyperscaler logging service)? If logging is handled outside Aria, the Aria for Logs capability in Advanced is unused.
Aria operations for networks usage
Is the network-visibility and troubleshooting capability of Aria for Operations for Networks in active use? This is principally relevant for large NSX deployments with complex topology and troubleshooting requirements. If not in use, VCF Enterprise is not justified.
Tanzu and Kubernetes usage
Is Tanzu Standard being used for Kubernetes workload management on vSphere? If yes, Advanced is required. If no (e.g., Kubernetes is running on a separate platform such as OpenShift or a managed Kubernetes service), the Tanzu capability is unused.
HCX usage
Is HCX being used for ongoing hybrid migration? If yes, Advanced is required. If HCX is not in use (or was used for a one-off migration that has completed), the capability is not justifying the tier on an ongoing basis.
The aggregated answer to these questions produces the right-sized tier recommendation. Customers honestly answering the questions frequently find that the deployed feature set justifies VCF Standard, VVF, or sometimes only vSphere Foundation rather than VCF Advanced.
When VCF Enterprise is actually justified
VCF Enterprise is rarely the right tier. The customers we have engaged with where Enterprise is actually justified share several attributes: very large NSX deployments (multi-thousand-core) with complex network topology requiring Aria for Operations for Networks for troubleshooting; large enterprise security postures using the full Aria security and compliance capabilities; or enterprise operations teams with full Aria suite adoption as a strategic operational standard.
For most customers receiving an Enterprise quote in the first proposal, the right response is to ask explicitly what feature set the Enterprise tier provides beyond Advanced and to map the additional features against the deployed usage. The mapping typically shows that the additional cost is not justified by the additional usage.
When VCF is wrong altogether: the VVF and vSphere Foundation alternatives
The right-sizing analysis sometimes shows that even VCF Standard is not the right tier — the deployment's use of vSAN, NSX, and Aria is sufficiently limited that VVF or vSphere Foundation makes more sense.
VVF (VMware vSphere Foundation, in the bundled-with-vSAN configuration) includes vSphere, limited vSAN (100GB per core), and curated Aria management capabilities. It excludes NSX and the broader Aria suite. Working list price band: $320-380 per core per year. For vSphere-and-light-vSAN deployments without NSX advanced requirements, VVF can be 30-50% below VCF Standard on annual run-rate.
vSphere Foundation (standalone, without vSAN) includes vSphere with a baseline lifecycle and management capability. It excludes vSAN, NSX, and the Aria suite. Working list price band: $180-230 per core per year. For deployments where storage and networking are handled outside the VMware stack, vSphere Foundation can be 50-70% below VCF Standard.
The decision between VCF Standard, VVF, and vSphere Foundation depends on whether the deployment actually uses vSAN and NSX. Customers using third-party storage (e.g., PowerStore, NetApp, Pure) and third-party networking (e.g., physical fabric without NSX overlay) typically do not need either vSAN or NSX and should consider vSphere Foundation.
The tier-upgrade dynamic across the term
Customers selecting a lower tier in the initial commercial sometimes worry about mid-term upgrade if the deployment grows into requiring a higher tier. The mid-term upgrade is possible commercially but typically at less favourable economics than the initial-commercial pricing. The trade-off is between paying for the higher tier from the outset (over-paying if the higher capability is not used) and paying a transition premium if the upgrade becomes necessary.
The economically rational discipline is usually to size the initial commercial against the credible deployment trajectory and to accept the mid-term upgrade risk if the trajectory shifts. The risk is materially smaller than the cost of over-buying the higher tier from the outset.
Negotiating around the tier decision
The negotiation against the tier decision works on two axes: justifying the customer's preferred tier (typically lower than the first-proposal tier) and securing the discount stack at that tier.
The tier-justification argument should be made on deployed-feature-set grounds rather than on cost grounds alone. Broadcom's commercial team will not accept "we want a lower tier because it is cheaper" but will accept "our deployment does not use NSX Advanced features, Aria for Automation, or Tanzu, and we are committing to the appropriate tier for the deployed feature set." The latter framing is more persuasive and aligns with the supplier's published positioning of the tiers as fit-for-purpose.
The discount stack at the lower tier should be negotiated independently of the tier decision. The volume-tier and other discount components apply uniformly across tiers; the customer should not accept a discount reduction at the lower tier as a trade-off against the tier decision.
A worked example: 1,500-core enterprise customer
Consider a 1,500-core enterprise customer running vSphere Enterprise Plus and vSAN with NSX deployed for basic firewall and segmentation. Aria is used for capacity reporting only. Tanzu is not used. HCX is not in active use.
First-proposal tier (VCF Advanced): at the mid of the band, approximately $560 per core annually. At a 30% volume-tier discount and a 10% three-year term, the effective is approximately $353 per core per year, or $530K annual run-rate.
Right-sized tier (VCF Standard): at the mid of the band, approximately $430 per core annually. At the same discount stack, the effective is approximately $271 per core per year, or $406K annual run-rate. The right-sizing saves approximately $124K annually, or $370K over the three-year term.
Alternative right-sized tier (VVF, if NSX use is genuinely basic and replaceable): at the mid of the band, approximately $350 per core annually. At the same discount stack, the effective is approximately $221 per core per year, or $331K annual run-rate. The further right-sizing to VVF would save approximately $199K annually beyond Advanced, or $597K over the three-year term — but at the cost of losing NSX capability, which the customer has to verify is acceptable.
The example shows the cumulative impact of edition decisions on commercial outcome. Customers performing the right-sizing analysis as a routine part of the renewal cycle find that the discipline is consistently the single largest lever on the commercial.
Related reading
For deeper detail, see the Broadcom VMware pricing pillar, VCF licensing explained, VCF pricing analysis, VCF components breakdown, VVF vs VCF comparison, our pricing calculator methodology, and discount structures.