VMware VCF Licensing Explained: Per-Core Minimums and What They Mean for Your Budget

Broadcom's per-core licensing includes two minimums that can multiply costs for organizations renewing or purchasing VMware subscriptions. Every physical CPU socket must be licensed for at least 16 cores, and new orders carry a 72-core minimum. Together these can add paid cores without changing hardware. In small environments, the added cores can turn into five-figure subscription increases depending on bundle, term, and discount.

This replaces the old per-socket model entirely. Perpetual VMware licenses with SnS (Support and Subscription) renewals no longer exist. Everything is subscription now, priced per core, with minimums that can make small environments pay for capacity they do not have.

VCF vs. VVF: what each bundle includes

VMware now sells two main subscription bundles. Both are per-core, with no perpetual options and no per-VM metering. All physical cores on all ESXi hosts running VMware software must be licensed. There is no exclusion for test or development servers.

VCF (VMware Cloud Foundation) is the full-stack bundle: vSphere Enterprise Plus, vSAN Enterprise, NSX, Aria Operations, Aria Automation, HCX, and vSphere Kubernetes Service (VKS). VVF (vSphere Foundation) is the smaller bundle: vSphere Enterprise Plus, vSAN Enterprise, and Aria Operations Standard. No NSX, no Automation, no HCX, and a limited Tanzu tier.

A third option exists: vSphere Standard. It is per-core hypervisor licensing only, with no vSAN and no Aria. Organizations running 2- to 3-host environments that need only ESXi and vCenter may find it through their channel partner. Broadcom does not prominently advertise it.

VCF list price is $350 per core per year. Broadcom positioned this as a 50% reduction from the initial post-acquisition pricing of $700 per core per year. VVF lists at $135 per core per year on average, ranging from $150 for 3-year terms to $190 for 1-year MSRP. GoVendorFree reports North American VCF quotes around $420 to $480 per core per year, and UK quotes around £380 to £440 per core per year, though those figures may include partner markup, support, or taxes. Confirm whether a quote includes support, VAT, and partner margin before comparing.

The vSAN storage allocation is where the bundles split. VCF includes 1 TiB of vSAN capacity per core. VVF includes 0.25 TiB (250 GiB) per core, increased from 100 GiB as of November 2024 (vSphere 8.0 U3e). On a 192-core environment, that is 192 TiB versus 48 TiB. Storage-heavy workloads on VVF will require additional vSAN entitlement purchases. vSAN no longer activates automatically through the VCF or VVF solution key as of November 2024, per OTAVA and Broadcom documentation. Confirm current entitlement details with an account rep.

For many VMware estates, NSX is the clearest functional separator between VCF and VVF. VCF includes full NSX with network virtualization, micro-segmentation, and distributed firewall. VVF includes zero NSX. Within Broadcom's current VMware bundles, VCF is the bundle that includes NSX. If a security team requires micro-segmentation, VCF is the path.

VCF also includes Aria Suite (Operations, Automation, and Logs) versus Aria Operations Standard in VVF. HCX, the migration tool for moving VMs between vCenters or cloud environments, is VCF-only. The vSphere Kubernetes Service (VKS) entitlement (renamed from Tanzu Kubernetes Grid in VCF 9) is broader in VCF than the limited Tanzu Standard tier in VVF.

The 16-core per CPU minimum

Every populated physical CPU socket must be licensed for at least 16 cores, regardless of how many physical cores the CPU actually has. This is documented in Broadcom KB 313548, updated June 17, 2026.

The KB gives this example: a server with two CPUs that each have 8 physical cores. A reader might expect to license 16 cores total. The customer must instead purchase 32 cores, because the minimum subscription capacity is 16 cores per CPU. The calculation for each host is: take the higher of actual cores per CPU or 16, multiply by the number of populated sockets, then sum across all hosts.

Count physical cores, not threads or hyperthreads. A 16-core CPU with hyperthreading enabled shows 32 logical processors to the OS, but the license count is 16 cores.

For a dual-socket host with 8-core CPUs, the licensed core count doubles from 16 to 32. With 6-core CPUs, it rises from 12 to 32. Older hardware magnifies the gap between physical cores and licensed cores.

To check current core counts via PowerCLI:

# Audit all ESXi hosts connected to vCenter
Get-VMHost | Select-Object Name,
    @{N='Sockets';E={$_.ExtensionData.Hardware.CpuInfo.NumCpuPackages}},
    @{N='CoresPerSocket';E={[int]($_.ExtensionData.Hardware.CpuInfo.NumCpuCores / $_.ExtensionData.Hardware.CpuInfo.NumCpuPackages)}}

For a full audit that applies the 16-core minimum and flags the 72-core order minimum:

# Full audit: licensed core count with 16-core minimum applied
Get-VMHost | ForEach-Object {
    $sockets = $_.ExtensionData.Hardware.CpuInfo.NumCpuPackages
    $coresPerSocket = $_.ExtensionData.Hardware.CpuInfo.NumCpuCores / $sockets
    $licensedCores = ([math]::Max($coresPerSocket, 16)) * $sockets
    [PSCustomObject]@{
        Host = $_.Name
        Sockets = $sockets
        PhysicalCores = $coresPerSocket * $sockets
        LicensedCores = $licensedCores
    }
} | Format-Table -AutoSize

# Sum total and check 72-core minimum
$total = Get-VMHost | ForEach-Object {
    $sockets = $_.ExtensionData.Hardware.CpuInfo.NumCpuPackages
    $coresPerSocket = $_.ExtensionData.Hardware.CpuInfo.NumCpuCores / $sockets
    ([math]::Max($coresPerSocket, 16)) * $sockets
} | Measure-Object -Sum
Write-Host "Total licensed cores: $($total.Sum)"
Write-Host "72-core minimum applies: $(if ($total.Sum -lt 72) { 'YES - must purchase 72' } else { 'No' })"

Without vCenter, check each host directly: Host > Hardware > CPU Processors, and look at the Cores per socket value.

The 72-core order minimum

Broadcom introduced a 72-core minimum purchase per order in April 2025. This applies to VCF, VVF, and vSphere Standard. If the total licensed cores across all servers is less than 72, the customer must purchase 72 cores worth of licensing anyway.

Reporting from StarWind (November 2025) suggested the minimum was reversed after industry backlash. That is partially wrong. The minimum still applies to new orders, subscription transitions, and tier changes. What changed is that Broadcom allows smaller commitments for renewals under certain conditions, typically when the customer signs a multi-year term.

For environments below 72 licensed cores, the order minimum can dominate the renewal math. A 3-host cluster with dual 16-core CPUs (96 cores) clears it. A 2-host cluster with the same CPUs (64 cores) does not, and must license 72 cores despite having 64.

Several reseller and customer reports describe late-renewal penalties around 20% when subscriptions lapse before renewal. This is separate from the core minimums but compounds the cost pressure on small shops deciding whether to renew or migrate.

Calculating the actual cost

Use this calculation:

1. Count physical cores per CPU on each host (not threads)
2. Apply the 16-core minimum per CPU (take the higher of actual or 16)
3. Multiply by the number of populated sockets per host
4. Sum across all hosts
5. Apply the 72-core order minimum if the total is below 72
6. Multiply by the per-core rate ($350 list for VCF, $135 for VVF)
7. Multiply by the number of years in the subscription term

Worked example: 3 hosts, each dual-socket 32-core Intel Xeon (64 cores per host, 192 total). At VCF list price: $350 × 192 × 3 years = $201,600. At VVF: $135 × 192 × 3 years = $77,760. The $123,840 delta buys NSX, Aria Automation, HCX, a broader Tanzu entitlement, and a larger included vSAN allocation.

CPU density changes the licensing bill. A server with two 8-core CPUs (16 physical cores) must license 32 cores because of the 16-core-per-socket minimum. A server with one 16-core CPU licenses only 16 cores. Same total physical cores, double the licensing cost. When buying server hardware before a renewal, compare socket count and cores per socket before purchase. Do not choose CPUs based only on acquisition price.

What customers are paying

Public reports suggest many customers negotiate below list, while some reseller quotes land above Broadcom's list price after markup.

Public forum anecdotes are not a price sheet, but they show the spread customers are seeing. A Reddit user on r/vmware negotiated $165 per core per year on a three-year VCF deal in December 2025. That is 53% off list, and it took months of negotiation. Another user with 256 cores and 448 TB of vSAN saw an 80% increase on a VVF renewal in April 2026. A Spiceworks user reported a renewal going from approximately $1,100 per socket per year to a minimum of $10,000 per year.

In the AT&T/Broadcom contract dispute, AT&T alleged a 1,050% price increase. That is a legal dispute between two large enterprises, not a typical customer renewal, but it illustrates the direction of pricing under the new model.

Across the Reddit, Spiceworks, and GoVendorFree reports cited above, VCF runs roughly $165 to $480 per core per year depending on negotiation leverage and region. VVF runs roughly $100 to $190 per core per year. The sample is not a formal market survey.

Reported negotiation levers include three-year terms, reducing core count before renewal by consolidating VMs and decommissioning hosts, showing a credible migration plan, and working through a Broadcom partner instead of buying direct. Some public customer reports describe support cost increases of 3x to 5x over prior SnS pricing. Treat that as anecdotal unless a reseller quote confirms it.

Who should pay for VCF

VCF makes sense if the environment needs NSX, is building a private cloud platform, uses Aria Automation for provisioning, needs HCX for migration, or runs substantial Kubernetes workloads through Tanzu.

VVF makes sense if the environment needs vSphere and vSAN but not NSX, and does not use Aria Automation or HCX.

Below 72 licensed cores, the order minimum can make VCF and VVF cost more than the features are worth unless the environment specifically needs vSAN, NSX, Aria, or Broadcom support. In that scenario, Proxmox VE, Hyper-V, or Nutanix AHV are worth evaluating. For a home lab or small test environment, a VMUG Advantage membership at $200/year provides lab access to the full suite without per-core licensing.