Cloud Director, licensed.

VMware Cloud Director is the multi-tenant cloud management platform that service providers, large enterprises, and managed-service operations use to deliver VMware-based services to internal or external customers. Its licensing structure has always been distinctive — different from per-CPU VCF, different from per-node hyperscaler pricing — and the Broadcom transition has reshaped it further. This article works through the Cloud Director licensing mechanics for 2026: who needs it, how it is sized, how it interacts with the broader VCF stack, and where the audit and renewal risks sit.

If you operate Cloud Director or are considering it as part of a service-provider or large-enterprise architecture, the licensing detail matters more than usual because the metric is non-obvious and the cost can scale rapidly if the architecture is not planned carefully.

What Cloud Director is

VMware Cloud Director is a software-defined multi-tenancy platform built on top of vSphere, vSAN, and NSX. It provides organisation-level resource isolation, role-based access control, self-service provisioning, network and storage policy management, and tenant-facing portals. The platform is used heavily by VMware Cloud Provider Programme (VCPP) partners to deliver hosted VMware services, and increasingly by large enterprises running internal cloud-platform models to deliver VMware capacity to internal business units.

Functionally, Cloud Director sits above the base SDDC components. It does not provide the underlying compute, storage, or networking — those come from vSphere, vSAN, and NSX. It provides the multi-tenancy, policy, and self-service overlay that turns a single SDDC into a hosted service.

The licensing metric and the SKU structure

VMware Cloud Director is licensed primarily on a per-VM-running metric in service-provider contexts (through VCPP) and on a per-core or per-tenant metric in enterprise contexts. The exact metric depends on which licensing programme the customer is on.

For VCPP service providers, the historical billing model has been monthly per-VM-running reporting, with the per-VM rate set by the customer's VCPP tier and rental level. Under Broadcom, this model has been substantially retained, but the underlying rates have moved upward and the audit posture on monthly reporting has tightened.

For enterprise customers, Cloud Director is licensed as a separate add-on to the VCF subscription, on a per-core basis matching the underlying VCF entitlement. The per-core add-on charge is meaningful — typically 10% to 20% on top of the base VCF subscription — and many enterprises do not realise it is separately required until they try to deploy Cloud Director against an existing VCF entitlement.

What is included in the Cloud Director licence

The Cloud Director licence covers the multi-tenancy management platform itself, including the tenant portals, the orchestration engine, the policy framework, and the API layer that enables programmatic interaction.

It does not cover the underlying VCF components, which remain separately licensed. It does not cover the operations management components (Aria Operations Tenant, formerly vRealize Operations Tenant App), which are separately licensed where deployed. It does not cover the chargeback and metering components (formerly vRealize Chargeback), which are also separate.

For service-provider deployments, the practical licensing stack typically looks like: VCPP base entitlement for vSphere, vSAN, NSX, plus the Cloud Director multi-tenancy licence, plus Aria Operations Tenant for tenant-facing operations, plus Aria Automation for service catalogue, plus the chargeback component if used. The total licensing cost stacks up quickly if all components are deployed without rationalisation.

The Broadcom transition impact on Cloud Director licensing

Three specific shifts under Broadcom have affected Cloud Director customers.

VCPP rate increases. The VCPP rental rates that service providers pay have moved upward materially under Broadcom. The increases vary by tier and by partner relationship but have routinely been in the 20% to 40% range for partners renewing under the new terms. This has compressed margins for VCPP partners and forced many to raise tenant-facing prices in turn.

Reporting compliance scrutiny. VCPP requires monthly reporting of VMs-running by partner. Broadcom has tightened the scrutiny on these reports, both in audit interpretation and in the level of detail required. Partners with sloppy historical reporting have been particularly exposed.

VCF bundling pressure. Broadcom has been pushing VCPP partners to convert to VCF subscription terms rather than per-VM-running terms. The pitch is operational simplicity; the practical effect for many partners is a significant cost increase because their VM-running profile is not utilised at the level that VCF subscription pricing assumes.

Audit risks specific to Cloud Director

Customers running Cloud Director have several specific audit-risk patterns to manage.

Misreported VM counts. Service providers reporting VM counts to Broadcom on a monthly basis are exposed to historical audit if the reports turn out to have been inaccurate. Broadcom's audit team now routinely requests historical VM utilisation logs that can be cross-referenced against the reports. Discrepancies produce significant settlement claims.

Tenant-side compliance bleed-through. In some VCPP arrangements, the licence compliance posture of the tenant — not just the service provider — can come under scrutiny. Where tenants run unlicensed VMware components inside their service-provider-hosted environment, the responsibility for the compliance gap is contractually murky and frequently litigated.

Enterprise per-core gaps. Enterprises running Cloud Director on top of VCF without the separate Cloud Director licence frequently surface as compliance gaps in audit. The Cloud Director software runs without a licence-enforcement check that would block deployment, so the gap is easy to create unintentionally.

Sizing Cloud Director deployments

For customers planning Cloud Director deployments, several sizing considerations matter for both cost and operational viability.

The Cloud Director licensing scales with the underlying VCF footprint, not with the number of tenants or the number of VMs directly. This means that consolidating tenants onto fewer, larger SDDCs is licensing-favourable, while distributing tenants across many small SDDCs multiplies the licensing cost.

The operational implications of consolidation are real, however. Larger SDDCs concentrate tenant blast radius, complicate change management, and create cross-tenant contention risks. The right balance is workload-specific and depends on the tenant profile.

For enterprises building internal cloud platforms with Cloud Director, the typical mistake is to over-engineer the multi-tenancy boundary. Many internal-customer use cases do not need Cloud Director's full feature set and can be served more economically with vSphere's native organisation features or with simpler self-service tooling. Reserving Cloud Director for genuinely multi-tenant deployments — where strict isolation and per-tenant accounting are required — keeps the licensing cost contained.

Negotiating Cloud Director terms

For both service providers and enterprises, several specific negotiation levers apply.

VCPP partners have leverage in their volume of consumption, their geographic footprint, and their ability to make credible threats around platform migration (to alternative virtualisation stacks or hyperscaler-native multi-tenant offerings). The negotiation typically happens through the partner channel rather than direct, but the levers are real.

Enterprises have leverage in bundling Cloud Director licensing into the broader VCF renewal conversation rather than treating it as a separately negotiated add-on. The bundled negotiation produces better outcomes because the headline VCF deal is large enough to absorb adjustments on the Cloud Director line.

Both customer types benefit from precise upfront analysis of which Cloud Director features they actually use. Many deployments use a small subset of the platform's capabilities, and the negotiation can sometimes be structured to reflect that — through targeted SKU selection, through tiered pricing, or through scope-limited add-on terms.

Alternatives to Cloud Director

Customers reconsidering Cloud Director under the new commercial reality have several alternative directions to evaluate.

Hyperscaler-native multi-tenancy. For service providers, the alternative of running tenants on hyperscaler-native infrastructure with the provider's own multi-tenancy overlay is increasingly viable. The economics depend on the tenant profile and the workload mix, but for net-new service-provider buildouts, this path is increasingly chosen over Cloud Director.

Simpler self-service for enterprises. For internal-cloud-platform use cases, simpler self-service tooling — Terraform modules, GitOps workflows, ServiceNow integrations — often produces equivalent end-user experience without requiring Cloud Director's multi-tenancy machinery.

Containers and Kubernetes. For both service-provider and enterprise contexts, Kubernetes-based multi-tenancy patterns are absorbing use cases that historically would have used Cloud Director. The operational model is different and the migration is non-trivial, but the long-term cost trajectory often favours the container path.

What to do now

If you operate Cloud Director as a service provider

Audit your VCPP reporting accuracy against deployed VM history. Tighten the reporting discipline if there are gaps. Engage proactively on the next VCPP renewal cycle with a clear picture of your volume, your alternatives, and your cost trajectory under the new rates.

If you run Cloud Director in an enterprise

Confirm that your Cloud Director licensing is in place against your actual deployment. Audit the feature usage to confirm Cloud Director is genuinely needed across the full deployment footprint. Bundle the next Cloud Director renewal into the broader VCF renewal conversation.

If you are evaluating Cloud Director for a new deployment

Be precise about which use cases genuinely require Cloud Director versus which could be served by simpler alternatives. Plan the sizing around consolidation rather than fragmentation. Budget the licensing as a meaningful add-on cost, not as a free overlay on the VCF subscription.

The strategic bottom line

VMware Cloud Director remains a viable platform for multi-tenant VMware deployments, but the new commercial reality requires more discipline than the historical model demanded. Service providers face material rate increases and tighter reporting scrutiny. Enterprises face per-core add-on charges that frequently get missed in initial planning.

For deployments where Cloud Director's full multi-tenancy capability is genuinely needed, the platform is still the right answer. For deployments where lighter alternatives could serve the use case, the cost of Cloud Director frequently outweighs the value. The work to make this distinction precisely — feature-by-feature, tenant-by-tenant — pays back over the multi-year deployment horizon and produces materially better outcomes than treating Cloud Director as a default multi-tenancy choice.