Tanzu under Broadcom, the bundle rewards breadth and punishes the slice
Broadcom collapsed the prior Tanzu portfolio into a smaller set of bundled subscription offerings priced on cores, ending most perpetual and a la carte SKUs. The bundle is efficient for customers who use all of it and expensive for the ones who used one capability, and knowing which one you are before the renewal is the whole preparation.
Prepared by Redress Compliance · August 7, 2026 · Broadcom and VMware advisory. Based on 30 to 40 VMware engagements advised 2024 to 2025.
Executive summary
Narrow users pay for the whole platform.
The prior portfolio sold Kubernetes runtime, application platform, observability, and data services separately.
The Broadcom packaging bundles them, and in roughly two thirds of the narrow estates we advised, the bundle raised effective cost 1.5 to 3 times, a 2.3x median, because the customer used one capability and now pays for the rest whether deployed or not.
Access to features you will not deploy is not value.
The metric moved to cores, and the quotes moved with it.
Pricing aligned with the wider VMware Cloud Foundation model, core based subscription only, with perpetual and most a la carte options retired: estates repriced on cores faced 20 to 40 percent quote increases at renewal, and there is no perpetual buyout to fall back on.
Confirm exactly which cores the quote counts before modeling anything.
The open source exit is real, and underused.
Tanzu is built on open foundations: upstream Kubernetes is freely available and the Spring framework remains open source, so a credible plan to run on them, or on a competing managed Kubernetes service.
Is the leverage that keeps the renewal honest. Teams that negotiated without a costed alternative lost 10 to 20 percent of available leverage, and the estates that brought one achieved a 22 percent average renewal reduction.
The strongest table is the consolidated one. Most Tanzu customers also run VMware Cloud Foundation, and co terminating the Tanzu renewal with the VCF agreement consolidates the spend into one negotiation where the leverage compounds.
Renewal quotes routinely assume full platform adoption, so the deployment audit, which Tanzu capabilities actually run in production, is the document that resizes the quote before the discount conversation starts.
Tanzu licensing, before and after Broadcom
| Dimension | Before | After Broadcom | The buyer impact |
|---|---|---|---|
| Packaging | Many separate products | Bundled platform offerings | Paying for unused features |
| Pricing metric | Mixed metrics | Core based subscription | Cost tracks the core count |
| License type | Perpetual and subscription | Subscription only | No perpetual buyout to fall back on |
| The narrow use case | Buy one product | Buy the bundle | Higher cost per used feature |
The account team pitch inverts for narrow users. The bundled platform simplifies licensing and adds value through capabilities you already paid to access, runs the pitch, and for estates using the full breadth it can hold.
For the two thirds using a slice, the bundle multiplied cost 1.5 to 3 times, which is why the deployment audit precedes every other move: list what actually runs in production, and price the quote against that, not against the platform.
The open source exit, and what makes it credible
The exit is unusually clean by VMware standards because the foundations are open: upstream Kubernetes carries the runtime, the Spring projects remain open source for the application layer, and the managed Kubernetes services from every hyperscaler compete for the workloads in between.
Credibility follows the same rule as every Broadcom negotiation: a vague preference moves nothing, and a costed plan, workloads mapped, the migration effort priced, the operational model named, moves the quote whether or not anything migrates.
The same dynamic runs across the wider portfolio, worked in the Broadcom changes guide and priced in the Broadcom pricing report, and the exit evaluations that pay either way, Nutanix and Proxmox among them, follow the identical logic one layer down the stack.
The VMware negotiation playbook
The buyer side framework across the Broadcom portfolio: the core model, the bundle deconstruction, the exit evaluations, and the moves that hold a flat renewal.
Get the white paper →The renewal traps, and the audit that defuses them
- Bundle inflation: paying for platform breadth you do not use, answered by the deployment audit listing what actually runs.
- No perpetual exit: subscription only means the walkaway is the open source plan, not a buyout, so the plan gets costed before the quote arrives.
- Assumed adoption: quotes sized to the whole bundle rather than your deployment, refused with the audit in hand.
- The uncounted cores: the core basis of the quote challenged against the infrastructure Tanzu actually runs on, before any rate discussion.
- The standalone negotiation: Tanzu negotiated apart from VCF splits the leverage, so the dates co terminate and the spend consolidates into one table.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across VMware engagements, 2024 to 2025
Across roughly 30 to 40 VMware engagements Fredrik Filipsson advised between 2024 and 2025, the move to bundled subscription raised cost most for customers who used Tanzu narrowly:
The bundle against the prior effective cost, in the two thirds of estates using one capability.
Achieved with the deployment audit, the defensible core count, and the costed exit tabled.
The negotiation sequence that produced the reductions was consistent: the deployment audit first, because the quote assumes full adoption until the audit says otherwise; the core count challenged second, because the metric conversion inflates by default.
The costed alternative third, upstream Kubernetes or a managed service, priced to executability; and the co termination with VCF closing the structure, so the whole Broadcom relationship negotiates once, with full weight, on a calendar the buyer set.
Your first five moves
- Audit the Tanzu capabilities actually in production, because the quote assumes the whole platform until your list says otherwise.
- Challenge the core count the quote assumes, against the infrastructure Tanzu genuinely runs on.
- Cost the open source exit to executability, upstream Kubernetes or a managed service, worth 10 to 20 points whether or not you move.
- Co terminate Tanzu with the VCF agreement, consolidating the spend into one negotiation with full weight.
- Refuse the full adoption quote and negotiate from the audited deployment. The Broadcom practice runs the renewal with you.
Frequently asked questions
What happened to VMware Tanzu licensing under Broadcom?
The portfolio collapsed from many separate products into a smaller set of bundled platform offerings, sold subscription only and priced on cores in line with the VMware Cloud Foundation model, with perpetual and most a la carte SKUs retired.
Customers who used one capability now buy the bundle, which raised narrow users' effective cost 1.5 to 3 times.
How is Tanzu priced now?
As a core based platform subscription aligned with the wider VCF strategy: the bundle includes capabilities previously bought separately, which helps broad users and penalizes narrow ones, and estates repriced from prior metrics onto cores faced 20 to 40 percent quote increases at renewal.
Confirm exactly which cores are counted before modeling anything.
Is there a credible alternative to Tanzu?
Yes, and it is unusually clean: upstream Kubernetes is freely available, the Spring framework remains open source, and managed Kubernetes services compete for the middle.
A costed plan on those foundations moved renewals whether or not anything migrated, and teams without one lost 10 to 20 percent of available leverage.
How much can a Tanzu renewal be reduced?
The estates that brought the deployment audit, the defensible core count, and a costed alternative achieved a 22 percent average renewal reduction in our engagements.
The audit matters most, because renewal quotes routinely assume full platform adoption, and the list of what actually runs in production resizes the quote before any discount conversation.
Should Tanzu be negotiated with the VCF agreement?
Yes: most Tanzu customers also run VMware Cloud Foundation, and co terminating the dates consolidates the spend into one negotiation where the leverage compounds.
A standalone Tanzu line negotiates against the whole Broadcom account team with a fraction of the weight the combined relationship carries.
Do perpetual Tanzu licenses still exist?
Mostly not: Broadcom retired perpetual and most a la carte options, making Tanzu subscription only with no buyout to fall back on.
The walkaway position is therefore the open source or managed service exit, which is why costing it to executability before the renewal is the single most valuable piece of preparation.
