HCX, Tanzu, and Aria under Broadcom. The licensing reset.

Broadcom folded HCX, Tanzu, and Aria into the VCF and VVF subscription bundles, so the question is no longer what each tool costs but which bundle you are forced into.

How are HCX, Tanzu, and Aria licensed under Broadcom now?

HCX, Tanzu, and Aria are licensed only as components of VMware Cloud Foundation or vSphere Foundation subscriptions, billed per core. Broadcom describes the bundle composition on the VMware Cloud Foundation product page and the vSphere Foundation page.

The practical effect is that you cannot buy the tool you need without the suite around it. Pricing conversations are therefore core count conversations, not product conversations.

What happened to existing perpetual licenses?

Perpetual vRealize, Tanzu, and HCX entitlements keep working but cannot renew support as standalone items. At support expiry the only path Broadcom offers is a bundle subscription priced per core.

How do you match the bundle to what you actually deploy?

Start with a deployment inventory, not the quote. Map every HCX site pairing, Tanzu cluster, and Aria module in production, then compare that list to what the proposed bundle carries.

• HCX: count active site pairs and migration waves still planned. Finished migrations need no HCX renewal.
• Tanzu: count Kubernetes clusters actually scheduled on Tanzu runtime, not clusters on other distributions.
• Aria: list modules with active users in the last 90 days. Dashboards nobody opens are not usage.

Which estates should consider VVF instead of VCF?

Estates that run plain vSphere with basic monitoring fit VVF. The VCF premium only pays back when HCX migrations, Tanzu workloads, or full Aria automation are real and current.

What are the negotiation levers on a VCF or VVF renewal?

The levers are core count, term length, and credible exit motion. Broadcom prices against your switching cost, so every lever works by lowering that perceived cost.

1. Re count cores against current hosts, not the legacy entitlement. Decommissioned clusters come out.
2. Price both VCF and VVF, and force the delta to be justified component by component.
3. Run a migration assessment on a visible subset of workloads before the renewal window opens.
4. Ask for HCX terms that survive a partial exit, since you need it to leave.

Broadcom's own support portal documentation governs entitlement conversion, so pull your conversion records before accepting the quoted baseline.

How does HCX change your exit and migration options?

HCX cuts both ways. It is the tool Broadcom includes to move workloads into VCF estates, and it is the same tool that moves them out to alternative hypervisors or cloud.

Treat HCX entitlements as strategic. A renewal that lapses HCX while a migration is half done strands the program and hands leverage back to the vendor.

What should a migration safety clause cover?

• Term: HCX access for the full migration window, not just the subscription term.
• Scope: site pairings to third party destinations, not only VMware endpoints.
• Data: export of Aria operational history before the entitlement closes.

Where the common advice on Broadcom VMware bundles is wrong

The standard reseller advice is to take VCF because it is the strategic bundle and the per core delta looks small against the suite value. We disagree. In roughly 20 of the 30 plus Broadcom renewals we benchmarked, the VCF components beyond plain vSphere and basic operations were deployed in under a third of the estate, which means the suite value was theoretical while the core charge was real. The buyer side move is to price VVF first, force Broadcom to justify the VCF delta component by component against your deployment inventory, and keep HCX terms that protect the exit path. The bundle should follow usage, not the other way around.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Inventory HCX site pairs, Tanzu clusters, and Aria modules in active use.
2. Pull entitlement conversion records from the Broadcom support portal.
3. Re count cores against current hosts and remove decommissioned clusters.
4. Price VVF and VCF side by side and demand a component level justification.
5. Add HCX and data export terms that survive a partial exit.
6. Set a renewal calendar entry 9 months before expiry for the next cycle.

White Paper · Broadcom / VMware

Broadcom VMware Renewal Survival 2026

The 2026 buyer side reference on Broadcom VMware renewals. Read it free.

Read the white paper

Frequently asked questions

Can I still buy HCX, Tanzu, or Aria as standalone products?

No. Broadcom sells them only inside VMware Cloud Foundation or vSphere Foundation subscriptions, billed per core. Standalone SKUs ended with the post acquisition portfolio simplification, and standalone support renewals are no longer quoted.

What is the licensing difference between VCF and VVF for these tools?

VCF includes HCX Enterprise, the Tanzu Kubernetes runtime, and the full Aria suite. VVF carries only an Aria Operations slice. If you need migration tooling or Kubernetes runtime entitlements, Broadcom will steer you to VCF.

Do my perpetual vRealize or Tanzu licenses still work?

Yes, perpetual licenses keep running, but support cannot renew standalone. At support expiry the upgrade path is a per core bundle subscription, so plan the conversion before the support date forces it.

How is the per core charge calculated?

Bundles bill per physical core with a 16 core minimum per CPU. Small hosts with fewer cores still pay the minimum, which makes host consolidation a direct licensing lever.

Is Tanzu worth keeping if we run Kubernetes elsewhere?

Usually not as a paid driver of VCF. If your clusters run on other distributions, Tanzu entitlements are shelfware inside the bundle, and that is an argument for VVF pricing in the negotiation.

Why does HCX matter in a renewal negotiation?

HCX is both the on ramp and the off ramp. It migrates workloads into VMware estates and out to alternatives, so keeping HCX access through your migration window preserves the exit leverage that moves Broadcom pricing.