Managed Cloud vs Self-Hosted
ClawButler currently has two real operating modes: managed Cloud and self-hosted. The governance core stays the same; the infrastructure and operating responsibility change.
Operating Models#
Managed Cloud
Use the hosted control plane, then connect OpenClaw gateways or pair Runtime Hosts. ClawButler handles the shared control-plane operations and managed infrastructure defaults.
Self-Hosted
Deploy the control plane on your own infrastructure. You keep the same governance core, but you operate reverse proxy, secrets, backups, and supporting services yourself.
What Stays The Same#
- OpenClaw remains the only fully supported provider-native connector path.
- Runtime Host support remains partial for Hermes / Claude Code / Codex: pair, discover, batch-add, attach-mode session sync, and experimental managed inspection.
- Web is still the reference console; CLI, Mobile, and MCP remain official but intentionally asymmetric surfaces.
- Approvals, audit, sessions, cost, budgets, config safety, templates, runbooks, and evidence stay on the same governance contract.
Boundary Differences#
| Boundary | Cloud | Self-Hosted |
|---|---|---|
| Infrastructure ownership | ClawButler operates the shared control plane and managed defaults. | You operate Web, API, database, cache, reverse proxy, secrets, and backups. |
| Notifications and auth plumbing | Shared platform infrastructure is already wired for the hosted environment. | SMTP, push, OAuth, encryption, and backup status depend on your local configuration. |
| Automation auth | Use normal user login for humans and org-bound service tokens for MCP / automation. | Same token model, but you own the surrounding auth, secret rotation, and exposure boundary. |
| Upgrades and rollback | Handled on the hosted control-plane side. | You run the install/update/rollback flow and validate your deployment after upgrades. |
| Support boundary | Best when you want less ops overhead and faster start-up. | Best when you need your own infra, reverse-proxy, and data residency boundary. |
How To Choose#
Choose Cloud
You want to pair a Runtime Host quickly, govern local coding runtimes, and avoid running the control plane yourself.
Choose Self-Hosted
You need to keep API, Web, PostgreSQL, Valkey, and supporting infrastructure inside your own environment.
Keep The Boundary Honest
Neither mode changes the current product contract: OpenClaw-first governance core, Runtime Host partial support, and no provider-native parity claim for Hermes / Claude Code / Codex.
Migration Between Modes#
Cloud → Self-Hosted
- Deploy your own instance and validate health, capabilities, and infrastructure status.
- Recreate the auth and notification boundary you need in the target environment.
- Reconnect OpenClaw gateways or re-pair Runtime Hosts, then verify approvals, sessions, and cost sync.
Self-Hosted → Cloud
- Sign in to Cloud and establish the target organization context.
- Reconnect your OpenClaw gateway or pair Runtime Hosts again from the hosted control plane.
- Verify the governance loop: dashboard, approvals, audit, cost, attach-mode sessions, and any managed projection summaries you depend on.
Pick The Operating Boundary, Not A Marketing Tier
The useful distinction today is managed versus self-managed infrastructure. The governance core is the same contract.