Pricing
We're still building this page out. In the meantime: RunOS is completely free today, unlimited nodes, unlimited clusters, no credit card needed.
Start freeFor teams evaluating RunOS at scale
For teams that need more than a free tier promises
RunOS is BYOC: bring your own cloud. Your workloads never leave your own cloud or hardware account. It's standard Kubernetes underneath, with your own kubeconfig, so nothing about how you run it changes once you bring us in.
If you're weighing RunOS against a platform team build, or you've got questions about how it fits your existing infrastructure, talk to us. We'd rather walk through your setup than have you guess from a pricing page.
What's on the roadmap
Big companies need certain things: compliance, security, audit trails. We're building toward that. None of it has shipped yet. Here's what's planned, not what's live:
-
Roadmap, not shipped
Full audit logs
Who installed what, when, and why, across every cluster you run.
-
Roadmap, not shipped
SSO integration
Team access tied to your existing identity provider instead of separate RunOS logins.
-
Roadmap, not shipped
SOC2 compliance
A formal attestation for teams whose procurement process requires one.
What governance you get today
We're not going to pretend RBAC or SSO inside RunOS gives you control today, because we haven't built them yet. What you actually get right now is simpler and, honestly, harder to argue with: you own the infrastructure outright. It's your cloud account, your kubeconfig, standard Kubernetes with nothing proprietary underneath.
That means whatever access controls, network policies, or audit tooling you already run at the infrastructure layer still apply. RunOS installs services onto your cluster. It doesn't sit between you and the permissions model you've already built. If you disconnect RunOS tomorrow, that governance doesn't change, because it was never ours to begin with.
Talk to us
This isn't a sales-gated quote request. It's a conversation about whether RunOS fits how your team runs infrastructure today, and where the roadmap items above land relative to your timeline. Tell us about your cloud setup, your compliance requirements, and what you're trying to solve. We'll tell you straight whether we're ready for it yet.
Get in touchStart free, self-serve
RunOS has been 1.0 and generally available since June 30, 2026. It's the same product whether you talk to us first or not: unlimited nodes, unlimited clusters, no credit card. If you're a smaller team, or you just want to try it against your own infrastructure before any conversation about roadmap timing, this is the entry point.
Start freeFAQ
- When will SSO, audit logs, and SOC2 ship?
- We don't have dates to share yet. They're on the roadmap, not in the product. If timing matters for your evaluation, tell us and we'll give you a straight answer on where things stand.
- Do we need a contract to use RunOS at scale today?
- No. RunOS is free and self-serve right now, no contract required, whether you're running ten nodes or ten thousand. Talking to us is about fit and roadmap timing, not a gate on usage.
- How does BYOC affect our compliance scope?
- Your infrastructure stays in your own cloud or hardware account the entire time. RunOS doesn't host your workloads, your data, or your Kubernetes control plane, so your existing compliance scope for that infrastructure doesn't change because you added RunOS.
- What do we actually control if RBAC and SSO aren't built yet?
- Everything at the infrastructure layer: your cloud IAM, your kubeconfig, your network policies. RunOS runs standard Kubernetes on hardware you already control, so the access model you've already built keeps working.