VMware Cloud Foundation Licensing

VMware Cloud Foundation is licensed per physical core on subscription only, with a 16-core-per-CPU minimum, a 72-core minimum order since April 2025, and a 2026 list price near $350 per core per year that lands at roughly $185 to $275 per core after discount. There are no perpetual VCF licenses and no per-VM or per-socket option. Your bill is driven by total physical cores across every host you license, multiplied by the term rate, subject to minimums that can force you to pay for capacity you do not use. This guide explains the licensing model, the bundle you are buying, the core-counting rules, and where the negotiation room sits.

VCF is the flagship of Broadcom's restructured portfolio and the successor to the old per-socket vSphere editions. For the full vendor picture see our VMware Broadcom licensing guide and the VMware intelligence hub. For the pricing detail behind the figures here, see our VCF pricing 2026 reference.

How VCF licensing works

VMware Cloud Foundation is sold as a single integrated subscription that bundles the full software-defined data center stack. You no longer buy vSphere, vSAN, and NSX as separate SKUs with their own metrics. You buy VCF per core, and the bundle is included. The metric is the physical core: every core in every CPU of every host running VCF must be licensed, regardless of how many virtual machines or how much of the core capacity you actually use.

The subscription is term-based, offered on one-year, three-year, and five-year commitments, with longer terms carrying lower per-core rates. When the term ends, the right to run the software ends unless you renew, which is the structural break from the perpetual model covered in our end of perpetual licenses analysis. There is no buy-once option remaining.

What the bundle includes

The VCF subscription includes the components that most enterprises previously licensed separately, which is the basis of Broadcom's argument that the higher per-core price buys more software.

The bundle is the value case and the trap at once. If you genuinely use vSAN and NSX, VCF can be cheaper than buying the parts. If you only run vSphere and have no need for software-defined storage or networking, you are paying for capabilities you will not deploy, which is exactly when vSphere Foundation is the better fit.

Core-counting and minimum rules

Three rules determine your licensed quantity, and each can inflate the count beyond your intuition. First, every physical core on every licensed host must be covered; you cannot license a subset of cores on a populated CPU. Second, each physical CPU carries a 16-core minimum, so a 12-core CPU is still billed as 16. Third, since April 2025 Broadcom has applied a 72-core minimum to new orders, so a small deployment below 72 cores still pays for 72.

The minimums punish small and edge deployments hardest. A two-host cluster with modern low-core-count CPUs can pay for 72 cores when it physically has 48, a 50 percent overpay before any discount. The counting math is identical to the model explained in our VMware per-core licensing guide, and it is the single most important number to get right before you request a quote.

VCF versus vSphere Foundation

Broadcom offers two main bundles. VMware Cloud Foundation at roughly $350 per core per year is the full stack. VMware vSphere Foundation, at roughly $135 to $190 per core per year, is the compute-centric bundle for shops that need the hypervisor and management but not the full software-defined data center. Choosing the wrong one is the most expensive single mistake in a VMware renewal.

The rule is simple. If vSAN and NSX are core to your architecture, VCF is the efficient choice. If you run third-party storage and networking and only need vSphere, VVF saves more than half the per-core rate. Run the comparison against your actual deployed features, not your aspirations, and revisit it at every renewal. Our VMware renewal negotiation guide treats this bundle-fit decision as the first lever to pull.

Perpetual-to-subscription conversion

Customers who held perpetual vSphere and vSAN licenses were offered conversion paths into VCF or VVF subscriptions, often with promotional credits for a limited window. The conversion is not a like-for-like swap: perpetual per-socket entitlements are translated into per-core subscription quantities, and the recurring cost frequently exceeds the old maintenance line by a wide margin. Buyers who let the perpetual support lapse and tried to return found there was nothing to reinstate, only a fresh subscription at current pricing, the dynamic explained in our support reinstatement fees guide.

If you are still on perpetual entitlements, model the conversion and the alternatives together before the support contract expires. The conversion offer, a competitive migration, and a vSphere Foundation downgrade are all on the table, and the bargaining power is highest while you still hold supported perpetual licenses.

vSAN capacity and add-on costs

The vSAN included in VCF is not unlimited. The bundle grants a defined storage capacity allowance per licensed core, and estates that store more than the allowance must buy additional vSAN capacity on top of the per-core subscription. For storage-dense workloads this add-on can become a meaningful line item, so model your actual storage footprint against the included allowance before assuming vSAN is fully covered. The same applies to advanced NSX features and certain Aria capabilities, which carry usage boundaries inside the bundle.

This is where the headline per-core rate understates the real cost for some estates. A workload that is storage-heavy but core-light pays the per-core subscription on relatively few cores yet consumes vSAN capacity that triggers add-on charges, inverting the usual economics. The fix is to size storage and compute together at design time, and to decide deliberately whether vSAN is the right storage layer at all, or whether a third-party array on vSphere Foundation serves the workload more cheaply.

Add-on pricing is also a negotiation point in its own right. Bundled allowances, overage rates, and the price of additional vSAN capacity are all quotable line items, and they are frequently overlooked in a renewal focused on the headline per-core rate. Bring them into the renewal negotiation explicitly, because an unmodeled storage overage can erase the saving won on the core rate.

Common VCF licensing mistakes

Four mistakes recur in VCF deployments, and each is avoidable with planning. The first is licensing the full estate on VCF when only part of it uses vSAN and NSX, paying the full bundle premium across workloads that need only vSphere. The second is ignoring the minimums until the quote arrives, then discovering a small cluster is billed at 72 cores. The third is failing to right-size hosts before licensing, leaving half-empty CPUs that round up to the 16-core floor. The fourth is treating the vSAN allowance as unlimited and absorbing storage overage charges that were never budgeted.

The common thread is that VCF rewards deliberate design and punishes default behavior. An estate that lets its hardware and bundle choices drift will overpay structurally, while an estate that designs hosts, splits bundles by workload need, and models storage will pay close to the efficient minimum. The discipline is the same one our per-core licensing guide applies to the core count, extended to the full bundle.

Audit exposure is the quiet fifth risk. Running VCF features beyond your entitlement, exceeding the vSAN allowance, or deploying on more cores than licensed all create compliance findings that surface at true-up or audit. Keep deployment within entitlement and document it, the same way our audit defense practice prepares any vendor estate for scrutiny.

Planning for growth within the term

A VCF subscription is sized at signing, but estates grow, and how you handle mid-term growth determines whether expansion is cheap or punishing. Adding cores during a term is a true-up against your contract, and the rate you pay for those added cores should be negotiated up front, not at the moment you need them. A contract that fixes the true-up rate protects you from paying current list for growth that your original discount should have covered.

Model the growth path before you sign. If you expect to add a cluster or refresh onto denser hosts within the term, price that expansion into the negotiation so the added cores carry the same discount as the base. Buyers who sign for today's footprint and grow into list-priced true-ups lose much of the discount they negotiated, which is why the renewal and growth terms belong in the same conversation.

Consider term length against your growth profile too. A fast-growing estate may prefer a shorter term that lets it renegotiate the whole footprint sooner at a better volume tier, while a stable estate benefits from locking a longer term at a lower rate. The right choice depends on the trajectory, and it is the same flexibility-versus-rate trade examined in our subscription pricing reference.

Common questions

Can I still buy VMware Cloud Foundation perpetually?

No. Broadcom retired perpetual VMware licensing. VCF is sold only as a term subscription on one, three, or five-year commitments, priced per physical core.

What is the minimum I have to buy?

Each physical CPU carries a 16-core minimum, and since April 2025 new orders carry a 72-core minimum. A deployment below those thresholds still pays for them, which hits small and edge clusters hardest.

Is vSAN included in VCF?

Yes, VCF includes a vSAN capacity allowance per licensed core, along with NSX and the Aria management suite. That bundling is the value case for VCF and the reason it costs more per core than vSphere Foundation.

How much can I negotiate off the list price?

Realized VCF pricing commonly lands at $185 to $275 per core after discount, with the most room on orders above 200 cores and multi-year commitments. Treat list as a starting point and benchmark against multiple quotes.