NSX Licensing Under Broadcom
Introduction – Why NSX Licensing Matters
Network virtualization and security have become core needs in modern data centers, and VMware NSX has been a go-to software-defined networking (SDN) platform to meet those needs.
NSX enables micro-segmentation, virtual firewalls, and automated network provisioning within VMware environments – capabilities that many enterprises rely on to secure and manage their infrastructure.
Now that Broadcom has acquired VMware, NSX’s licensing model is undergoing significant changes, which could have a profound impact on how customers purchase and deploy this critical technology. Read our complete guide to VMware Licensing Changes Under Broadcom: vSphere, vSAN, NSX & More.
It’s more important than ever for IT procurement teams and license managers to understand the new rules of the game.
Broadcom’s licensing approach is markedly different from VMware’s legacy model, and failing to adapt could lead to steep cost increases or unwanted product bundles.
In this guide, we break down what’s changing with NSX licensing under Broadcom and how you can navigate (and negotiate) the new landscape.
NSX Licensing Before Broadcom
Before the Broadcom acquisition, VMware NSX was offered in multiple editions (Standard, Advanced, and Enterprise).
Each edition came with a different feature set – for example, Standard covered basic network virtualization, Advanced added features like distributed routing and firewalling, and Enterprise included the full suite of security capabilities (such as distributed IDS/IPS and advanced threat prevention).
Licensing metrics also varied. In traditional VMware fashion, NSX was often licensed per CPU socket (per processor) in on-premises deployments, similar to vSphere.
A single NSX license per CPU would entitle a host server’s CPU (up to a core limit) to run NSX services.
In some cases, alternative metrics existed: service providers could license NSX on a per-VM basis for multi-tenant cloud environments, and there were per-user options in VDI contexts. This flexibility allowed different consumption models, but it also added complexity.
Under VMware, NSX licensing was notoriously complex and expensive. Many customers found the cost of NSX (especially the Advanced and Enterprise tiers) to be a barrier, leading to careful consideration of whether the network security benefits justified the price.
VMware sometimes bundled NSX in broader offerings (like enterprise license agreements or the vCloud Suite) to ease adoption, but standalone NSX purchases still required significant investment.
In summary, before Broadcom stepped in, NSX had a tiered, à la carte licensing model – you could purchase only the edition you needed, and scale according to CPU or other metrics as appropriate.
This modular approach, while flexible, meant customers had to manage multiple SKUs and often negotiate discounts to make NSX financially palatable.
Broadcom’s NSX Licensing Approach
Broadcom has taken a very different approach to NSX licensing, one that emphasizes simplification of SKUs but at the cost of flexibility. The most striking change is that NSX is no longer offered as a standalone product in the way it was before. Broadcom has essentially eliminated the separate NSX editions (Standard/Advanced/Enterprise) and folded NSX’s functionality into broader solution bundles.
Specifically, VMware NSX is now bundled within VMware Cloud Foundation (VCF), Broadcom’s flagship “full stack” offering that includes vSphere, vSAN, NSX, and the VMware Aria management suite as a single package.
In other words, to get NSX under Broadcom’s model, you are strongly pushed (if not required) to purchase the entire Cloud Foundation subscription, which comes with a host of other components.
This represents a major shift from the past. There are no traditional NSX SKUs for sale on their own anymore – Broadcom’s portfolio simplification discontinued individual sale of products like NSX, vSAN, etc. (They’ve reduced thousands of VMware SKU codes down to just a few bundles.)
If you ask Broadcom or a reseller about NSX, you’re likely to be pointed to VCF or possibly a vSphere bundle with an “NSX add-on.”
Broadcom did introduce a second bundle called vSphere Foundation (VSF or VVF), which includes vSphere, basic Tanzu Kubernetes, and some Aria monitoring tools – but notably, VSF does not include NSX.
That means if you truly need NSX’s network virtualization and security features, the default Broadcom answer is VMware Cloud Foundation.
The risk for buyers here is obvious: to access NSX, you may need to invest in a much larger bundle (VCF) than you otherwise would have, potentially driving up costs by forcing you to pay for additional products you hadn’t planned on (like vSAN or the full Aria Suite).
Broadcom’s strategy appears to be maximizing value per customer by offering an all-encompassing solution, rather than selling individual components.
From their perspective, this simplifies the product line and ensures customers are fully committed to the VMware stack.
But from a customer perspective, it removes the à la carte choice – you can’t just pick NSX Advanced for a few hosts; you get “all or nothing.”
What if you only want NSX on its own? At this point, standalone NSX licenses are no longer available to new customers.
Broadcom has not explicitly launched a separate NSX-only subscription product. (In internal mappings, NSX’s capabilities are being marketed under names like VMware Firewall with Advanced Threat Protection as part of the security bundle in VCF.)
If any limited standalone NSX option exists at all, it would likely be priced under the new model (per core subscription) and only offered in special cases. For most enterprises, practically speaking, NSX = Cloud Foundation now.
Another change under Broadcom is the alignment of licensing metrics.
Historically, NSX (like vSphere) was tied to CPU sockets; Broadcom has moved VMware products to a per-core licensing model.
So if you were used to buying NSX per processor (with up to X cores covered per proc), you’ll find that now NSX (via VCF) is counted by cores. For example, VMware used to allow up to 32 cores under one CPU license; now, Broadcom might charge per 8-core or 16-core blocks.
The bottom line is Broadcom has simplified the tiers (essentially one tier of NSX in VCF) but made the licensing scope broader and the metric more granular (cores instead of CPUs). This sets the stage for potential cost increases, especially on modern servers with high core counts.
Read how to combine negotiations, How to Negotiate vSAN and vSphere Together in Broadcom Deals.
Implications for Buyers
For customers, Broadcom’s NSX licensing approach has several serious implications:
- Higher Entry Costs & Bundling: If NSX is only sold bundled, the entry price for deploying NSX is significantly higher. You can’t buy a small 2-CPU NSX license for a pilot project anymore; you might have to buy a Cloud Foundation subscription covering a whole stack. This means fewer options and a higher baseline spend just to get NSX’s functionality. Even if you don’t need vSAN or advanced management tools, you’re paying for them in the bundle. Enterprises that previously only licensed NSX for specific purposes (e.g., micro-segmentation in one cluster) now face the prospect of having to purchase a broad suite.
- Loss of Granular Control: The absence of standalone NSX editions means you can’t choose a lighter version if you only require basic features. Everyone gets the “Enterprise-equivalent” feature set as part of VCF. While that might sound good, it removes the ability to save costs by opting for a lower tier. Some organizations that only need standard networking may end up over-licensed (and overpaying) for capabilities they won’t fully utilize.
- Licensing Scope Uncertainty: It’s crucial to clarify how far NSX licensing must extend within your environment. Under the new model, if you adopt VCF to get NSX, does it require you to license your entire vSphere environment with VCF? Or can you apply it to just a subset of clusters? Broadcom’s default posture is selling enterprise-wide solutions, so there’s a risk that they expect a broader deployment. Customers need to ensure they can license NSX selectively (e.g., only in the data center or clusters where it’s needed) rather than being forced to cover every ESXi host. Without explicit agreement, you might later face a compliance issue if only part of your environment is license,d but the contract assumed all vSphere hosts should be under the bundle. It’s safer to negotiate and document the intended scope (more on that in the negotiation section below).
- Standalone vs. Bundled Pricing: If Broadcom does allow a standalone NSX subscription in some form (or an NSX add-on to vSphere), expect it to come at a premium price. Given that the bundle (VCF) itself is pricey, any carve-out product will likely be “priced to make the bundle look attractive.” In other words, Broadcom has little incentive to offer a cheap NSX-only option; they would rather you buy the full stack. So either way – bundled or hypothetical standalone – customers should be prepared for higher costs relative to what NSX used to cost under VMware’s regime.
- Data Center-Wide Impact: NSX isn’t something you sprinkle on a single VM – it operates at the virtualization layer across hosts. Therefore, licensing it often intersects with how you manage clusters and networks broadly. If Broadcom’s terms make it hard to isolate NSX to a small footprint, some buyers might end up licensing NSX broadly across their data center, even if only a portion actively uses it. This “all-in” effect could significantly increase total spend and also entangle NSX usage decisions with other IT planning (for example, you might avoid adding new ESXi hosts unless you’re ready to license them under Cloud Foundation too).
In summary, the new model implies that customers will have less flexibility and likely incur higher costs when using NSX, unless they carefully negotiate terms to limit the scope and price.
Enterprises must budget for the possibility of adopting Cloud Foundation licensing (with NSX included) or ensure that any alternative approach is contractually solid.
It’s a more one-size-fits-all model – great for Broadcom’s sales, not so great for a customer who only wanted one slice of functionality.
NSX Pricing Changes
Broadcom’s acquisition of VMware has been accompanied by pricing changes that affect NSX, as well as other products.
In general, Broadcom is known for aggressively seeking to “align prices to market rate”, which is a polite way of saying they often raise prices for acquired software to boost margins.
NSX pricing under Broadcom is no exception – many customers are bracing for higher costs compared to their previous VMware contracts.
Here are the key pricing-related changes and considerations for NSX:
- Per-Core Pricing & Higher Counts: Under VMware, NSX per-CPU licenses often covered a processor with up to 32 cores. Broadcom’s shift to per-core licensing means that if you have a host with two 24-core CPUs (48 cores total), you now need 48 core licenses. Earlier, you would have bought perhaps 2 CPU licenses (covering those 48 cores). If Broadcom charges per core, that could effectively double the cost in this example. Additionally, Broadcom instituted a minimum of 16 cores per CPU when licensing, so even a smaller 8-core processor is treated as 16 for licensing purposes. This move particularly hurts efficiency for customers with lower-core CPUs or partial use cases – you pay for capacity whether you use it or not.
- 72-Core Minimum Order: One of the most jarring changes has been the introduction of a 72-core minimum purchase requirement on new VMware subscriptions (including vSphere/VCF). This policy, which took effect in 2024-2025, means that even if you only want to license a small cluster, you must buy at least 72 cores worth of subscription. For NSX, if you were thinking of protecting a tiny environment (say a 3-host cluster with 16 cores each = 48 cores), you’d still have to buy 72 cores of Cloud Foundation licensing. This raises the floor cost dramatically, pricing out smaller deployments. Many small to medium-sized businesses and remote offices have found that this rule effectively forces them to either overspend or consider dropping VMware NSX entirely. Broadcom initially enforced the 72-core minimum strictly, although there has been some backlash. You should check if any exceptions or reductions have been made, but plan for that requirement to persist.
- Elimination of Discounts and “Friendly” Pricing: Under VMware, enterprise customers often negotiated discounts on NSX (especially if bundled in an Enterprise License Agreement). It was not uncommon to get, say, 30-50% off list price for a large commitment. Broadcom’s stance, however, has been far less generous on discounting. They are looking to increase VMware’s revenue, and one tactic is to reduce the discount margin customers can get. Many buyers with prior NSX discounts are seeing renewal quotes that strip away those concessions, effectively raising their price even if usage stayed the same. Broadcom is more rigid in pricing discussions, frequently holding closer to (or at) full list price (“market rate”). The result is that your NSX licensing costs at renewal could jump significantly purely because your old VMware deal expired and Broadcom is now pricing it anew.
- General Price Hikes: Beyond metric changes, actual price increases have occurred. Some reports from enterprises (including those in Europe and the US) indicate VMware subscription proposals that are multiple times more expensive than their previous maintenance renewals for equivalent capabilities. We’re talking increases on the order of 150% up to even 5x-10x in extreme cases where a customer had a very favorable older contract. While NSX-specific pricing is wrapped into these bundles, the overall effect is that if you were paying (for example) $X per host per year for NSX support, you might now be looking at $2X or $3X (or more) per host per year under a subscription model. Broadcom did publicize at one point that it lowered the list price of VMware Cloud Foundation (from an astronomical level down to a still-high level), but that “discount” was largely cosmetic – by bundling NSX and others into VCF and enforcing broad adoption, customers often still pay more in net terms. In short, expect NSX to cost more now than it used to, unless you carefully negotiate a deal.
- Legacy vs. Current Benchmarking: It’s wise for any customer to benchmark the new NSX pricing versus their legacy VMware pricing. Look at what you paid for NSX (and necessary support) in the past – maybe you had NSX Data Center Enterprise at $7,000 per CPU perpetual + support, or maybe $YY per VM in cloud – and compare it with what Broadcom’s subscription quote equates to. Often, translating the subscription to a 3-year or 5-year TCO will reveal the increase in cost of ownership. This benchmarking arms you with facts when pushing back. For example, “We used to spend $200k over 3 years for NSX, now this new model wants $600k for the same footprint – that’s a 3X increase.” Having those numbers can help justify demands for concessions or, at the very least, clear explanations from the vendor.
- “Market Rate” Justifications: Broadcom might argue that NSX is now priced similarly to its market competitors in networking and security. They may claim VMware underpriced some things historically to gain adoption, and that the new pricing reflects NSX’s true value. As a customer, you should take this with a grain of salt. Yes, NSX is a powerful product – but alternatives exist (physical network segmentation, other SDN solutions, cloud-native networking, etc.), which means you do have a ceiling of what you’re willing to pay before an alternative becomes more attractive. Broadcom’s “market rate” stance essentially positions itself to charge more unless customers push back or threaten to leave.
To summarize, NSX pricing under Broadcom is trending upward through a combination of new licensing metrics, broader bundle requirements, and reduced discounting. Enterprises must be vigilant at renewal or when considering NSX deployment to avoid sticker shock.
The days of VMware’s relatively negotiable, flexible NSX deals are likely over; now it’s about managing a tougher, higher-cost pricing regime. The next section will focus on how to handle this when you’re at the negotiating table.
Negotiation Strategies
If you need NSX in your environment (or want to continue using it under a new VMware subscription), negotiation is absolutely critical.
Simply accepting Broadcom’s default licensing offer could result in drastically higher costs and paying for far more software than you actually use.
Here’s the reality: without negotiation, you could end up paying for NSX across your entire environment even if you only deploy it on a subset of systems, and you may be locked into high prices for years to come.
Don’t let that happen. Instead, employ strategic negotiation tactics to tailor the deal to your needs:
- Push for Selective Licensing (Partial Deployment) – One of the top priorities should be ensuring you can license NSX for only the parts of your environment that actually need it. Broadcom’s bundle might assume a whole data center deployment, but you have the right to propose a smaller scope. For example, if only your production cluster will use NSX, insist on licensing just that cluster (say, 100 cores) rather than every host in every site. This might involve technically segmenting those hosts (so NSX isn’t enabled elsewhere) and contractually noting which clusters are licensed. Selective licensing prevents the vendor from later claiming you owe licenses for, say, your DR site or test lab where NSX isn’t in use. It can be done – but you need to negotiate this carve-out explicitly. Without it, Broadcom will happily sell you a subscription covering everything by default.
- Ask for Custom Carve-Outs (No Mandatory Enterprise-Wide Adoption) – In a similar vein, negotiate clauses that allow exceptions or carve-outs from an all-or-nothing licensing approach. For instance, you might agree to adopt Cloud Foundation in your main data center, but carve out an exception that allows remote offices or specific non-critical clusters to remain on basic vSphere without NSX. Make it clear that you are not prepared to “rubber-stamp” NSX (and its associated costs) across locations or workloads that don’t require it. A custom carve-out could also involve time-based phasing (maybe you’ll roll out NSX gradually, and only pay as you enable it in each area). The goal is to avoid a situation where the contract forces you into a company-wide NSX deployment or billing, regardless of actual need.
- Bundle for Better Discounts – Counter-intuitive as it sounds, you can turn Broadcom’s bundling strategy to your advantage in negotiations. If you genuinely are interested in other VMware products (e.g., upgrading vSphere hosts, adopting vSAN for storage, or expanding your VMware usage), consider negotiating everything together as a package deal. Vendors often offer volume or bundle discounts when a larger quantity of product is purchased at once. For example, if you’re due to refresh vSphere licenses or add vSAN, use that as leverage: “We’ll commit to the full Cloud Foundation stack – NSX, vSAN, vSphere – but in return we need a significant discount or incentive.” Broadcom wants to increase your spend, so positioning a larger purchase can give you bargaining chips to reduce the unit cost of NSX. Another approach is to involve Enterprise License Agreement (ELA) discussions – perhaps you’ll agree to a multi-product, multi-year ELA that includes NSX, which can open the door to more favorable pricing than a one-time NSX purchase. The key is to not silo your NSX negotiation; see if you can make it part of a bigger deal where you have something to trade.
- Negotiate Renewal Caps – Pricing isn’t just about the year-one cost; it’s also about what happens in year two, three, and beyond. Broadcom’s model is subscription-based so that you will have recurring renewals. It is essential to cap those renewal increases as part of your negotiations. Don’t allow an open-ended renewal clause that could result in a price hike of 20% or more annually. Instead, push for a price cap on NSX (and related bundle) renewal fees – typically in the range of 3% to 5% per year. For instance, you’d want language like “renewal rates shall not increase by more than 5% annually.” This protects you from exorbitant hikes after you’re committed. Broadcom might resist, but insist that predictability is a must if they want you to sign a multi-year deal. Even better, if you can lock the renewal price to a fixed figure or a very low escalator for a certain number of years (say, option to renew for two additional years at a fixed per-core rate), do so. Negotiating a cap now can save your budget in the long run.
- Use Alternatives as Leverage – Perhaps the most potent tool you have is the existence of alternative solutions. Broadcom needs to know that you do have other ways to achieve network virtualization and security, and you’re not afraid to consider them. Options include competitor technologies like Cisco ACI (Cisco’s SDN solution that integrates with their Nexus switches) or Juniper’s Apstra/Contrail, as well as open-source SDN projects (for example, Open vSwitch with OpenStack networking, or Tungsten Fabric, etc.). Additionally, if you’re contemplating moving workloads to the public cloud, the native cloud networking and security features (such as AWS Security Groups, Azure NSGs, and Azure Firewall) could offset the need for NSX on-premises. Without being overtly threatening, make it clear in negotiations: “At this price point, we might allocate those funds to other network solutions or cloud services.” If Broadcom’s team believes you are willing and able to migrate away from NSX, they have more incentive to be reasonable on pricing and terms. We’ve already seen some organizations explore dropping VMware entirely due to cost – you can reference those industry trends as evidence that you have a Plan B. Even if you ultimately prefer to stick with NSX, showing that you have done your homework on alternatives (and are ready to use them) is key leverage.
In all these strategies, maintain a firm but collaborative tone. Broadcom’s sales reps are under pressure to sell big bundles, but they also don’t want to lose customers.
Be prepared to justify your asks (e.g., why you only need NSX in certain areas, what budget constraints you have, how competitor quotes compare, etc.).
It may take multiple rounds, and you might need to escalate to higher management on both sides, but pushing on these points can drastically improve the deal you get.
The goal is to tailor the NSX licensing to your actual needs and budget – not to passively accept Broadcom’s first offer.
Checklist – Key NSX Licensing Terms to Negotiate
When finalizing your VMware/Broadcom agreement, make sure you address the following critical NSX licensing terms in writing.
These items can be turned into contract clauses to protect your interests:
- Selective Use Rights: “Customer may license NSX only for designated clusters or hosts, and is not required to license all vSphere hosts enterprise-wide.” – This clause ensures you’re allowed to deploy (and pay for) NSX just where you need it, without an obligation to expand coverage to every server. It’s vital for partial adoption scenarios.
- Expansion Rights (Price Lock): “Additional NSX licenses may be purchased at the same unit rate for 36 months.” – This gives you the right to grow your NSX deployment later at a predictable cost. If you add more hosts or cores, the new licenses will be at the same price per core (or with the same discount) as your initial purchase, for a set period. It prevents Broadcom from gouging you on incremental growth after you’re committed.
- Renewal Price Cap: “Annual NSX renewal fees shall not increase by more than 3% (compounded) per year.” – This clause caps how much the subscription cost can rise at renewal time. With it, you avoid nasty surprises, such as a 20% jump in year 2. Even if you sign a multi-year deal, include a cap for when that term is up. A 3-5% cap is generally reasonable and aligns with typical maintenance inflation, ensuring price stability.
Ensure that these negotiated terms are included in the contract or, at the very least, in a binding side letter. It’s not enough to have verbal assurances – you need the legal language.
By securing these provisions, you significantly reduce the chance of overpaying or being locked into unfavorable conditions as you continue to use NSX.
(Depending on your situation, you might also negotiate other terms – e.g. a bundle discount rate, or a clause allowing license termination for convenience if Broadcom’s support falters – but the above are foundational must-haves for NSX.)
FAQs on NSX Licensing under Broadcom
Q: Is NSX only sold as part of Cloud Foundation now?
Broadcom has essentially integrated NSX into the VMware Cloud Foundation bundle. As a result, new NSX licenses are generally obtained by subscribing to Cloud Foundation, which includes NSX along with vSphere, vSAN, and other components. There isn’t a readily available standalone NSX “product” that you can buy off the shelf like before. In practice, yes – if you want NSX, you will be purchasing VCF or, at the very least, a vSphere+NSX bundled offering. This represents a significant shift from when you could purchase NSX Advanced or Enterprise as separate licenses.
Q: Can I license NSX for only some clusters?
It’s possible, but you must negotiate it clearly. Broadcom’s default sales pitch might assume an enterprise-wide deployment. Still, you absolutely can restrict NSX to specific clusters or hosts – you just need to purchase subscriptions for those and deploy NSX services only there. To avoid any compliance issues, ensure your contract notes specify which environment or clusters are covered. Many customers are doing this: for example, licensing NSX for their production data center while leaving test/dev clusters without NSX to save cost. There is no technical requirement that NSX be everywhere; it just needs to be reflected in your licensing quantities and terms. Yes, you can license NSX for a subset of your infrastructure, but ensure you have that understanding in writing with Broadcom.
Q: Has NSX pricing gone up under Broadcom?
In general, yes, NSX (like most VMware products) has become more expensive under Broadcom’s ownership. The shift to subscription pricing, per-core licensing, and bundled suites means that many customers are seeing higher price tags for NSX functionality than they did before. Some of this increase is direct (list prices or fees have gone up), and some is indirect (you’re forced to buy more cores or additional products as part of a bundle). There have been reports of substantial price hikes – often several times higher than previous VMware quotes for comparable setups. While your exact situation will depend on your prior contract and what Broadcom offers you, you should be prepared for a notable increase. It’s a key reason why careful negotiation is needed – to mitigate just how much more you’ll pay going forward.
Q: What alternatives to NSX exist?
If NSX’s new licensing model doesn’t work for you, there are alternative solutions for software-defined networking and network security. On-premises, the leading competitor is Cisco ACI (Application Centric Infrastructure), which provides network virtualization through Cisco switches and an SDN controller. Many large enterprises use ACI as an alternative means to micro-segment and manage their networks. There are also open-source options (for the adventurous), such as building an SDN with Open vSwitch and OpenStack’s Neutron, or using projects like Tungsten Fabric; these can require more DIY effort but avoid vendor lock-in. For organizations moving to cloud or already hybrid, you might leverage cloud-native networking features – for example, AWS and Azure have robust network security groups, distributed firewalls, and transit networks that can fulfill similar roles to NSX in the cloud environment. Additionally, other hyper-converged and virtualization vendors offer integrated networking solutions. For instance, Nutanix provides Flow Networking and Flow Security as part of its platform, which could potentially replace some NSX use cases if you transition to AHV (Nutanix’s hypervisor). The best alternative depends on your strategic direction – if you’re staying on-prem and heavily invested in Cisco, ACI is worth a look; if you’re reducing VMware footprint, cloud provider tools, or open-source might suffice. The key is that you do have options, and knowing that gives you leverage with Broadcom (as mentioned in negotiation strategies).
5 Actionable NSX Negotiation Tips
- Confirm NSX Packaging First: Before entering into any deal, clarify with VMware/Broadcom representatives whether NSX is only available via Cloud Foundation or if an add-on option exists. Knowing the exact packaging and SKU you’ll be quoted for NSX will shape your negotiation strategy and prevent surprises.
- License Only What You Need: Don’t assume you must license NSX everywhere. Push for selective licensing – define the specific clusters or host counts that require NSX, and structure the purchase around that. This avoids blanket costs for unused coverage.
- Cap the Renewals Early: Treat future renewals as part of today’s deal. Negotiate a renewal price cap (e.g., 3-5% annual increase limit) while you have leverage so that you won’t be stuck with an exorbitant uplift in a year or two. Get this in writing as a condition of your subscription.
- Leverage Bundle Opportunities: If you foresee the need for vSphere upgrades or vSAN, bundle them with NSX in a single negotiation. A larger combined purchase can give you leverage to demand steeper discounts. Broadcom wants to sell you the whole stack – use that to squeeze more value (or a discount) out of the bundle.
- Have a Plan B (and mention it): Enter talks with a clear alternative in mind – whether it’s exploring Cisco ACI, Nutanix, or increased cloud adoption – and tactfully let Broadcom know. When a vendor realizes you’re ready to pivot away from NSX if the deal isn’t right, they are far more likely to cooperate on pricing and terms. Always be polite but firm: you have choices, and you’ll use them if needed.
By following these tips and the guidance in this article, you can approach NSX licensing under Broadcom with a strategic mindset.
The goal is to retain as much flexibility and cost-efficiency as possible in a landscape that’s pushing for one-size-fits-all subscriptions.
With careful planning and tough negotiation, you can still make NSX work for your organization without breaking the bank or giving up control of your licensing terms.
Good luck, and stay steadfast in those discussions – it’s a new era for VMware customers, but informed buyers can still emerge as the winners.
Read more about our VMware & Broadcom Licensing Consulting Services.
