VMware Tanzu after Broadcom: the licensing playbook

Since Broadcom's acquisition of VMware, every Tanzu-based enterprise we work with has had the same conversation internally: do we stay, do we migrate, do we renegotiate? The answer is almost always 'renegotiate first, decide on migration with real numbers' — and yet most customers jump to the migration conversation immediately. Here is the playbook we have been using with customers over the past twelve months.

Step 1: model the licensing options honestly

Broadcom now bundles VCF in ways that make small estates more expensive and large estates potentially cheaper per-workload. The only way to know which side of that line you are on is to model your actual current-state consumption against both the old and new pricing structures. ANKASOFT does this as a paid week-long exercise because it is the one piece of work that has to be objective — your renewal rep will happily model it for you but with a finger on the scale.

Step 2: separate the platform conversation from the workload conversation

Many teams conflate two questions: 'should we stay on vSphere?' and 'should we stay on TKG / TAP?' They are separate decisions. vSphere is deeply embedded in most estates we see — the cost of leaving is typically three to five years of ops rework. Tanzu Application Platform, on the other hand, has competitors whose migration path is months, not years.

We tell customers to answer the vSphere question on a five-year horizon and the TAP question on a one-to-two-year horizon. Those are the honest time frames.

Step 3: negotiate with the real alternative on the table

The highest-leverage negotiation move is walking into the renegotiation with a concrete migration plan — not because you are likely to execute it immediately, but because your rep is more persuadable when they know you can. We build these migration plans as part of engagement scope. They are useful artefacts even if you never run the migration.

The worst Tanzu decisions get made when the licence renewal is inside 90 days and nobody has modelled the alternatives. Start the modelling eighteen months out.

Step 4: plan the air-gapped and Day-2 posture separately

Several of our regulated-sector customers run Tanzu in air-gapped environments. Broadcom's licensing changes and support terms interact differently with air-gapped installations than with connected ones — and the Day-2 operational burden depends heavily on what you licensed for. Walk through both with someone who has operated them in production.

Where this lands

ANKASOFT is a Broadcom-authorised delivery partner for VMware Tanzu and VCF. We have run the renegotiation-first playbook with clients across automotive, banking and insurance in the past twelve months. The engagement is usually four to eight weeks and ends with either a much better renewal or a credible, sized migration plan. Both are better than the 'sign the renewal at list price' default.