VCF Licensing Explained: Cores, Components and Cost

VMware Cloud Foundation is licensed per physical core on subscription, with two minimums that frequently decide the quantity before the rate applies. Understanding those minimums and what the bundle actually contains is most of what you need to evaluate a VCF quote sensibly.

This covers the components, the licensing mechanics, real quoted pricing, and the test for whether the premium over VVF is justified for your estate.

VCF is the full private cloud platform. Relative to VVF — which already includes the hypervisor, vCenter, a vSAN entitlement, vSphere Kubernetes Service and operations tooling — VCF adds whole product categories rather than a larger allowance:

• NSX. Software-defined networking: micro-segmentation, distributed firewalling, overlay networks. This is the single most common reason to move up, and there is no partial option.
• VCF Automation. Self-service provisioning and infrastructure-as-code consumption of the platform.
• VCF Operations for Networks. Network visibility and troubleshooting across the stack.
• SDDC Manager. Full-stack lifecycle management — patching ESXi, vCenter and NSX as a coordinated unit rather than component by component.
• A larger vSAN entitlement per core, and Live Recovery capability.

The Aria branding people remember has been folded into VCF Operations and VCF Automation. The capability split is broadly as it was; the names on the quote are not.

Per physical core, on subscription. No perpetual option, no per-socket or per-VM model. Count physical cores, not threads.

16-core minimum per CPU socket. A socket with 12 physical cores licenses as 16. Two sockets at 12 cores each is 24 physical cores licensing as 32.

72-core minimum per order, since April 2025. Below the threshold you license 72 regardless.

These compound, and they are why the quantity line is worth more scrutiny than the rate line. In a VCF quote we issued in 2026 the quantity was 96 cores — and in two VVF quotes from the same period the quantity was exactly 72, which was the order minimum binding rather than a description of the hardware.

The commercial consequence is that host density is a licensing decision. If you are licensing a floor anyway, fewer denser hosts use those cores rather than wasting them. Model this before a hardware refresh, not after.

On a licensing proposal AceMQ issued in 2026: VCF at $344.40 per core per year, 96 cores, one-year term, $33,062.40 for the term. A real quoted figure rather than a list price or an estimate.

For comparison, VVF quotes from the same period came in at $119.08 and $126.29 per core on three-year terms. VCF ran roughly 2.7 times VVF per core.

That ratio is the number to plan against. It means the tier decision changes your bill by a multiple while a hard-fought discount changes it by a percentage — so the sequence that saves money is to settle the tier on requirements first, then negotiate. Teams that do it the other way round optimise the small variable.

One nuance on term: a three-year commitment is often price protection rather than a discount. The per-core rate is frequently not reduced for the longer term — what you get is a locked rate while list pricing moves. Given where VMware pricing has travelled, that hedge is often worth having, but it is not the same thing as a discount. Note too that these orders generally cannot be terminated for convenience, with no pro-rata refund on the unused portion.

One question, asked honestly: can you name the requirement?

NSX. Do you need micro-segmentation, distributed firewalling or overlay networking — often because a compliance obligation names it explicitly? This is the clearest and most common reason to be on VCF, and if it applies the decision is basically made.

Self-service provisioning. Do internal teams need to provision infrastructure themselves through VCF Automation, or does a platform team handle requests? If it is the latter, the automation layer is capability you will not consume.

Fleet lifecycle management. Are you patching enough hosts that SDDC Manager coordinating the stack as a unit saves real operational time? Genuinely valuable at scale; genuinely constraining if you prefer upgrading components on your own schedule.

vSAN capacity. Does your storage-to-compute ratio exhaust the VVF entitlement? Storage economics catch people out more often than CPU sizing does — do that arithmetic against your real footprint.

If none of those land, VVF is the cheaper correct answer and we would tell you so. One regional caveat: Broadcom withdrew VVF from several EMEA countries in December 2025, so in those markets VCF may be the only supported path regardless of requirements. Check availability for your entity before building a case around VVF pricing.

If you want VVF and VCF priced side by side against your real core counts, talk to AceMQ — we are a Broadcom partner and we build these quotes weekly. The tier comparison goes deeper on the decision itself.