Home → Calculating Real VMware Costs: A Complete Breakdown of Broadcom's Subscription Pricing
Licensing & Cost

Calculating Real VMware Costs: A Complete Breakdown of Broadcom's Subscription Pricing

March 30, 2026 · 11 min read

Calculating Real VMware Costs: A Complete Breakdown of Broadcom's Subscription Pricing

Broadcom's acquisition of VMware in late 2023 didn't just change the vendor — it fundamentally rewired how VMware environments are priced. Administrators who had spent years working with predictable per-socket perpetual licenses suddenly faced subscription-only bundles, a shift to per-core counting, and cost increases that community reports place at 150% to over 1,000% for many organizations.

This isn't a guide about whether the new model is fair. It's a guide to surviving it. You need to understand exactly how Broadcom counts cores, what VCF versus VVF actually includes, where the hidden costs live, and how to run a PowerCLI audit before your renewal conversation — so you're not negotiating blind.

📋 TL;DR: VMware licensing now costs roughly $190–250 per core per year depending on tier, with a 72-core minimum order. A modest 5-host cluster with dual 16-core CPUs = 160 cores = $30,400–40,000/year at list price. Before Broadcom, that same cluster might have run $5,000–10,000/year on perpetual + SnS.

[SCREENSHOT: Side-by-side cost comparison table showing pre-Broadcom perpetual vs post-Broadcom subscription for a 5-host cluster]

What Actually Changed: The End of Perpetual Licensing

On January 22, 2024, Broadcom officially ended perpetual VMware licenses and renewals for all products. This affects every organization on the planet running VMware infrastructure. Here's the complete picture of what changed:

| Feature | Pre-Broadcom (≤2023) | Post-Broadcom (2024+) |

|---|---|---|

| License model | Perpetual + annual SnS | Subscription-only (annual or multi-year) |

| License metric | Per socket (1 license = 1 CPU, up to 32 cores) | Per core (16-core minimum per CPU, 72-core minimum order) |

| Product options | Modular — buy vSphere, vSAN, NSX separately | Bundled — VCF or VVF only |

| Essentials/Essentials Plus | Available for SMBs | Discontinued |

| Support | Optional, purchasable separately | Mandatory, bundled into subscription |

| Compliance enforcement | Trust-based, infrequent audits | Active telemetry monitoring, strict enforcement |

| Late renewal | No penalty | 20% surcharge on first-year subscription cost |

The elimination of Essentials and Essentials Plus kits is particularly brutal for small businesses. There is no longer a budget on-ramp for VMware.

The Two Bundles: VCF vs VVF (That's It)

Broadcom collapsed what was once a modular catalog of 10+ products into exactly two subscription offerings. Every conversation with a Broadcom rep or VAR will eventually come back to this choice.

VMware Cloud Foundation (VCF) — The Full Stack

VCF is Broadcom's flagship bundle. It includes everything:

List price: ~$240–250 per core per year (community-verified Q1 2025 quotes; your negotiated rate will vary)

The "pay for everything" trap: NSX adds real complexity and cost. If your organization doesn't need software-defined networking today, you're still paying for it. VCF requires a minimum of 16 cores per physical CPU for counting purposes and carries the 72-core minimum order for new purchases.

Minimum cluster requirement: Broadcom's official VCF design requires a minimum of 7 physical nodes (4 for management domain + 3 for workload domain) with vSAN storage.

VMware vSphere Foundation (VVF) — The Lean Tier

VVF is the stripped-down alternative:

List price: ~$190–192 per core per year (community-verified)

VVF looks cheaper on a per-core basis, but the vSAN entitlement is tight. A dual-socket server with 32 total cores gets only ~8 TiB included. For most production workloads, you'll hit that cap quickly and need to purchase vSAN Capacity Add-On licenses — which erodes the cost advantage.

[SCREENSHOT: VVF vs VCF feature comparison matrix with checkmarks, showing NSX and Aria gaps in VVF]

The 72-Core Minimum: The Hidden Tax on Small Deployments

This is the change that hit small and mid-size organizations hardest. Effective April 10, 2025, Broadcom mandates a minimum purchase of 72 cores per product per order.

What this means in practice:

Additionally, each physical CPU is counted at a minimum of 16 cores, even if the processor has fewer. A 12-core Xeon is billed as 16 cores.

The math for a small shop:


72 cores × $192/core/year (VVF list price) = $13,824/year

Before Broadcom, a comparable small environment on vSphere Essentials might have cost $600–800/year in SnS renewals on a perpetual license bought years ago.

Step-by-Step: Calculating Your Real Cost

Step 1: Audit Your Physical Core Count with PowerCLI

Before any conversation with Broadcom or a reseller, you need a precise core count. Use PowerCLI against your vCenter to generate an accurate inventory:


# Connect to vCenter first
Connect-VIServer -Server vcenter.yourdomain.local

# Get physical CPU core count per host (this is what Broadcom counts)
Get-VMHost | Sort-Object Name | ForEach-Object {
    $hostView = $_ | Get-View
    $cpuPackages = $hostView.Hardware.CpuInfo.NumCpuPackages  # Physical sockets
    $cpuCores    = $hostView.Hardware.CpuInfo.NumCpuCores     # Physical cores (total)
    $coresPerCPU = [math]::Round($cpuCores / $cpuPackages)
    
    # Broadcom counts each CPU at minimum 16 cores
    $billableCores = [math]::Max($cpuCores, $cpuPackages * 16)
    
    [PSCustomObject]@{
        Host           = $_.Name
        Sockets        = $cpuPackages
        PhysicalCores  = $cpuCores
        CoresPerSocket = $coresPerCPU
        BillableCores  = $billableCores
    }
} | Format-Table -AutoSize


# Get total billable cores across all hosts — your licensing floor
$totalBillable = Get-VMHost | ForEach-Object {
    $v = $_ | Get-View
    $sockets = $v.Hardware.CpuInfo.NumCpuPackages
    $cores   = $v.Hardware.CpuInfo.NumCpuCores
    [math]::Max($cores, $sockets * 16)
} | Measure-Object -Sum

$licenseFloor = [math]::Max($totalBillable.Sum, 72)
Write-Host "Total billable cores (Broadcom model): $($totalBillable.Sum)"
Write-Host "Effective license minimum: $licenseFloor cores"
⚠️ Do NOT use Get-CimInstance Win32_Processor against ESXi hosts — ESXi is not Windows and this query will fail or return garbage. Use Get-View with Hardware.CpuInfo as shown above.

[SCREENSHOT: PowerCLI console output showing the core audit script results for a 3-host cluster]

Step 2: Calculate vSAN Storage Requirements

If you're using vSAN, calculate your raw storage against the per-core entitlement. Use William Lam's official Broadcom core/TiB calculator for precise numbers.


# VVF gives 0.25 TiB per core; VCF gives 1 TiB per core
# Calculate whether you need vSAN Capacity Add-On licenses

$vcfCoresLicensed  = $licenseFloor  # from Step 1
$vvfStorageIncl    = $vcfCoresLicensed * 0.25  # TiB included with VVF
$vcfStorageIncl    = $vcfCoresLicensed * 1.0   # TiB included with VCF

# Get actual raw vSAN capacity in your cluster
$vsanCapacity = Get-Datastore | Where-Object {$_.Type -eq "vsan"} | 
    Select-Object -ExpandProperty CapacityGB
$vsanTiB = [math]::Round(($vsanCapacity / 1024), 2)

Write-Host "Raw vSAN capacity: $vsanTiB TiB"
Write-Host "VVF included storage: $vvfStorageIncl TiB"
Write-Host "VCF included storage: $vcfStorageIncl TiB"

if ($vsanTiB -gt $vvfStorageIncl) {
    $addOnNeeded = [math]::Ceiling($vsanTiB - $vvfStorageIncl)
    Write-Host "⚠️  VVF requires $addOnNeeded TiB in vSAN Capacity Add-On licenses"
}

Step 3: Model 1-Year vs. 3-Year Costs

Multi-year commitments typically yield 15–20% discount versus annual list price — but they lock you into current pricing and the current feature set. Model both scenarios:


# Cost modeling: VCF vs VVF, 1yr vs 3yr
$coreCount     = $licenseFloor  # from Step 1
$vcfListYear   = 250            # $/core/year list price (verify with your VAR)
$vvfListYear   = 192            # $/core/year list price

$discount1yr   = 0.00   # no discount on annual
$discount3yr   = 0.17   # ~17% typical multi-year discount

$results = @(
    [PSCustomObject]@{ Tier="VCF"; Term="1-year"; CostPerCore=$vcfListYear; Total=[math]::Round($coreCount * $vcfListYear * (1 - $discount1yr)) }
    [PSCustomObject]@{ Tier="VCF"; Term="3-year"; CostPerCore=[math]::Round($vcfListYear*(1-$discount3yr),2); Total=[math]::Round($coreCount * $vcfListYear * 3 * (1 - $discount3yr)) }
    [PSCustomObject]@{ Tier="VVF"; Term="1-year"; CostPerCore=$vvfListYear; Total=[math]::Round($coreCount * $vvfListYear * (1 - $discount1yr)) }
    [PSCustomObject]@{ Tier="VVF"; Term="3-year"; CostPerCore=[math]::Round($vvfListYear*(1-$discount3yr),2); Total=[math]::Round($coreCount * $vvfListYear * 3 * (1 - $discount3yr)) }
)

$results | Format-Table -AutoSize

Real-world example for a 5-host cluster with dual 16-core CPUs (160 billable cores):

| Tier | Term | Annual Cost | 3-Year Total |

|---|---|---|---|

| VCF | 1-year | $40,000 | $120,000 |

| VCF | 3-year | ~$33,200/yr | ~$99,600 |

| VVF | 1-year | $30,720 | $92,160 |

| VVF | 3-year | ~$25,500/yr | ~$76,500 |

List prices. Negotiated rates for large deployments are typically lower — engage your VAR or Broadcom directly.

The Late-Renewal Penalty Trap

This one catches organizations off-guard. Broadcom now charges a 20% late-renewal surcharge on the first-year subscription cost if you do not renew by your anniversary date.

On a 160-core VCF deployment at $40,000/year, a missed renewal date costs you $8,000 on top of the renewal fee. This is a hard deadline, not a grace period.

Action items:

Troubleshooting Real Licensing Issues

Problem: "License Mismatch" After Host Addition

When adding a new host to a licensed cluster, vCenter performs a license check. If the new host's core count pushes you over your purchased license total, you'll see a compliance warning in vCenter Health.


# Check current license usage vs. capacity
Get-VMHost | ForEach-Object {
    $v = $_ | Get-View
    [PSCustomObject]@{
        Host            = $_.Name
        State           = $_.ConnectionState
        LicenseState    = $_.LicenseKey
        PhysicalCores   = $v.Hardware.CpuInfo.NumCpuCores
    }
} | Format-Table -AutoSize

Resolve by purchasing additional cores before adding the host. Do not add hosts and plan to "true-up later" — Broadcom's telemetry reports compliance in near-real time.

Problem: vSAN Features Grayed Out

If erasure coding, stretched cluster, or deduplication/compression options appear grayed out, the issue is almost always either:

  1. 1. Insufficient vSAN storage entitlement — you've exceeded your included TiB and haven't purchased Add-On licenses
  2. 2. VVF tier — certain advanced vSAN features require VCF

# On the ESXi host directly — check vSAN status
esxcli vsan health cluster list

# Check storage policy compliance
esxcli storage vsan status get -s

For erasure coding specifically: this requires vSAN Enterprise or VCF. VVF does not include it.

Problem: NSX Features Missing After Migration to VVF

If you migrated from a VCF trial or legacy NSX-T deployment to VVF, NSX will be unlicensed. VVF does not include NSX at any tier. You'll see standard and distributed virtual switches available, but all NSX overlays and distributed firewall rules will cease functioning.

Resolution: Either upgrade to VCF (which includes NSX) or purchase NSX as a separate add-on. There is no partial NSX in VVF.

Hidden Costs Checklist

Before finalizing any Broadcom quote, verify these frequently-missed line items:

| Cost Item | Notes |

|---|---|

| vSAN Capacity Add-On | Required when raw storage exceeds per-core entitlement |

| NSX Advanced Add-Ons | Distributed Firewall, IDS/IPS are add-ons even within VCF |

| VCF Operations for Networks | Some versions require separate license |

| ARM/Non-x86 Infrastructure | Separate SKU discussion with Broadcom required |

| Multi-site/stretched cluster | Additional vSAN licensing implications |

| Late-renewal penalty | 20% of first-year cost if you miss anniversary date |

| Hardware refresh true-up | Adding hosts mid-term requires immediate license amendment |

The Alternatives Conversation

Given these cost increases, the community discussion around alternatives is louder than ever. This isn't the article to deep-dive alternatives, but know that these are actively being evaluated by organizations facing renewal sticker shock:

The migration cost and retraining investment is real. Many organizations will choose to stay on VMware for 3–5 more years while evaluating. The 72-core minimum and late-renewal penalties make that calculus painful but sometimes still better than a full migration.

Summary: What You Need to Do Before Your Next Renewal

  1. 1. Run the PowerCLI core audit (Step 1 above) — know your exact billable core count before any conversation
  2. 2. Check your renewal anniversary date in the Broadcom Support Portal today
  3. 3. Model VCF vs VVF using the cost table in Step 3 — involve your storage team on vSAN entitlement
  4. 4. Verify vSAN raw capacity against included TiB to spot Add-On requirements early
  5. 5. Set renewal reminders — the 20% late fee is avoidable with a calendar alert
  6. 6. Get quotes from a VAR, not just list price — negotiated rates can be 20–40% below list for larger deployments
  7. 7. Evaluate VMUG Advantage if you run a home lab or dev environment — VMUG provides VCF/VVF access for $200/year
💡 Affiliate note: For hardware infrastructure supporting your VMware environment, we recommend server platforms validated on the Broadcom Hardware Compatibility Guide. See our home lab hardware guide for current affiliate picks on budget-friendly Xeon platforms.

Sources & Further Reading

Last verified: March 2026. Broadcom pricing changes frequently — always confirm current rates with your reseller or Broadcom account team before budgeting.

Stay ahead of the VMware changes

We're publishing detailed comparison guides, migration walkthroughs, and cost calculators. Get them in your inbox.

🖥️

Written by Rob Notaro

Senior infrastructure engineer specializing in VMware, Horizon VDI, and enterprise virtualization. Currently deploying Horizon 2512 and VCF in production environments.