Broadcom folded VMware NSX into the Cloud Foundation bundle and moved to divest Carbon Black. This CIO playbook covers the bundle math, the NSX decision, the Carbon Black exit, and the buyer side levers that remain.
Broadcom put NSX inside the Cloud Foundation bundle and moved Carbon Black toward divestiture, so the CIO question is what to keep, what to replace, and how to price it.
Broadcom packages NSX as a component of VMware Cloud Foundation rather than a standalone purchase. You receive NSX entitlement whether or not you deploy it.
That changes the CIO question. The cost is in the bundle already, so the decision is whether to use NSX or treat its entitlement as sunk and run something else.
VCF prices per core on subscription, a shift detailed across VMware Cloud Foundation materials. Listed capacity, not used capacity, is what inflates the bill.
Because NSX comes inside VCF, replacing it does not always save license money. The savings case for an alternative rests on operational fit and complexity, not the line item. NSX capabilities are documented on the VMware NSX pages.
If you run microsegmentation and software defined networking at scale, the bundled NSX is strong value. If you do not, the entitlement is sunk and a simpler stack may cost less to operate.
The NSX decision
| Factor | Keep NSX | Replace NSX |
|---|---|---|
| License cost | Already in VCF | No VCF saving |
| Operational fit | Strong at scale | Simpler stack |
| Microsegmentation | Native | Third party tool |
| Best when | You use it heavily | Entitlement is sunk |
Broadcom moved to separate Carbon Black from VMware, with public context tracked on Broadcom news. A divested product carries roadmap and integration uncertainty.
For CIOs, that uncertainty is a planning signal, not a panic button. The right response is to evaluate endpoint alternatives on a normal cycle and avoid long lock in until the ownership settles.
Move on a deliberate timeline, not a reactive one. A measured evaluation protects continuity while keeping you free to switch if the divested roadmap disappoints.
The common advice is to rip out NSX and Carbon Black the moment they land in a Broadcom bundle to cut cost. We disagree. In the Broadcom VMware renewals we reviewed, dropping NSX rarely saved license money because it is already inside VCF, and a rushed Carbon Black exit created its own migration bill. The cost lever buyers miss is the VCF core count itself, which moved spend by 40 to 100 percent. The buyer side move is to right size the core count first, use the NSX you already paid for where it fits, and time the Carbon Black exit to the ownership change rather than to a renewal panic.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
We stopped arguing about NSX as a line item and counted cores instead. Right sizing the Cloud Foundation core count moved more money than any feature negotiation on the table.
Broadcom packages NSX as a component of VMware Cloud Foundation rather than a standalone product. You receive NSX entitlement inside the bundle whether or not you deploy it, which reframes the decision around usage rather than purchase.
Usually not, because NSX is already inside the VCF subscription. The savings case for replacing it rests on operational simplicity and fit, not on a license line item. If you use NSX heavily, the bundled value is strong.
VMware Cloud Foundation is priced per core on subscription, not per socket perpetual. Listed capacity rather than used capacity drives the bill, so right sizing the core count is the primary cost lever for buyers.
Broadcom moved to divest Carbon Black, separating it from VMware. That brings roadmap and integration uncertainty rather than immediate discontinuation. The prudent response is to plan endpoint alternatives and avoid long lock in until ownership settles.
Not reactively. Evaluate alternatives on a deliberate timeline, demand roadmap commitments before extending, and keep contract terms short during the ownership change. A measured exit protects continuity while preserving the option to switch.
The VCF core count. In the renewals we reviewed it moved spend by 40 to 100 percent, far more than any feature negotiation. Counting real cores and removing unused capacity is where the money is.
Yes, and often you should. Because the entitlement sits inside VCF, using NSX where it fits captures value you have already funded. The decision is about operational fit, not avoiding a separate charge.
Sequence them into one renewal plan. Right size the VCF core count first, decide NSX on usage, and time the Carbon Black exit to the ownership change. Treating them as one coordinated plan beats three separate reactions.
A buyer side framework for the VCF bundle, the per core conversion, and the Broadcom renewal cycle. Includes the core count worksheet, the bundle interpretation guide, and the renewal leverage map used across recent VMware engagements.
Independent. Buyer side. Built for CIOs and procurement leads carrying VMware estates moving onto Broadcom subscription terms. No vendor influence. No sales kickback.
Open the playbook in your browser. Corporate email only.
Open the Playbook →
We have served 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
VCF bundle movement, per core subscription pricing, NSX adoption patterns, the Carbon Black divestiture, and the wider Broadcom commercial leverage signals across every engagement.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
