CSPs replacing VMware have solved the infrastructure. OpenShift Virtualization handles the VMs. What they haven't replaced is vCloud Director — the portal, tenant management, metering, and billing that turned infrastructure into a product customers could consume.
The gap CSPs hit after migration
Cloud Orchestrator fills every gap above OpenShift.
The Problem
vCloud Director was the commercial operating system above the infrastructure. That part has no equivalent in the Red Hat portfolio. Without it, the migration is technically complete but commercially broken.
Your customers had a self-service UI in vCD. On OpenShift there is no equivalent — they can't log in and manage their own resources.
vCD tracked every VM, every vCPU-hour, every GB of storage per tenant. OpenShift doesn't bill anyone. Your finance team has no data.
vCD gave every customer their own Organisation. OpenShift namespaces are not the hard isolation CSP customers expect and regulators require.
The Solution
Deploy on top of your OpenShift environment and your customers get the self-service experience they had before. Your team gets the operational control they need. Nothing below OpenShift changes.
Each customer gets their own branded portal. They provision VMs, manage resources, and view usage without raising a ticket with you.
Every customer's workloads run in fully isolated environments. Compute, network, and storage separation enforced automatically.
Define your VMaaS catalog exactly as you did in vCloud Director. Tenants order from the catalog; you control what's available and at what quota.
Every vCPU-hour, every GB, every managed resource tracked per customer. The data your billing team needs is generated automatically.
Feed consumption data directly into your billing system. Invoice customers based on actual usage with no manual reconciliation.
Your brand, your domain, your portal. Cloud Orchestrator runs invisibly — what your customers see is your cloud product, not ours.
Getting There
Installs on your existing OCP environment. Connects to your identity provider and networking on day one.
Configure VM sizes, storage tiers, and networking options. Set quotas and policies per tenant class.
Onboard pilot customers with isolated environments and portal access. Test metering and billing end-to-end before full cutover.
Migrate remaining tenants, connect billing, and decommission vCloud Director. Your cloud product runs on modern infrastructure.
Related use cases
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.