VMware Tanzu licensing in 2026. Why the Broadcom bundle costs narrow users more.

Broadcom sells Tanzu as bundled, per core subscriptions with no perpetual option. The bundle suits customers who run the whole platform and costs the rest far more, so find out which group you are in before the renewal quote arrives.

What changed in VMware Tanzu licensing under Broadcom?

Broadcom folded a long list of separately sold Tanzu products into a small set of bundled platform subscriptions, priced on cores. Broadcom also retired perpetual licenses and most a la carte SKUs. If you bought one Tanzu product before, you are now asked to buy the platform it sits in.

The old catalog let you pick a Kubernetes runtime, an application platform, observability and data services one at a time. The new packaging follows the wider VMware Cloud Foundation model: subscription only, per core, sold as a platform.

Which Tanzu components now sit inside the bundles?

For the largest bundle, Tanzu Platform for Cloud Foundry, Broadcom's knowledge base lists the products it contains. Check your quote against this list, because each line is a capability you may or may not deploy.

• Application runtime. Tanzu Application Service (the Cloud Foundry runtime) plus Operations Manager for install and lifecycle.
• Spring. Tanzu Spring Runtime, the commercial Spring subscription with longer support windows and enterprise builds.
• Data and messaging. Tanzu RabbitMQ, Tanzu for Postgres and Tanzu for MySQL on Cloud Foundry, plus Tanzu for Redis for Tanzu Application Service.
• Delivery and observability. Concourse for Tanzu pipelines and the Tanzu Observability by Wavefront integration.

The Kubernetes runtime went the other way. VMware states that vSphere Kubernetes Service, the renamed Tanzu Kubernetes Grid Service from vSphere with Tanzu, is included in VMware Cloud Foundation at no extra cost. If Kubernetes on vSphere was all you used, your VCF entitlement may already cover it.

How is Tanzu priced now, and which cores does the quote count?

Tanzu is now a per core platform subscription aligned with VCF pricing. Customers moved from the old metrics onto cores saw renewal quotes rise 20 to 40 percent, and there is no perpetual option to retreat to. Before you argue about the rate, find out how many cores it was multiplied by.

VCF itself counts physical cores on every licensed ESXi host, with a minimum of 16 cores per CPU, under Broadcom's published counting rules. A Tanzu quote may reuse that host count by default. Ask which hosts and clusters the Tanzu line was sized on before you model any price.

Where does the core count in a Tanzu quote usually go wrong?

• Whole VCF footprint. The quote counts every core in the VCF environment, including clusters that never run a Tanzu workload.
• Old sizing carried forward. Cores from a proof of concept or a retired foundation are still in the renewal baseline.
• Test and disaster recovery. Nonproduction and standby clusters are counted at the same rate as production.
• Growth assumptions. The quote builds in expansion your platform team has not planned.

A worked example: what a core recount does to the quote

Say a company paid $150,000 a year for one Tanzu capability under the old metric. The renewal arrives as a platform bundle at $360,000 a year on 1,200 cores, which is $300 per core and 2.4 times the prior spend. The Tanzu workloads run on clusters with 800 cores.

The recount alone removes $120,000 a year without touching the rate. The result is still 1.6 times the old spend, which is why the costed alternative and the VCF co termination come next. The figures are illustrative, not Broadcom list prices.

Does the Tanzu bundle make sense if you only use one part of it?

For most narrow users it does not. In roughly two thirds of the narrow Tanzu environments we advised, the bundle raised effective cost 1.5 to 3 times, with a median of 2.3x. Those customers used one capability and now pay for the rest whether it is deployed or not.

The bundle does work for a customer running the full platform: Cloud Foundry, Spring, data services and observability all in production. For that buyer, the per core price can come in below the old sum of separate products.

How the answer changes with what you run

Spring is a good test case. Open source Spring Boot minor releases get at least 13 months of support, while the commercial subscription gives at least 25 months, according to the Spring support policy. If your teams upgrade on schedule, the extra support window may be worth little to you.

Spring Cloud Data Flow is the exception. Broadcom stopped maintaining it as open source in April 2025, with 2.11.x as the last open source line, and did the same for Spring Cloud Deployer and Spring Statemachine. New releases of those three go only to Tanzu Spring customers, while the rest of the Spring portfolio stays open source.

Should you accept the bundle because the extra capabilities come included?

The account team will say the platform simplifies licensing and gives you capabilities you already paid to access. Some advisors repeat this and call unused modules free upside. We disagree. A feature you will not deploy delivers no value, and its price stays in the base that every future increase is applied to.

Price the quote against what runs in production, and ask for unused capabilities to be removed or priced at zero.

What makes the open source exit from Tanzu credible?

The exit is cleaner than elsewhere in VMware because the foundations are open. Upstream Kubernetes carries the runtime, the Spring projects stay open source for the application layer, and every hyperscaler's managed Kubernetes service competes for the workloads in between.

A vague preference for open source changes nothing in a Broadcom negotiation. A costed plan does, whether or not anything migrates. Teams that negotiated without one lost 10 to 20 percent of the negotiating room available to them.

What a costed alternative has to contain

1. Workload map. Every Tanzu workload listed with its target: upstream Kubernetes, a managed service, or retirement.
2. Migration effort. Engineering weeks and any partner cost, priced per workload group.
3. Operating model. Who runs the platform after migration, and what that team costs per year.
4. Replacement subscriptions. Managed service fees and any commercial support for Kubernetes, Spring or data services.
5. Timeline. A sequence that could start inside the next renewal term.
6. Sponsor. A named executive who has signed off on the plan.

The same logic runs across the wider VMware portfolio, set out in our Broadcom changes guide and priced in the Broadcom pricing report. One layer down the stack, the exit evaluations for Nutanix and Proxmox pay off in the same way, whichever way you decide.

What have we seen in recent Tanzu and VMware renewals?

Across roughly 30 to 40 VMware engagements I advised between 2024 and 2025, the shift to bundled subscription hurt customers who used Tanzu narrowly the most. The customers who did the preparation work below finished well under the first quote they received.

Those who arrived with the deployment audit, a checked core count and a costed alternative achieved an average renewal reduction of 22 percent. The order of work was the same each time.

1. Deployment audit. The quote assumes full adoption until your list says otherwise.
2. Core count challenge. The conversion from old metrics to cores inflates by default.
3. Costed alternative. Upstream Kubernetes or a managed service, priced to the point where it could be executed.
4. Co termination with VCF. The whole Broadcom relationship is negotiated once, with full weight, on a calendar you set.

Renewal quotes assume you run the whole platform. The list of what runs in production resizes the quote before any discount conversation starts.

How to check what you actually run

• Kubernetes. The Supervisor and workload cluster inventory in vCenter or VCF Operations, and kubectl get nodes against each cluster, give hosts and node counts.
• Cloud Foundry. Operations Manager shows which tiles are installed, and cf apps across orgs and spaces shows what is live.
• Spring. A dependency scan such as mvn dependency:tree shows which Spring Boot versions you ship and whether any build pulls enterprise only artifacts.
• Entitlements. The Broadcom Support Portal lists what you are licensed for, which you compare line by line with the deployment list.

What are the common Tanzu renewal traps, and how do you avoid them?

Five traps come up on most Tanzu renewals we see. Each one has a specific answer you can prepare before the quote arrives.

• Bundle inflation. You pay for platform breadth you do not use. The deployment audit answers it.
• No perpetual exit. Subscription only means your walkaway is the open source plan, since there is no buyout. Cost the plan before the quote lands.
• Assumed adoption. The quote is sized to the whole bundle rather than your deployment. Refuse it with the audit in hand.
• Uncounted cores. Challenge the core basis against the infrastructure Tanzu runs on, before any talk about rate.
• Standalone negotiation. Negotiating Tanzu apart from VCF splits your weight, so align the dates and bring the spend to one table.

What the account team will say, and how to reply

Contract terms to ask for

• Core definition. Name the clusters or hosts in scope, so the count cannot drift to the whole VCF footprint later.
• Component list. Attach the capabilities you licensed, so unused modules cannot be used to justify the next increase.
• Renewal cap. A fixed ceiling on the next renewal price, since there is no perpetual fallback.
• Reduction right. The right to drop cores or components at renewal as workloads leave the platform.
• Co termination. The Tanzu end date aligned with the VCF agreement.

Why should Tanzu be negotiated together with the VCF agreement?

Most Tanzu customers also run VMware Cloud Foundation, and Broadcom negotiates the whole account. A standalone Tanzu line faces the full account team with a fraction of the spend behind it. Co terminating the two agreements puts the total spend into one negotiation, where your weight adds up.

What to do next

1. This month, build the deployment list. Pull cluster, tile and application inventories with the checks above, and set them beside your entitlements in the Broadcom Support Portal.
2. Ask for the quote by cluster and component. Request a breakdown of the cores and capabilities the Tanzu line was priced on, so every assumption can be tested.
3. Cost the exit. Price upstream Kubernetes or a managed service to the point of execution, with a named sponsor, whether or not you intend to move.
4. Put co termination in writing. Ask Broadcom to align the Tanzu end date with the VCF agreement before either quote is final.
5. Refuse the full adoption quote. Negotiate from the audited deployment and the contract terms above. Our Broadcom practice can run the renewal with you.

Frequently asked questions