A two-minute read.
What Broadcom's terms require
Broadcom publishes the terms for VMware Cloud Foundation, its main private cloud product, in a document called the Specific Program Documentation. The June 2026 edition sets out how the software is licensed and what a customer has to do to keep it working [1].
Two of its rules are about money. The software is licensed per core, with a minimum of 16 cores per processor. Every core on the server has to be licensed, including cores deactivated in the Basic Input/Output System (BIOS). Switching cores off does not reduce what you owe [1].
A reporting clause with an operational penalty
The third rule has nothing to do with money. A customer has to send Broadcom a compliance report 180 days after the license is registered, and every 180 days after that. The document states that failing to send a timely, unaltered report will result in features of the management plane being degraded or blocked, and support entitlements suspended [1]. The management plane is the console your team uses to run the estate.
Why a better rate offers no protection here
The penalty for a paperwork miss therefore lands in operations. There is no invoice, no audit and no conversation to have. Writing in February 2026, Fredrik Filipsson of Redress Compliance set out a careful playbook for these contracts [2]. It covers auditing your core counts, scoping the bundles cluster by cluster, pricing your exit to move the discount band, and banking clauses for the next renewal. It is good advice, and all of it is aimed at the rate. The rate is the part of this contract a discount can fix. The reporting clause is the part it cannot. A hard-won saving on cores buys you nothing on the morning your console is degraded because a report went unsent.
Who is exposed, and who can stop worrying
Plenty of organizations will never face this risk. If a managed service provider registered your licenses and files on your behalf, the obligation sits with them and nothing goes in your calendar. The question is whether you know that or assume it. Ask for confirmation in writing and the matter closes in a morning.
Where it does bite, it bites in one shape: a large estate kept on-premise and run by a small platform team. That team is measured on uptime, and this is the rare clause that threatens uptime with no financial warning in front of it. Nothing gets more expensive first. The console simply does less.
Three things, and none of them takes longer than a morning. Find out who registered your VMware licenses. Confirm in writing whether your partner sends the compliance report or you do. Then count the cores your BIOS has switched off, because you are paying for every one of them.
An estate that misses the date will hear about it first from its own console.
References
[1] Broadcom, VMware Cloud Foundation Specific Program Documentation, June 2026.
https://ftpdocs.broadcom.com/cadocs/0/VCF_SPD_June2026.pdf
[2] Fredrik Filipsson, Broadcom VMware licensing changes, explained. What changed and what it costs in 2026, Redress Compliance, February 2026.
https://redresscompliance.com/broadcom-vmware-licensing-changes-explained
Sources
Ready to Translate Strategic Vision into Velocity?
Partner with Apto Group's senior advisors to execute high-impact priorities across Asia Pacific.