New Pricing Structure for NSX - VMware News - CustomNet VMware Research Jump to content

VMware Declines to Endorse Azure as a vSphere Platform

Microsoft's Azure technology publicly competes against Amazon Web Services as a VMware vSphere platform.
Read more

VCP6.5-DCV Objective 1.1: Role-Based Access Control

All entries in this study guide are in early development and are gradually being developed at the same time.
Read more

VCP6.5-DCV Objective 1.2: Secure ESXi and vCenter Server

Each entry contains links to top research sources. More links can be found at the bottom of each page.
Read more

VCP6.5-DCV Objective 1.3: Configure and Enable SSO and Identity Sources

If interested in a heavily curated Twitter feed of VMware research, please consider subscribing to my list on @vNetworking: 'VMware Top Contributors'.
Read more

VCP6.5-DCV Objective 1.4: Secure vSphere Virtual Machines

I hope that you enjoy the site and that in time it becomes a useful reference for you!
Read more
Sign in to follow this  

New Pricing Structure for NSX

Recommended Posts

As of May 2016, NSX offered three options: Standard, Advanced, and Enterprise. In 2017, there is now a fourth category called Remote Branch Office.

The full chart of comparisons can be found on the NSX Product Page. The following below has been confirmed true as of October 9, 2017.


The Advanced licensing option has an edge over the Standard option with the following additional features:

  • Automation of security policies with vRealize
  • NSX edge load balancing
  • Distributed firewalling
  • Integration with Active Directory
  • Server activity monitoring
  • Service insertion (3rd part integration)


The Enterprise option has all of these, but beats the Advanced option with these extra features:

  • Cross vCenter NSX
  • Multi-site NSX
  • VPN (IPSec and SSL)
  • Remote Gateway
  • Integration with HW VTEPs


The Remote Branch Office option is not better or worse than Advanced but has a different mix of options. Below are the features which this option lacks that separate Remote Branch Office from Enterprise:

  • Distributed routing
  • SW L2 bridging to physical environment
  • Cross vCenter NSX
  • Multi-site NSX optimizations
  • Remote Gateway
  • Integration with HW VTEPs

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this