01
Same score, same runtime.
Cloud will execute the exact same score files the OSS does. One CLI command to move a project to Cloud, one to move it back. No hidden runtime divergence.
I’m focused on the open-source runtime first. A hosted control plane will follow once the OSS feels right — same score files, same voices, no lock-in. This page is a placeholder. If you’d use Cloud, tell me what you need and I’ll build that, not what I imagine you need.
Nothing here is a commitment. It’s where my head is — published so you can argue with it before any code lands.
Cloud will execute the exact same score files the OSS does. One CLI command to move a project to Cloud, one to move it back. No hidden runtime divergence.
Trace history with replay/diff, golden-dataset dashboards, persistent memory, audit log. The boring infrastructure most teams don’t want to operate themselves.
Model spend goes to your provider directly. Cloud charges for hosted runs, storage, and seats — never a markup on inference.
Apache 2.0 stays Apache 2.0. The day you outgrow Cloud, the same score files run unchanged on your own infra. The deal is "easier than self-hosting", not "stuck on my box".
Drop your email. I’ll write personally — what you’re trying to build, what self-hosting forces you to do that you don’t want to, how I can shape Cloud around that. No drip campaigns, no marketing list.
The OSS runtime ships with the production primitives most teams need: traces, evals, HITL, secret scoping. The control plane is convenience, not capability — what works self-hosted will keep working when Cloud opens.
One install. Your first agent running in 60 seconds. No signup. No telemetry.