Call Us (877) 740-5028
Call Us (877) 740-5028
Call Us (877) 740-5028
Table of Contents
Broadcom’s acquisition of VMware reshaped how thousands of organizations buy and manage infrastructure software. Subscription-only models replaced perpetual licenses, over 160 SKUs collapsed into a handful of bundles, and per-core pricing became the new standard. For many IT leaders and procurement teams, navigating VMware licensing suddenly felt like learning a new language under pressure.
The core counts, minimum thresholds, and bundle inclusions can feel overwhelming, especially when the math has real budget consequences. A miscounted host or an overlooked minimum can mean paying for capacity you never planned to buy.
This blog breaks down how VMware licensing works today: The 16-core and 72-core minimum rules, what’s inside each bundle, how vSAN fits in, and how to calculate your requirements with real examples. The goal is to make the calculations approachable so that decisions are grounded in accurate numbers.
All VMware licensing now runs on a per-core subscription model. That means every physical core on every licensed host counts, and two mandatory minimum rules shape the entire calculation.
According to Broadcom, every CPU on an ESXi host must be licensed for a minimum of 16 cores, even when the physical core count is lower. So, if a server has two 8-core CPUs (16 actual cores), the calculation still treats each socket as 16 cores, producing a minimum of 32 licensed cores for that host alone.
A simple way to see this is: The 16-core rule is applied per socket, not per server. A 10-core CPU does not save you anything on paper. You still license it as 16.
Starting April 10, 2025, Broadcom introduced an additional threshold: Every VMware product purchase requires a minimum of 72 cores per license instance. This applies to both VCF and VVF and sits on top of the 16-core-per-CPU rule. Importantly, you cannot combine core counts across different products to reach that threshold. For example, 40 VCF cores and 32 VVF cores do not satisfy a compliant 72 for either product.
For small or edge deployments, this change hits hard. An organization running two hosts with a single 8-core socket each would have 32 physical cores, but still must license 72, more than double what they actually run. That gap between physical hardware and licensing minimums is where costs jump unexpectedly.
Broadcom consolidated over 160 VMware SKUs into two primary bundle options. Choosing the right one affects both what you pay and what capabilities you get.
VVF includes vSphere Enterprise Plus, Tanzu Kubernetes Grid (one supervisor cluster), Aria Suite Standard, and 250 GiB of vSAN capacity per licensed core. For organizations focused on server consolidation, basic virtualization, or edge and branch locations, VVF covers the essentials without bundling tools they will not use.
The vSAN entitlement in VVF is worth noting: Each VVF core purchased carries 0.25 TiB of vSAN entitlement, rounded up to the next TiB. For storage-light workloads, this is often more than enough. For heavier storage needs, additional vSAN TiB licenses are available as an add-on.
VCF includes everything in VVF plus NSX networking, Aria Suite Enterprise, and 1 TiB of vSAN capacity per core. That four-to-one improvement in vSAN entitlement is significant for data-intensive environments. VCF is built for organizations running a full-stack private cloud, production Kubernetes workloads, or regulated industries that need tighter operational controls.
For teams already investing in NSX or planning to use Tanzu at scale, VCF often delivers better per-core value than licensing the same components separately. The included tooling is there either way. The question is whether you use it.
vSAN licensing now follows a separate path, which can change how teams estimate overall platform cost. Starting November 22, 2024, vSAN is no longer enabled automatically by a VCF or VVF solution key. For purchases made on or after that date, Broadcom issues a distinct vSAN license key for storage virtualization.
In practice, the solution key activates vSphere, NSX, Aria, and the other bundled components, but storage virtualization requires an additional activation step with the dedicated vSAN key. For teams who assumed vSAN remained fully automatic after bundle activation, this is a gap that can surface during an audit or a fresh deployment.
The storage entitlements are still included in VCF and VVF. You do not purchase them separately. But you do need to assign the separate key. Overlooking this step during deployment or renewal planning can stall projects and complicate compliance reviews, which is important for accurate total cost calculations.
Consider a 2-host cluster with 2 CPUs per host and 8 physical cores per CPU. That gives you 32 physical cores in total. But VMware licensing applies a 16-core minimum per CPU, so each of the 4 CPUs is counted as 16 cores, bringing the licensed total to 64 cores.
If the 72-core minimum also applies, the environment must still be licensed at 72 cores. In other words, a cluster with 32 physical cores can trigger a 72-core purchase floor, which is where budgeting surprises often begin.
Now consider a larger environment: 8 hosts, 2 CPUs each, 24 cores per CPU. Each host has 48 physical cores; the cluster total is 384. Because every socket meets or exceeds the 16-core minimum, no rounding occurs. The 72-core minimum is far exceeded. The required license count is 384 cores, and the math scales predictably from there.
In contrast to the small deployment, larger environments are rarely caught off guard by the minimums. The risk there tends to be undercounting physical cores after hardware refreshes or cluster expansions. Those changes can quietly push requirements higher.
One of the more practical improvements in recent VMware licensing terms is license portability. The portability entitlement applies to new end-user licenses for VCF version 5.1 and above purchased after December 13, 2023. A qualifying subscription can run on-premises, with authorized VMware Cloud Service Providers, or in supported public cloud environments.
On the other hand, licenses obtained through a cloud service provider rather than directly from Broadcom or an authorized reseller do not carry the portability entitlement. That distinction matters for hybrid strategies and disaster recovery planning. An organization that wants to move workloads between on-prem and a provider without buying double capacity needs to confirm how the original license was purchased.
For teams navigating migrations or distributed environments, portability removes a significant cost concern. You no longer pay for the same workload twice during a transition period, as long as the license qualifies. Avoids double-paying for workload capacity during migrations or DR, which directly supports leaner infrastructure budgets.
Accurate core counting, understanding what’s in each bundle, and knowing where the minimums apply are the three areas that most often determine whether VMware licensing stays within budget or runs over. The 16-core-per-CPU rule, the 72-core minimum per license instance, and the separate vSAN key requirement all carry financial weight that is easy to underestimate without hands-on familiarity with how Broadcom’s rules interact.
As a Broadcom Pinnacle Partner, OTAVA helps clients calculate compliant core counts, navigate VCF vs VVF bundle decisions, and optimize total VMware licensing costs across their environments. Whether you are planning a new deployment, approaching a renewal, or trying to model what your next budget cycle looks like, our team brings the technical depth to work through the details with you.Schedule a licensing assessment with our team. We will review your environment, model your core counts, apply the minimums, and help you choose the right bundle for your business needs, so you are not paying for capacity you do not need or missing coverage you do.
