STAKATERSTAKATERA conversation about what your customers are trying to build — and how we might go to market together.
OpenMetal
Bare metal infrastructure & BMaaS
Stakater
Commercial cloud layer above Kubernetes
Together
Complete cloud platform, 90 days to revenue
The Problem We're Solving
The gap isn't infrastructure — that's solved. The gap is everything between "Kubernetes is running" and "first tenant is paying."
What OpenMetal delivers today
Bare Metal as a Service
Dedicated compute, storage, networking on demand
Kubernetes-ready infrastructure
OpenShift, RKE2, or upstream K8s on your bare metal
What customers still need to build
Self-service portal & catalog
12–14 monthsHard multi-tenancy
16–18 monthsUsage metering + billing API
10–12 monthsTotal: 2–4 years · €3M+ · before first tenant invoice
The Joint Solution
Tenants — internal teams, customers, managed services
Stakater — Cloud Orchestrator
Commercial Layer
Portal · Catalog · Multi-Tenancy · Metering · Billing · White-Label
Kubernetes · OpenShift · RKE2 · Upstream K8s
OpenMetal
Bare Metal Infrastructure
Dedicated compute · NVMe storage · 10/25GbE networking
OpenMetal owns
✓ Bare metal provisioning & lifecycle
✓ Network fabric & uplinks
✓ Hardware SLA & data centre ops
✓ Customer infrastructure relationship
Cloud Orchestrator owns
✓ Tenant portal & service catalog
✓ Hard multi-tenancy (KCP)
✓ Usage metering & billing API
✓ White-label & governance
The Joint Value
OpenMetal gains
Larger deals
BMaaS + SCO is a bigger ticket than bare metal alone
Stickier customers
Operators building on your infrastructure don't churn
Differentiation
Not just BMaaS — a complete "build your cloud" platform
New segments
Neoclouds, MSPs, and CSPs who need both layers today
Your customers gain
90 days to first revenue
vs 2–4 years building the commercial layer themselves
Full stack, one conversation
Infrastructure + commercial layer without separate procurement
No vendor lock-in
Open source KCP + standard Kubernetes APIs throughout
Proven reference architecture
Validated across telco, MSP, government, AI, and neocloud
Stakater gains
Qualified distribution
OpenMetal's customer base is already infrastructure-ready
Validated on bare metal
OpenMetal reference architecture strengthens our BMaaS story
North American reach
OpenMetal's US footprint accelerates our entry there
Neocloud reference customers
Joint wins become the reference story for the segment
Go-to-Market
We're not proposing a specific model yet — we want to explore which fits OpenMetal's priorities and capacity.
SCO validated on OpenMetal infrastructure. Joint solution brief: "Cloud Orchestrator on OpenMetal." OpenMetal refers qualifying customers to Stakater.
→ Referral fee on closed deals
→ Co-branded solution page
→ No sales training needed
OpenMetal identifies customers building cloud services on K8s. Stakater engages jointly on those deals. Both teams co-present and close together.
→ Revenue share on SCO licenses
→ Joint sales playbook
→ Shared pipeline visibility
"OpenMetal Cloud Platform" = OpenMetal BMaaS + SCO commercial layer as a single packaged offering. OpenMetal owns the customer relationship and resells both layers.
→ OEM / resell agreement
→ OpenMetal-branded portal
→ Deepest differentiation
What We'd Like to Understand
We're here to learn as much as to present. These questions would help us scope what a partnership looks like in practice.
How many customers are running Kubernetes on OpenMetal today?
And what are they building on top — internal platforms, managed services, something else?
What's the most common request you can't fulfil today?
Portal, metering, tenant isolation, billing — where do customers say they're stuck?
Are you seeing interest from neoclouds or MSPs who want to build a cloud business?
GPU cloud, sovereign cloud, industry-specific — we see this segment growing fast.
What would need to be true for a bundled "OpenMetal Cloud Platform" to make commercial sense?
Deal size, margin structure, go-to-market motion — where's the line for it to be worth the investment?