Licensing is the first question in almost every VMware Cloud Foundation conversation today, and often the most confusing one. The good news is that the model itself is simple once you know the rules. In this post, I’ll explain how VCF 9 is licensed, how to count the cores you need, how much vSAN capacity is included, and the mistakes I see most often.
The Basics: Per-Core Subscription
- VCF is sold as a subscription, licensed per physical CPU core in every ESX host that runs it.
- Minimum of 16 cores per CPU. Every populated socket is licensed for at least 16 cores, even if the processor has fewer.
- VMware vSphere Foundation (VVF), the smaller bundle, uses the same per-core metric and the same 16-core minimum.
- Hyper-threads don’t count; only physical cores do.
How to Count Cores
Count per CPU, then add everything up:
Cores per host = number of CPUs × max(physical cores per CPU, 16)
| Hosts | CPUs per host | Cores per CPU | Licensed cores per CPU | Total cores to license |
|---|---|---|---|---|
| 4 | 2 | 12 | 16 (minimum applies) | 128 |
| 4 | 2 | 32 | 32 | 256 |
| 3 | 1 | 8 | 16 (minimum applies) | 48 |
Notice the first row: hosts with 12-core CPUs pay for 16 cores per CPU. With the minimum in place, low-core-count CPUs are poor value for VCF. When you buy new hardware, CPUs with 16 or more cores make the most of what you pay for.
For larger estates, Broadcom provides a License Counting PowerCLI tool that collects core and vSAN capacity needs for every host connected to a vCenter. It’s attached to Broadcom KB 313548.
vSAN Capacity Is Included
Each licensed core comes with a vSAN entitlement:
- VCF: 1 TiB of vSAN per licensed core, counted against raw capacity and pooled across your hosts.
- VVF: 0.25 TiB of vSAN per licensed core.
So the 128-core example above includes 128 TiB of raw vSAN capacity with VCF. If your clusters need more raw capacity than that, you buy additional vSAN capacity on top. Remember it’s raw, not usable: after RAID protection and reserves, usable space is much lower. The free vSAN Capacity Calculator shows you the raw capacity you’ll actually deploy.
How Licenses Are Applied in VCF 9
- No more 25-character keys. From VCF 9, the licence is a subscription file that you generate on the Broadcom portal and apply through VCF Operations.
- In VCF 9.1, licensing runs on a separate VCF License Server appliance, deployed during the VCF Operations upgrade. The day-to-day workflow stays the same.
- Moving from VCF 9.0 to 9.1 needs no new licence, as long as your subscription covers the cores you run.
- Moving from VCF 5.x: the old keys don’t carry forward. Components run in evaluation mode during the upgrade and are then relicensed in VCF Operations with new subscription files.
- Perpetual licences must be converted to a subscription before you upgrade. Start this early; the commercial process often takes longer than the technical work.
Common Mistakes
- Forgetting the 16-core minimum on small CPUs, which inflates the count.
- Treating the vSAN entitlement as usable capacity. It’s measured against raw TiB.
- Counting only production clusters. Every host running VCF needs licensing, including management domain and DR hosts. Check your agreement for how standby hosts are treated.
- Assuming every add-on is included. Some advanced services are sold separately; confirm what your subscription covers.
- Leaving the licence renewal to the last month. Track the subscription end date in VCF Operations.
Quick Checklist
- List every host: CPUs and physical cores per CPU.
- Apply the 16-core minimum per CPU and total the cores.
- Compare your raw vSAN capacity with the included TiB.
- Confirm which add-ons and advanced services you need.
- Generate the licence file and apply it in VCF Operations.
Licensing terms and bundles can change, so always confirm the details for your agreement with Broadcom or your partner. If you have a counting question for your own environment, leave it in the comments.

