Managed cloud
Use the hosted control plane — sign up, create your organization, pair your own workers — and what differs from self-hosting.
Managed cloud
The managed cloud is the same control plane as the self-hosted core, operated by us: we run the API, dashboard, database, backups, updates and monitoring. Your workers still run on your machines, with your agents, your code and your provider keys.
Get started
- Sign up at the dashboard. Your account and first organization are created.
- Your organization starts on a trial; see Billing for what happens when it ends.
- Install a worker on a machine with your code and a signed-in agent, and pair it with the cloud: Workers on the managed cloud.
- Create a project — or connect GitHub — and your first task, exactly as in the quick start.
What is the same
Tasks, workers, agents, providers, capabilities, verification, Git, integrations, the API, the CLI and the mobile app work as documented everywhere else in these docs.
What differs
| Self-hosted | Managed cloud | |
|---|---|---|
| Who runs the control plane | You | Us |
| Plans and limits | None | Your plan's limits on workers and members |
| Billing | — | Plans, trial, invoices on the Billing page |
| Server settings, feature flags | Your platform administrators | Our staff |
| Integration callback URLs | Any | Must be public https addresses |
| Platform-level capabilities | Yours | Curated by us; your organization registers its own too |
| Plugin execution | You decide | Off by default; ask support to enable it |
The control plane never clones or stores your repositories: agents work on your workers. It does store task metadata and timelines — including agent output, verification logs and reports, which can contain excerpts of code — and artifacts such as screenshots. Secret values are redacted from recorded output.