VMware after Broadcom: what changed for your costs
What to check in your VMware estate, and the options companies are weighing.
Since Broadcom completed its acquisition of VMware, the way VMware is sold has changed significantly. For many companies with large virtualised estates, renewal time has become a moment for serious cost review.
What changed
In broad terms, VMware moved from a long menu of individual products and perpetual licences to:
- Subscriptions instead of perpetual licences
- Bundled offerings that group products together, instead of buying each one separately
- Per-core licensing, so cost follows the number of CPU cores you run on
The exact impact depends heavily on your setup and contract. For some companies little changes. For others, especially those with many cores, older hardware or only a few products in use, renewals look very different from before.
What to check before your renewal
- Count your cores accurately. Since cost follows cores, know exactly how many you license, per cluster and per host.
- Check host utilisation. Underused hosts cost the same per core as busy ones. Consolidation often reduces the licensable footprint.
- Map products to real use. Bundles may include products you don’t use, or miss one you rely on. Know which features you actually need.
- Look at hardware age. Older servers with many cores but low performance can be expensive to license. Sometimes a hardware refresh pays for itself through licensing alone.
- Model the alternatives. Moving some workloads to public cloud, to another platform, or simply consolidating clusters are all options. Each has a cost and a risk.
Where FinOps helps
This is a classic FinOps question: a large, recurring cost, a decision with many options, and engineering and finance both involved. Putting VMware, public cloud and the rest of your infrastructure in one cost view makes the trade-offs clear, before the renewal date makes the decision for you.