TAS and TKG: What You Are Actually Licensing
The Tanzu TAS vs TKG comparison starts with a basic distinction that Broadcom's bundling tends to blur. Tanzu Kubernetes Grid (TKG) is the Kubernetes runtime — the conformant cluster platform that runs your containers. Tanzu Application Service (TAS), the former Pivotal Cloud Foundry, is a higher-level application platform: developers push source code with a single command and the platform builds, deploys, and runs it without touching Kubernetes primitives. TKG gives you Kubernetes; TAS gives you an opinionated PaaS that sits above it.
That difference now drives the licensing. Following the mid-2024 restructuring, the 2025 catalogue folded TAS, TKG, and Tanzu Mission Control into a consolidated Tanzu Platform, and the standalone TAS per-core SKUs reached End of Availability. TKG capability is bundled inside VMware Cloud Foundation, while TAS remains a premium add-on licensed separately above VCF. Most VCF subscribers therefore already hold the Kubernetes runtime; it is the application platform that carries the extra cost. The full landscape, including exit options, is covered in our guide to Tanzu licensing and Kubernetes alternatives.
The Per-Core Repricing Under Broadcom
Broadcom reprices Tanzu on CPU cores allocated to Kubernetes or application capacity, replacing the older application-count and node-count models from the VMware era. The per-core Tanzu Platform subscription is now the primary commercial vehicle. The metric change matters more than the headline rate: enterprises that sized Tanzu on the number of applications or nodes are repricing on cores, and the result is uneven — some estates land lower, but many land materially higher, particularly dense deployments running many cores per application.
Broadcom's preferred motion is to include Tanzu inside the VCF bundle and price standalone Tanzu so the bundle looks attractive by comparison. The same per-core consolidation we see across the wider VMware and Broadcom licensing portfolio applies here. Specific per-core figures are quote-based rather than published, which is precisely why a core-by-core model is essential before accepting any renewal quote.
Tanzu TAS vs TKG: Side by Side
| Dimension | Tanzu Application Service (TAS) | Tanzu Kubernetes Grid (TKG) |
|---|---|---|
| What it is | Cloud Foundry application platform (PaaS) | Conformant Kubernetes runtime |
| Developer model | Source push (cf push), no K8s exposure | Containers, manifests, K8s primitives |
| Licensing today | Premium add-on above VCF, per-core | Bundled inside VCF |
| Standalone SKU status | Per-core SKUs reached End of Availability | Consolidated into Tanzu Platform / VCF |
| Cost exposure | Add-on can rival the VCF base itself | Largely sunk if you already run VCF |
| Credible alternative | OpenShift, upstream K8s + buildpacks | Upstream Kubernetes, managed K8s |
For organisations running large TAS deployments, the add-on cost can rival the VCF base itself — which is exactly the threshold at which OpenShift and upstream Kubernetes become genuinely competitive on total cost. The question is not whether Tanzu works; it is whether the application-platform premium still earns its keep against your real usage.
Which to Keep, Which to Question
If you run VMware Cloud Foundation, treat TKG as largely sunk cost — you are already paying for the Kubernetes runtime inside the bundle, so the marginal decision is how much of it you actually consume, not whether to license it separately. The harder call is TAS. The application-platform premium is justified only where the developer-velocity gains are real and measured: faster onboarding, lower operational headcount, and fewer platform engineers maintaining bespoke Kubernetes tooling. Vendor-cited outcomes such as a 142% return on investment and around $2M in average infrastructure savings (per ESG and Forrester studies) describe best-case deployments, not a default — validate them against your own utilisation before renewing at the new per-core rate.
Where TAS usage is thin or concentrated in a few teams, the total-cost case for an alternative strengthens quickly. This is the same open-source versus commercial total cost trade-off that applies across the container platform market — upstream Kubernetes carries no licence fee but shifts cost into operations and support. The right answer depends on the size and maturity of your platform team, not on the vendor's ROI deck. Our VMware and Broadcom vendor hub tracks how these decisions are playing out across enterprise estates.
Negotiating the Tanzu Renewal
The strongest lever in any Tanzu renewal is a credible, documented migration assessment. Broadcom prices very differently against a buyer with a real exit path — when a costed OpenShift or upstream-Kubernetes plan is on the table, the per-core premium becomes negotiable rather than fixed. The assessment must be genuine: scope, timeline, and a target architecture that withstands the account team's attempt to dismiss it as a bluff. Separate the TKG-in-VCF conversation from the TAS add-on so Broadcom cannot use bundle economics to obscure what the application platform actually costs you.
Time the renewal to your leverage, not Broadcom's quarter-end, and insist on per-core transparency in the quote so you can model the bundle against buying components separately. For the full survival playbook on Broadcom pricing tactics, download the VMware Broadcom Survival Guide, and for direct support shaping the renewal, request a confidential briefing. We run these as standard software licensing negotiations on behalf of buyers.