VCF Private Cloud Edition. Who it actually suits.

VMware Cloud Foundation Private Cloud Edition sits at the top of the VCF subscription stack as Broadcom positions it: a fully bundled offering that wraps compute virtualisation, software-defined storage, software-defined networking, automation, lifecycle management, observability, and workload mobility into a single per-core subscription. It is sold as the SKU for organisations that intend to operate a true on-premises private cloud rather than a virtualisation estate that happens to run VMware.

That positioning is largely accurate. Whether it is the right SKU for a given customer depends on whether they actually intend to use the broader bundle as designed, or whether they would be better served by a narrower edition and selective add-ons. This article walks through what is in, what is not, and how to make that decision well.

What VCF Private Cloud Edition includes

The headline contents are the eight components that make up the wider VCF family: vSphere, vSAN, NSX, Aria, SDDC Manager, HCX, and (in current packaging) Tanzu Kubernetes Grid as the runtime. The Private Cloud edition includes all of these with broader feature entitlement than the more basic VCF tiers — particularly in NSX advanced networking, Aria Operations Enterprise, and HCX Enterprise capabilities.

Specifically, the Private Cloud edition typically includes NSX distributed firewalling at scale, advanced load balancing, NSX Intelligence for security analytics, Aria Operations with full capacity-management and assured-performance features, and HCX Enterprise's bulk migration, network extension, and replication-assisted migration features. The exact feature list shifts with version, and the Broadcom Product Guide is the authoritative reference.

Who Private Cloud Edition suits

Organisations building self-service IaaS

The strongest fit is organisations actually delivering self-service infrastructure-as-a-service to internal customers — application teams, lines of business, project deployments. These organisations use Aria Automation as the catalogue, NSX as the network/security policy plane, vSAN as the storage tier, and SDDC Manager as the lifecycle plane. For them the bundled feature set lines up with the operating model.

Organisations with substantial workload mobility needs

The second strong fit is organisations actively moving workloads between datacentres, between on-premises and hyperscaler VMware services, or between geographic regions. HCX Enterprise's bulk migration and network extension capabilities have real cash value, particularly for organisations going through M&A integration, geographic consolidation, or hybrid-cloud transitions.

Organisations with strong security/network policy requirements

The third fit is organisations whose architecture depends on NSX distributed firewalling and advanced security at scale — typically regulated industries (financial services, healthcare, government) where micro-segmentation is part of the compliance posture. For these customers, the NSX advanced feature set in Private Cloud Edition is genuinely load-bearing.

Who Private Cloud Edition does not suit

Organisations running VMware as a hypervisor estate

A meaningful portion of historical VMware customers run vSphere as a hypervisor and not much more. They do not have NSX in production, they may or may not use vSAN, they certainly do not run Aria Automation as a self-service catalogue, and HCX Enterprise is not part of their operating model. For these organisations, Private Cloud Edition pays for capabilities that will not be deployed and creates audit surface (because installed-but-disabled does not always equal "not exposed") without operational benefit.

Organisations planning a migration off VMware

Organisations actively planning a migration off the VMware estate over the subscription term should be sizing their VCF subscription against what they actually need to run during the migration window. Private Cloud Edition's broader bundle is typically the wrong tool here — the right answer is a narrower edition and a shorter term, paired with explicit migration planning.

Organisations with extensive non-VMware investments

Organisations that have already invested in third-party automation (ServiceNow, Terraform/IaC pipelines), third-party observability (Datadog, Dynatrace, Splunk), and third-party security (Palo Alto, Crowdstrike) often find that the Aria and NSX components of Private Cloud Edition duplicate capabilities they have already paid for. The deduplication conversation deserves to happen explicitly, not by default.

The decision framework

The right decision starts from a concrete list of capabilities the organisation will actually deploy in the subscription term. For each item in the VCF Private Cloud Edition bundle, the question is: are we using this in production, and is it load-bearing for our architecture?

If the honest answer for half or more of the bundle is "no", a narrower edition is almost certainly the right choice — even after factoring in any bundled-discount benefit Private Cloud Edition might offer. The math on bundled discounts only works if the bundle scope is actually used.

If the honest answer is "we use most of this, and the rest we plan to deploy over the term", Private Cloud Edition is likely the right SKU — but the negotiation should be paired with explicit feature-deployment commitments from Broadcom, particularly around customer success engagement to land the additional capabilities.

Negotiation considerations specific to Private Cloud Edition

Three negotiation points sit uniquely on Private Cloud Edition deals.

The first is customer success commitment. Private Cloud Edition is sold with implicit customer success engagement — assistance landing NSX advanced features, Aria Operations Enterprise deployment, HCX configuration. The implicit commitment should be drafted into the order form explicitly, with named hours, named outcomes, and explicit escalation paths. Without that drafting, the customer success engagement is whatever the account team can spare.

The second is feature deprecation protection. Broadcom has moved features between tiers and between bundles several times since 2024. Customers signing into Private Cloud Edition should negotiate an explicit "no downgrade" clause: features included at the start of the term remain included for the duration, and any feature retirement triggers a defined commercial remedy.

The third is renewal-time edition optionality. Customers who discover at renewal that they do not actually need Private Cloud Edition should have a contractual path to renew at a narrower edition without penalty. The default order form does not give them this path.

The audit dimension

One under-discussed aspect of Private Cloud Edition is the audit dimension. Because the edition includes features that customers may not use, the audit interrogation often surfaces a subtle but real problem: enabled-but-not-used features.

An NSX distributed firewall that was configured during a project and left running. An Aria Operations monitoring scope that includes environments outside the VCF estate. An HCX appliance still active after a migration completed. Each of these can become a discussion point in an audit even when the customer's intent was reasonable.

The defensive posture is operational rather than legal: maintain a quarterly review of which features inside the Private Cloud Edition bundle are actually deployed, document the configuration state, and disable features that are not in use. The reviews are not difficult; what they require is ownership, and most organisations do not assign it explicitly.

Closing

VCF Private Cloud Edition is the right SKU for organisations actually operating an on-premises private cloud — but that population is narrower than Broadcom's positioning suggests. Customers who use the broader bundle as designed get genuine value from the integration. Customers who use only part of the bundle pay full price for full scope and acquire audit surface they would otherwise not have.

The right answer for any given customer comes from honest assessment of deployed capability, not from accepting the default account-team recommendation. The customers who get this decision right do the assessment first, negotiate the edition second, and treat the bundled feature set as a contract to be defended for the duration of the term.