VMware Tanzu Licensing. The Broadcom era.

Broadcom collapsed the Tanzu SKU sprawl into a bundled platform on core based subscription, which raises cost for narrow users and changes the renewal math entirely.

What happened to VMware Tanzu licensing after the Broadcom acquisition?

Broadcom completed its acquisition of VMware and restructured the product line around bundles and subscriptions. Tanzu was repackaged from a wide portfolio of separate products into a smaller set of platform offerings.

The headline change for buyers is the end of most perpetual and a la carte options. Tanzu is now a subscription, and the unit of pricing aligns with the wider VMware Cloud Foundation strategy.

Broadcom describes the current Tanzu line on its Tanzu product page, and the acquisition and portfolio changes are documented in Broadcom's company news.

From SKUs to the Tanzu Platform bundle

The prior Tanzu portfolio included separate products for Kubernetes runtime, application platform, observability, and data services. Broadcom consolidated these into a smaller set of bundled platform offerings.

• Fewer SKUs: a narrower menu replaces the prior product sprawl.
• Bundled capabilities: features that were bought separately now travel together.
• Subscription only: perpetual and most a la carte options are retired.

Core based pricing and the subscription shift

Pricing moved to a core based subscription consistent with how Broadcom prices VMware Cloud Foundation. The technical documentation for the current platform sits in the Broadcom Tanzu technical documentation. Confirm exactly which cores are counted before you model a renewal.

How is Tanzu packaged and priced now?

Tanzu is sold as a platform subscription priced on cores, in line with the VMware Cloud Foundation model. The bundle includes capabilities that were previously separate purchases, which helps broad users and penalizes narrow ones.

If you used the full breadth of Tanzu, the bundle can be efficient. If you used one capability, you now pay for the rest whether you deploy it or not.

Where the common advice on Tanzu in the Broadcom era is wrong

The standard Broadcom account team pitch is that the bundled platform simplifies licensing and adds value through capabilities you already paid to access. We disagree. In roughly two thirds of the narrow Tanzu estates we advised in 2024 and 2025, the bundle raised effective cost by 1.5 to 3 times because the customer used one capability and now pays for the whole platform. The buyer side move is to audit which Tanzu capabilities are actually deployed, price the bundle against a focused open source alternative, and negotiate from that costed exit. Access to features you will not deploy is not value.

Under Broadcom the Tanzu bundle rewards customers who use all of it and punishes the ones who use a slice. Know which one you are before you renew.

What are the migration and renewal traps for Tanzu customers?

The traps are bundle inflation, the loss of perpetual rights, and renewal quotes that assume full platform adoption. Each can be managed with a usage audit and a credible alternative in hand.

• Bundle inflation: paying for platform breadth you do not use.
• No perpetual exit: subscription only means there is no buyout to fall back on.
• Assumed adoption: quotes sized to the whole bundle, not your deployment.

Open source exits: Kubernetes, Spring, and the alternatives

Tanzu is built on open foundations. Upstream Kubernetes is freely available, and the Spring open source projects remain open source. A credible plan to run on these, or on a competing managed Kubernetes service, is the leverage that keeps a Tanzu renewal honest.

Co terminating Tanzu with the VCF agreement

Most Tanzu customers also run VMware Cloud Foundation. Aligning the Tanzu renewal date with the broader VCF agreement consolidates spend into one negotiation and increases leverage. Broadcom documents the VCF platform on its VMware Cloud Foundation page.

What buyer side moves protect a Tanzu estate?

Protect the estate by auditing real usage, pricing a focused alternative, and negotiating Tanzu inside the wider VMware relationship rather than as a standalone line.

1. Audit deployment: list the Tanzu capabilities actually in production.
2. Cost an alternative: price upstream Kubernetes or a competing service.
3. Co terminate: align the Tanzu date with the VCF agreement.
4. Right size cores: challenge the core count the quote assumes.

How to handle the renewal quote

Bring the deployment audit, the costed alternative, and the core count you can defend. Refuse a quote sized to full platform adoption when your deployment is narrower, and use the open source exit as the anchor.

What to do next

1. Audit which Tanzu capabilities are actually deployed in production today.
2. Confirm exactly which cores Broadcom counts toward the subscription.
3. Price a focused alternative on upstream Kubernetes or a competing managed service.
4. Align the Tanzu renewal date with your VMware Cloud Foundation agreement.
5. Challenge any renewal quote sized to full platform adoption against your real usage.
6. Negotiate from the costed exit, not from the bundle list price.
7. Document the agreed core count and bundle scope in the order, not on a slide.

Frequently asked questions

Is VMware Tanzu still sold as separate products?

No. Broadcom consolidated the prior Tanzu portfolio into a smaller set of bundled platform offerings sold on subscription. Most separate products and a la carte purchases were retired in favor of the platform bundle.

Can I still buy Tanzu on a perpetual license?

No. Tanzu is now subscription only under Broadcom. Perpetual licensing and the buyout fallback it provided are no longer available, which changes the long term cost calculation.

Why did my Tanzu cost go up under Broadcom?

Narrow users see the largest increases because the bundle forces them to pay for platform breadth they do not deploy. Core based subscription pricing also raises cost where the core count is high relative to prior metrics.

How is Tanzu priced now?

Tanzu is priced as a core based subscription aligned with the VMware Cloud Foundation model. The cost tracks the number of cores running the platform, so confirming the counted cores is central to any renewal.

What is my exit option from Tanzu?

Tanzu is built on upstream Kubernetes and the open source Spring projects, both of which remain freely available. A costed plan to run on these or a competing managed Kubernetes service is the main source of renewal leverage.

Should I co terminate Tanzu with my VCF agreement?

Yes, in most cases. Aligning the Tanzu renewal with the broader VMware Cloud Foundation agreement consolidates spend into one negotiation and increases your leverage with Broadcom.

How do I avoid paying for Tanzu features I do not use?

Audit which capabilities are actually deployed, then negotiate the bundle scope and core count against that real usage and a costed open source alternative rather than accepting a quote sized to full adoption.

Does Broadcom price Tanzu the same way as VMware Cloud Foundation?

Tanzu now uses a core based subscription consistent with how Broadcom prices VMware Cloud Foundation. This alignment is part of why co terminating the two agreements improves negotiation leverage.