VMware NSX Licensing and Pricing Model: The Enterprise Guide for 2026

VMware NSX: What You're Licensing

NSX is VMware's software-defined networking (SDN) and network security platform. It virtualises network functions — routing, switching, firewalling, load balancing, micro-segmentation — in software, decoupled from underlying hardware. For enterprises that have standardised on NSX, it provides deep integration with vSphere and vSAN, consistent networking policy across environments, and advanced security capabilities through micro-segmentation.

The commercial significance of NSX under Broadcom is that it is simultaneously one of the most technically differentiated products in the VMware portfolio and one of the most difficult to replace. This combination — high value, high switching cost — has influenced how Broadcom prices and packages NSX in its post-acquisition commercial model. Understanding this context is essential to effective NSX licensing negotiation. The broader commercial environment is covered in our Broadcom VMware Licensing Guide 2026.

NSX Edition Tiers Under Broadcom

Broadcom has rationalised VMware's product portfolio substantially. NSX, previously available as NSX Data Center Standard, Advanced, and Enterprise Plus, is now primarily available as a component within VMware Cloud Foundation (VCF) or as a standalone NSX subscription. Here is how the tiers align in 2026.

Within VCF, NSX Enterprise Plus is included in the VCF subscription. For organisations on VCF, this means they are paying for Enterprise Plus capability regardless of whether they use the advanced features — which is either excellent value or unnecessary cost depending on your use case.

How NSX Is Priced in 2026

NSX pricing has shifted from socket-based perpetual licences to per-core subscription, consistent with Broadcom's broader VMware commercialisation strategy.

Per-Core Subscription (Standalone NSX)

Standalone NSX subscriptions are priced per CPU core, applied to hosts running NSX. As with vSphere and vSAN, this creates a cost amplification effect for modern servers with high core counts. A dual-socket server running 64 cores per socket (128 total cores) represents 128 units of NSX licensing at whatever the per-core rate is for your negotiated tier.

Published list pricing for NSX is not publicly disclosed by Broadcom, but market intelligence from enterprise negotiations suggests standalone NSX Advanced per-core annual rates in the range of $40–$120 depending on volume and negotiated discount. At $60/core for a 10,000-core estate, that is $600,000 annually for NSX alone — a significant budget line in environments where NSX was previously bundled at marginal cost.

NSX Within VCF

VCF bundles NSX Enterprise Plus with vSphere, vSAN, Aria, and support into a single per-core subscription. For organisations that require the full VMware stack, the bundle economics can be favourable compared to licensing each component separately. However, for organisations that use NSX without vSAN, or vSphere without NSX, the bundle creates overpayment for components not used. This is discussed in our VCF Licensing guide.

Legacy Perpetual NSX

Enterprises with legacy NSX Data Center perpetual licences — particularly those with active support — retain usage rights for the version they licenced. The critical question is support: active support entitles you to current software versions. Lapsed support limits you to the version in production at the time support expired, which creates both security risk and feature drift.

Cost Implications for Enterprise Environments

The Core Count Problem

The shift from socket-based to core-based licensing affects NSX as significantly as it affects vSphere. An enterprise that licenced NSX for 500 dual-socket servers (1,000 sockets) at $X per socket now licences the same environment for potentially 64,000 cores (500 servers × 2 sockets × 64 cores per socket) at $Y per core. Even if the per-core rate is set to be nominally comparable at average core counts, the reality for modern high-core-count servers is a substantial cost increase.

NSX in Environments Without vSAN

Organisations that use NSX for its networking and security capabilities but rely on traditional SAN or NAS storage rather than vSAN are at a pricing disadvantage in the VCF model. VCF pricing assumes the full stack. If you need NSX Enterprise Plus but not vSAN, standalone NSX may be commercially preferable — but Broadcom's commercial teams consistently push VCF. Negotiating a standalone NSX subscription requires explicit conversations about your architecture and use case.

Distributed vs. Gateway Firewall Usage

NSX's distributed firewall (DFW) is the primary micro-segmentation tool, running on every hypervisor host. The gateway firewall runs on dedicated NSX Edge nodes. Organisations whose primary NSX use case is gateway firewalling at lower scale may be able to negotiate reduced-scope NSX licensing based on Edge node count rather than full hypervisor estate core count. This is not a default Broadcom position but has been negotiated in specific architectural configurations.

NSX-Specific Negotiation Strategies

NSX licensing negotiations require understanding both the technical scope of your deployment and the commercial levers available. These strategies apply to 2026 renewal and new commitment conversations with Broadcom.

1. Scope Your Actual NSX Footprint

Before any negotiation, run an accurate inventory of which hosts are running NSX (as Transport Nodes) and which are not. Guest hosts, Edge nodes, management clusters, and cold DR hosts may not need to be licensed at the same tier or at all. Reducing the in-scope host count before negotiation is purely a scoping exercise — but it directly reduces the quantity basis for pricing and is entirely legitimate.

2. Challenge Feature Tier Requirements

Most enterprises using NSX leverage distributed firewalling and L2/L3 switching — features that do not require Enterprise Plus. If your actual use case is Advanced or Standard, negotiate for that tier rather than accepting the Enterprise Plus default that comes with VCF. The savings on a 50,000-core estate between Advanced and Enterprise Plus can be material.

3. Use Alternative Evaluation as Leverage

The SDN market has matured significantly. Cisco ACI, Arista CloudVision, and open-source alternatives (OVN, Cilium) are credible for specific use cases. Being able to demonstrate an active evaluation of alternatives creates genuine commercial pressure, particularly as Broadcom's account teams track enterprise migration activity. This is detailed further in our VMware Alternatives guide.

4. Negotiate the Transition Timeline

If you have legacy perpetual NSX with active support, you are not under immediate commercial pressure to convert to subscription. Use this position to negotiate transition timing that aligns with your infrastructure refresh cycle — and use the time to reduce your core footprint before the subscription pricing is applied.

5. Demand NSX-Specific Pricing in VCF Proposals

When evaluating VCF vs. standalone NSX, require Broadcom to provide explicit per-component pricing within the VCF bundle. This allows proper financial modelling of the bundle economics for your specific use case — and sometimes reveals that a standalone NSX subscription plus VVF (which excludes NSX) is more cost-effective than full VCF.

NSX Migration and Replacement Considerations

For enterprises evaluating whether to continue with NSX under Broadcom's pricing model or migrate to alternative networking solutions, the key considerations are feature parity, migration complexity, and long-term cost trajectory.

NSX micro-segmentation — applying distributed firewall policy at the workload level — remains technically differentiated relative to most alternatives. However, for organisations primarily using NSX for L2/L3 overlay networking and basic perimeter firewalling, the cost increase under Broadcom may not be justified relative to alternatives.

Migration from NSX is operationally complex, particularly for environments with extensive DFW policies and distributed routing configurations. Enterprises that undertake migration assessments typically identify a subset of workloads that are economically viable to move and retain NSX for security-critical segments. This hybrid approach — reducing NSX scope rather than eliminating it — is often the commercially optimal outcome.

NSX Budget Planning for 2026

For IT budget planning purposes, enterprises with NSX should model the following scenarios to prepare for renewal conversations with Broadcom.

• Status quo perpetual support renewal: Understand what Broadcom will actually charge for support renewal on your legacy NSX estate — this is your baseline comparison point.
• Standalone NSX subscription: Request standalone NSX subscription pricing (not just VCF) for your current in-scope host estate at your relevant feature tier.
• VCF full bundle: Request VCF subscription pricing for the same estate, noting what additional components you receive.
• Right-sized VCF: Model the VCF cost after eliminating non-essential hosts from scope (cold DR, dev/test, management clusters).
• Partial migration scenario: Estimate the cost of migrating lower-criticality segments to alternative networking platforms and retaining NSX for production security workloads only.

Having these five scenarios modelled before engaging Broadcom commercially ensures you are negotiating from analysis rather than reaction. For specialist support in building this model and executing the negotiation, the IT Negotiations team is available for a free initial consultation.