VMware Tanzu licensing after Broadcom — the bundle, the price, the alternatives.

What actually changed.

Broadcom's acquisition of VMware in November 2023 triggered a portfolio simplification that consolidated 168 historical VMware SKUs into roughly a dozen. Within the consolidated portfolio, Tanzu was repackaged. The pre-acquisition Tanzu Standard, Tanzu Advanced and Tanzu for Kubernetes Operations editions were retired or rebadged; the new structure pairs core Kubernetes (TKG / Tanzu Kubernetes Grid) with VMware Cloud Foundation (VCF) as a bundled platform, with Tanzu Application Platform (TAP) and Tanzu Application Service (TAS) sold as discrete bundles.

VCF and the per-core model

VMware Cloud Foundation under Broadcom is licensed per CPU core, with a 16-core-per-CPU minimum that prices materially higher than the pre-acquisition vSphere licensing. Tanzu Kubernetes Grid (TKG) is included in the VCF bundle — a structural change from the pre-acquisition model where TKG was a discrete SKU. For customers running Kubernetes on vSphere, the bundling captures real value; for customers running Kubernetes on bare metal or on public cloud, the included TKG is functionally shelfware.

Tanzu Application Platform — the standalone bundle

Tanzu Application Platform (TAP) — the developer-experience layer built on Cloud Native Computing Foundation projects — is sold as a discrete bundle, priced per developer or per workload depending on the negotiated structure. The pre-acquisition Tanzu Standard SKU is gone; the closest functional successor is the TAP Advanced bundle, which prices materially higher per developer than the legacy SKU. Customers carrying legacy Tanzu Standard licences face a re-licensing event at renewal.

Spring runtime and the open-source position

Spring (the Java framework) remains open source under the Spring Cloud and Spring Boot projects. VMware Tanzu Spring Runtime is the commercially-supported, security-patched Spring distribution; it carries a separate per-application or per-instance licence. Customers running Spring at scale without Tanzu Spring Runtime carry support risk and lose access to back-ported security patches for older Spring versions — a position that became materially more important after the Spring4Shell vulnerability.

Where Broadcom captures the value.

The 16-core minimum and the small-tier squeeze

VCF's 16-core-per-CPU minimum prices into the contract whether or not the actual CPUs reach 16 cores. Customers running Intel CPUs at 8-12 cores per socket carry double the licence count of their physical core count. The squeeze is heaviest at the small-tier — customers running fewer than 100 cores total see VCF prices that often exceed the pre-acquisition vSphere + vSAN + NSX line items combined.

Termed licensing and the perpetual transition

Broadcom retired perpetual VMware licensing entirely in February 2024. Existing perpetual customers may continue to use the software under the original licence, but support renewal is termed-only — typically 1 or 3 year terms — and the support renewal pricing has been materially higher than the pre-acquisition rate. Customers running large perpetual estates face a binary choice: convert to subscription, or run unsupported.

The TAP per-developer metric

Tanzu Application Platform (TAP) is priced per developer per year, with separate SKUs for build, run, and observability components. The per-developer metric counts every named developer with access to the TAP environment — including occasional contributors. Customers running TAP at scale need to scope developer access carefully; the metric grows quickly as platform adoption broadens.

What it costs to leave Tanzu.

The Broadcom-era pricing has pushed a material portion of the Tanzu customer base into evaluating alternatives. The economic case for migration depends on the workload type and the depth of Tanzu-specific dependencies. For pure Kubernetes — TKG clusters running standard CNCF workloads — migration to managed Kubernetes (EKS, AKS, GKE) or self-managed Kubernetes (Rancher, OpenShift) is technically straightforward. For Tanzu Application Platform deployments, the migration is heavier: TAP's developer experience and supply-chain components are not directly portable.

TKG to managed Kubernetes

Tanzu Kubernetes Grid clusters running standard Kubernetes workloads are typically migrable to managed Kubernetes services (EKS, AKS, GKE) within a 60-90 day window. The migration captures cost savings of 40-60% versus the equivalent VCF + TKG licence cost, but introduces operational dependencies on the chosen cloud provider. For customers committed to on-premises Kubernetes, Red Hat OpenShift, Rancher (Suse Rancher), or Mirantis Kubernetes Engine are the credible alternatives.

TAP to upstream CNCF

Tanzu Application Platform is largely composed of CNCF projects (Cartographer, Knative, Contour, Fluxcd, kpack, Carvel) wrapped in a curated developer experience. Replacing TAP with the upstream projects is technically possible but operationally heavy — the value TAP captures is the integration and supply-chain workflow, not the underlying projects. Migrations from TAP typically take 9-12 months and the alternative bundles (Red Hat OpenShift Developer Hub, Backstage with custom plugins) approach feature parity only partially.

What Broadcom is watching for.

Broadcom's audit posture on VMware has been materially more aggressive than the pre-acquisition VMware audit programme. Audits we have seen since 2024 focus on three areas: per-core counting accuracy (especially across multi-socket and high-density servers), perpetual-to-subscription transition disputes, and Tanzu-specific over-deployment where the licence allocation is smaller than the deployed Kubernetes workload. The audit cycle from notice to settlement has compressed materially under Broadcom.

The Symantec audit playbook

Industry observers have noted that Broadcom's VMware audit team draws on the playbook the company used at Symantec post-acquisition: aggressive measurement, narrow defence windows, and settlement positions that emphasise long-term subscription commitment over back-bill cash. Customers managing a Broadcom-era VMware audit should expect a settlement structure that pushes a 3-year VCF subscription as the resolution path, rather than the pure compliance back-bill the pre-acquisition audit programme typically pursued.

Six levers that hold in a Broadcom-era Tanzu negotiation.

1. Migration credibility. Demonstrated migration planning to alternative Kubernetes or PaaS platforms is the single most effective lever; Broadcom's renewal posture softens materially when leverage is real.
2. Core-count audit. Validating per-core counts against actual deployment removes the over-counting that follows the 16-core minimum.
3. TAP scope narrowing. Restricting TAP licensing to the development teams that actually use it — not the whole engineering organisation — captures meaningful savings.
4. Multi-year discount trade. Broadcom's discount ladder rewards 3-year commitments materially; the trade is term-flexibility against price.
5. Subscription transition timing. Where perpetual licences still have support remaining, deferring the subscription transition to the support expiry preserves leverage.
6. Spring Runtime scope. Limiting Tanzu Spring Runtime to production applications only — not all Spring workloads — captures developer-tier savings.