Broadcom collapsed dozens of VMware Tanzu SKUs into a Tanzu Platform bundle. The metric reset. The audit risk shifted. Read the buyer side response for Kubernetes estates carrying a Tanzu line in the next VCF renewal.
Broadcom collapsed VMware Tanzu into a Tanzu Platform bundle in 2024 and 2025. The license metric reset to per core capacity. Standalone Tanzu Application Service and Tanzu Kubernetes Grid options narrowed. The buyer side response is a Kubernetes inventory, a Tanzu Platform vs adjacent option model, and a clear stance for the next VCF renewal call.
Pair this article with the Broadcom licensing changes reference, the VMware alternatives comparison guide, and the Broadcom negotiation playbook.
Broadcom closed the VMware acquisition in November 2023. By mid 2024 the Tanzu product line was restructured. The 2025 catalog reflects the consolidated Tanzu Platform with a per core subscription as the primary commercial vehicle.
The metric reset is the most expensive change. Enterprises that priced Tanzu on application count or node count under the pre Broadcom catalog are repricing on cores. Some estates land lower. Many land higher. The TCO model is the only artifact that tells the difference.
The Platform bundle covers Kubernetes lifecycle, application runtime, observability, and policy. Specific components remain as named features inside the bundle.
| Capability | Pre Broadcom SKU | Where it lives now |
|---|---|---|
| Managed Kubernetes | Tanzu Kubernetes Grid | Tanzu Platform, or VCF Kubernetes capability |
| Multi cluster management | Tanzu Mission Control | Tanzu Platform module |
| Application runtime | Tanzu Application Service | Tanzu Platform Apps (constrained roadmap) |
| Observability | Tanzu Observability (Wavefront) | Aria Operations for Applications |
| Service mesh | Tanzu Service Mesh | Tanzu Platform, partial overlap with NSX |
Tanzu Platform subscriptions are priced on cores. The cores counted are the physical or vCPU cores allocated to the Kubernetes capacity, not the entire vSphere cluster.
Several VCF editions include Tanzu Kubernetes at no incremental cost. Before signing a Tanzu Platform line, run the entitlement check on the existing VCF agreement. Many estates that priced Tanzu standalone two years ago are now covered under VCF. The check takes a contract review and a feature map against the cluster inventory.
The buyer side question is whether to take Tanzu Platform inside VCF, alongside VCF, or to step out to an adjacent Kubernetes distribution.
| Path | Commercial profile | Best for |
|---|---|---|
| Tanzu inside VCF | Bundled in higher VCF edition | Heavy VCF estates already at the higher edition |
| Tanzu Platform standalone | Per core subscription line | Mixed cloud estates, hyperscaler heavy |
| Adjacent Kubernetes | OpenShift, Rancher, EKS Anywhere | Multi cloud, cost driven, exit oriented |
Tanzu is no longer the only credible enterprise Kubernetes distribution. Red Hat OpenShift, SUSE Rancher, and AWS EKS Anywhere compete head to head on most workloads. Pure upstream Kubernetes with a third party support contract also covers the standard case.
Tanzu is no longer a captive Kubernetes story. The renewal call should reference three concrete alternatives by name and price.
The per core metric is easier to audit than container or application counts. Broadcom and Vmware audit teams reference the host inventory, the cluster size, and the Tanzu deployment record.
The seven step checklist below moves a Tanzu estate from inherited drift to a defended Broadcom era position.
The roadmap is constrained. Broadcom has not announced a formal deprecation but the investment pattern points to a constrained future. Existing TAS estates should plan for either a Spring on Kubernetes migration, a path to a different platform, or a defended renewal under Tanzu Platform Apps with a clear support runway in writing.
Higher editions of VCF include a Tanzu Kubernetes capability. The exact edition and feature set varies by contract date and license type. The entitlement check is the only reliable way to confirm what an existing VCF agreement covers and where a separate Tanzu Platform line is necessary.
Broadcom narrowed the standalone TKG availability through 2024 and 2025. The primary commercial vehicle is now Tanzu Platform on a per core subscription. Some legacy TKG contracts remain in renewal, and certain partner channels still carry standalone options, but the catalog direction is toward the Platform bundle.
OpenShift is typically priced per node or per core with an annual subscription. On a like for like core basis the two distributions land in a similar range, with OpenShift often slightly lower at scale and Tanzu carrying a price premium where VCF integration matters. The full comparison must include support, migration, and adjacent tooling.
NSX provides east west network segmentation and basic service routing. Tanzu Service Mesh adds Istio based application aware mesh policy across multiple clusters. The two overlap in part but solve different problems. Many estates run NSX for vSphere networking and a separate mesh, either Tanzu Service Mesh or upstream Istio, for application policy.
Tanzu Observability, the former Wavefront product, was renamed Aria Operations for Applications in the Broadcom catalog rationalization. The product itself continues and existing deployments keep working. The buyer side question is whether the observability spend belongs inside the Aria bundle or alongside a different observability platform such as Datadog or New Relic.
A full exit in 12 months is realistic for estates with under 100 clusters and a clear application portfolio. Larger estates plan 18 to 24 months. The migration path matters more than the destination. A staged migration to OpenShift or Rancher with a parallel run window typically lands well. A big bang migration rarely lands well.
Redress runs Tanzu and Broadcom renewal work as a combined VCF, NSX, Aria, and Tanzu engagement. The work covers entitlement checks, three path pricing, and the renewal anchor.
Read the related Vendor Shield, Renewal Program, Benchmark Program, Software Spend Assessment, Benchmarking, about us, management team, locations, and contact pages.
A buyer side playbook for Broadcom era VMware and Tanzu renewals. Includes the VCF entitlement check template, the Tanzu Platform pricing scenarios, the OpenShift and Rancher adjacent comparisons, and the multi product renewal anchor table.
Independent. Buyer side. Built for CIOs, platform engineering leads, and procurement teams carrying VCF, NSX, Aria, and Tanzu lines. No vendor influence. No sales kickback.
Open the white paper in your browser. Corporate email only.
Open the Paper →The Tanzu line in the first Broadcom quote was double the prior year. The entitlement check inside VCF removed a third of it, and the OpenShift quote on the table took another twenty percent off the rest.
We have run 500+ engagements across 11 publishers. Every engagement starts with one conversation.
VCF edition changes, Tanzu Platform metric movement, NSX and Aria pricing examples, OpenShift and Rancher benchmarks, and the wider Broadcom commercial leverage signals across every engagement we run.
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.
