The Playbook

How to Build a
Cloud Business

on Red Hat OpenShift + Stakater Cloud Orchestrator



For CSPs, MSPs, and telcos ready to turn infrastructure into a product.

The window is open.

The VMware migration is creating a once-in-a-decade opportunity for service providers.

๐Ÿ—๏ธ

VMware's base is in motion

Millions of workloads need a new home. Every organisation managing those workloads needs a new platform โ€” and a new commercial model on top.

๐Ÿš€

OpenShift is the landing zone

Enterprise-grade, battle-tested, Red Hat backed. The de-facto choice for the next-generation cloud. The infrastructure problem is solved.

โฑ๏ธ

First movers win

The service providers who build a cloud product now define the market. Late movers become customers of the ones who moved first.

Infrastructure is not a cloud business.

A cloud business has three layers. Most service providers only have one.

Layer 3 โ€” What you sell

Cloud Product

Self-service portal ยท Service catalog ยท SLA-backed plans ยท Cost transparency ยท Your brand

Layer 2 โ€” What governs it

Commercial Platform

โ† Stakater Cloud Orchestrator

Multi-tenancy ยท Governance ยท Metering ยท API-first automation ยท White-label control plane

Layer 1 โ€” What runs it

Infrastructure

โ† Red Hat OpenShift โœ“ Solved

OpenShift Container Platform ยท OpenShift Virtualization ยท OpenShift Data Foundation

Layer 1: Red Hat OpenShift

The foundation. You may already have this.

โœ“

OpenShift Container Platform

Enterprise Kubernetes. Runs containerised workloads at scale. The operating system for your cloud.

โœ“

OpenShift Virtualization

Run VMs alongside containers on the same platform. The direct VMware replacement โ€” without the lock-in.

โœ“

OpenShift Data Foundation

Enterprise storage โ€” block, file, object. Runs on your hardware. No external storage vendor needed.

Why it matters

The hardest part of building a cloud is already done.

Enterprise infrastructure takes years to build and battle-test. OpenShift gives you that foundation on day one โ€” Red Hat backed, enterprise supported, sovereign-ready.

Now build the business on top of it.

Layer 2: Cloud Orchestrator

The commercial layer OpenShift doesn't ship with โ€” and every cloud business needs.

Multi-Tenancy

Many customers sharing the same infrastructure โ€” completely isolated from each other by architecture, not configuration. No lateral exposure between tenants.

Self-Service

Customers provision and manage their own resources through your branded portal. No tickets. No waiting. No engineering involvement per request.

Service Catalog

Define, publish, and sell services โ€” VMs, Kubernetes clusters, databases, backups. New offerings go live the day you decide to sell them.

Metering & Billing

Usage tracked per tenant, per service, per resource. Real-time cost transparency for your customers. Feed directly to your billing system.

Governance

Policies, quotas, RBAC, and compliance controls โ€” defined once, enforced everywhere. Audit trail out of the box.

White-Label

Your brand, your domain, your experience. Customers never see the infrastructure underneath. You are the cloud provider.

Layer 3: Your cloud product.

Define your service catalog. These are the services your customers can provision on demand.

๐Ÿ–ฅ๏ธ

Virtual Machines

Self-service VM provisioning on OpenShift Virtualization. Pick size, OS, storage.

โŽˆ

Kubernetes Clusters

Dedicated or shared OpenShift clusters โ€” provisioned in minutes, not weeks.

๐Ÿ—„๏ธ

Databases as a Service

Managed PostgreSQL, MySQL, Redis โ€” self-provisioned, backed up, monitored.

๏ผ‹

Anything else

Backup-as-a-Service, monitoring, custom workloads โ€” if it runs on OpenShift, it can be a catalog item.

New services go live the day you decide to sell them. No custom integration work per offering.

Package it. Price it. Sell it.

Cloud Orchestrator gives you the commercial levers to build a real cloud business model.

Service tiers

Basic Standard Enterprise

Different quotas, SLAs, and price points per tier. Upsell paths built in.

Consumption-based billing

Customers pay for what they use. Revenue scales with usage โ€” not with your headcount. Every new customer improves your margins.

White-label experience

Your brand, your domain, your pricing. Customers see your cloud product โ€” not the infrastructure underneath. You control the relationship.

The result

Revenue grows faster than costs. Your tenth customer costs almost nothing extra to serve. Your fiftieth improves your margins. That's a platform business โ€” not a services business.

How it works under the hood.

Config and execution are separated. That's the design principle that makes it secure and scalable.

Configuration Layer โ€” KCP

Single source of truth

Tenant definitions ยท Service policies ยท Identity (Keycloak) ยท Desired state for all clusters. End users interact here โ€” never with infrastructure directly.

Outbound sync only โ€” clusters connect in, not the other way around

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 cluster doesn't reach the others.

โœ“ Security by separation โœ“ Scale without rearchitecting โœ“ Sovereign-ready by design

From OpenShift to cloud business.

The path is shorter than you think.

1

Start with your OpenShift cluster

OCP, Virtualization, Data Foundation. The foundation. If you have it โ€” you're further than you think.

You may already be here
2

Deploy Cloud Orchestrator on top

Runs on your OpenShift cluster. Adds the commercial layer โ€” tenancy, metering, portal, catalog.

3

Define your service catalog

What do you want to sell? VMs? Clusters? Databases? Publish them. Customers can provision immediately.

4

Set your tiers and pricing

Basic, Standard, Enterprise. Define quotas, SLAs, and prices. Consumption-based or subscription โ€” your choice.

5

Launch your cloud product

Your brand. Your portal. Your cloud. Go live and start onboarding customers โ€” without adding headcount.

This isn't a roadmap.
It's in production.

Stakater Cloud is the reference implementation. We built this for ourselves first.

โœ“

Running since October 2024

Launched Stakater Cloud โ€” managed OpenShift with Cloud Orchestrator as the commercial layer. Paying customers from day one.

โœ“

Multi-tenant, self-service, white-label

Every capability in this deck runs in production on our own platform โ€” not a demo environment.

โœ“

Decoupled and available to others

We productized the commercial layer so other CSPs and MSPs can run the same model โ€” without building it from scratch.

Stakater

Red Hat Premier Partner since 2018

โœ“ Red Hat Certified Multi-Tenant Operator

โœ“ Master Services Agreement โ€” Sweden

โœ“ Reloader โ€” 24B+ downloads, 9.9k GitHub stars

โœ“ Global team โ€” 8 countries

Your cloud business
starts with one conversation.


Red Hat OpenShift + Stakater Cloud Orchestrator.
The complete stack โ€” infrastructure and commercial layer โ€” ready to go.



stakater.com