OpenShift runs the workloads.
What runs the cloud business on top?


The question your CSP customers are asking — and the answer.

Here's where the gap is.

Missing

Cloud Product

Self-service  ·  Billing  ·  White-label  ·  Service catalog

Customers need this. Nobody provides it.

Fills the gap

Cloud Orchestrator

Multi-tenancy  ·  Governance  ·  Metering  ·  API-first

Solved

Red Hat OpenShift

OCP  ·  Virtualization  ·  Data Foundation

What Cloud Orchestrator is made of.

KCP

Control Plane

Kubernetes-like API server. Multi-workspace, one per tenant. Declarative desired state synced to clusters.

Multi-Tenant Operator

Red Hat Certified

Enforces tenancy on each OpenShift cluster independently. Runs locally, no lateral exposure.

Portal

Self-Service

White-label customer portal. Your brand, your domain.

Service Catalog

Extensible

Publish any service. VMs, clusters, databases, custom offerings.

FinOps Operator

Metering

Usage tracking, cost attribution, billing feeds.

Config and execution are separated.

Configuration Layer — KCP

Single source of truth

Tenant definitions  ·  Service policies  ·  Identity (Keycloak)  ·  Desired state

End users interact here. Never with infrastructure directly.

Outbound sync only — clusters connect in, not the other way

Execution Layer — OpenShift

Hosting Clusters

Cluster A

MTO

Cluster B

MTO

Cluster N

MTO

Clusters enforce rules locally. Not routable to each other. Compromise of one doesn't reach another.

✓ Security by separation ✓ Scale without rearchitecting ✓ Multi-cluster independence ✓ Sovereign-ready

Built by people who run it themselves.

Stakater Cloud runs on this stack in production. Real tenants. Real workloads. If you want to dig into the architecture — let's talk.

stakater.com