Home β€Ί vs vCloud Director
Comparison

Cloud Orchestrator
vs vCloud Director

vCloud Director was the commercial operating system above VMware. Broadcom's acquisition changed everything. CSPs that have moved to OpenShift Virtualization still need what vCD gave them β€” Cloud Orchestrator is that layer, rebuilt for Kubernetes.

⚠️

vCloud Director's future is uncertain

Since Broadcom's acquisition of VMware, the vCloud Director roadmap has been disrupted. Many CSPs are actively migrating off the VMware stack. The infrastructure problem is solved with OpenShift Virtualization β€” the commercial layer above it is not.

Side by Side

How they compare.

vCloud Director

Cloud Orchestrator

Infrastructure
VMware vSphere only
Any Kubernetes β€” OpenShift, Rancher, upstream
Vendor status
Broadcom β€” roadmap uncertain
Stakater β€” active development
Self-service tenant portal
βœ“
βœ“
Hard multi-tenancy
βœ“ Organisations
βœ“ Kubernetes-native isolation
Metering per tenant
βœ“
βœ“
Billing API
Limited
βœ“ Full billing API
White-label portal
βœ“
βœ“
Container workloads
Limited
βœ“ Kubernetes-native
AI & GPU workloads
βœ—
βœ“ GPUaaS, Model as a Service
Air-gap / sovereign
βœ“
βœ“
XaaS SDK β€” custom services
βœ—
βœ“
Pricing model
Per VM / per vCPU
Base fee + MRU

Why CSPs are choosing Cloud Orchestrator

vCD gave you a commercial layer above VMware.
We give you the same thing above OpenShift.

☸️

Built for Kubernetes, not bolted onto it

vCloud Director was designed for VMware's proprietary stack. Cloud Orchestrator is built Kubernetes-native from the ground up β€” isolation, policy enforcement, and metering work with how Kubernetes actually works, not against it.

πŸš€

Container and VM workloads in one platform

vCloud Director handled VMs. Your tenants also run containerised workloads. Cloud Orchestrator manages both through the same portal, the same catalog, and the same billing layer.

🧩

Extensible where vCD was rigid

vCD's catalog was what it was. Cloud Orchestrator's XaaS SDK lets you define any managed service β€” VMaaS, GPUaaS, DBaaS, or anything specific to your business β€” as a first-class catalog item.

πŸ“…

A roadmap you can rely on

Cloud Orchestrator is under active development by Stakater, with a clear roadmap driven by customer demand. No acquisition uncertainty. No questions about whether the platform will exist in three years.

Migration Path

From vCloud Director
to Cloud Orchestrator.

1

Deploy on your OpenShift

Cloud Orchestrator installs on your existing OCP environment. No changes to the infrastructure below.

2

Recreate your VMaaS catalog

Configure your VM sizes, storage tiers, and networking. The catalog mirrors what tenants had in vCD.

3

Migrate pilot tenants

Onboard a small set of tenants first. Test metering, billing, and the portal experience before full cutover.

4

Decommission vCloud Director

Migrate remaining tenants, connect billing, and shut down vCD. Your cloud product runs on modern infrastructure.

Replacing vCloud Director?

We've done this migration before. Book a demo and we'll show you exactly how your current vCD setup maps to Cloud Orchestrator.

Book a demo

Ready to build your private hyperscaler?

Start with a complimentary 2-hour design workshop. We design your service catalog, tenant model, and 90-day pilot scope β€” with your team, on your infrastructure.