Deployment Options
Deploy OpenClaw using various methods
Deploy OpenClaw using various methods
OpenClaw can run on your own hardware, a VPS, managed hosting, in Docker, or on serverless runtimes. The right choice depends on uptime, how much you want to operate, and whether you need the full tool stack (browser, exec, cron). Start with the decision guide belowāthen open the linked walkthrough.
Use this table to pick a host shape. All paths assume you will harden DMs and the Gateway (hardening, pairing).
| Option | Best when | Tradeoffs | Guide |
|---|---|---|---|
| Local laptop / desktop | Trying OpenClaw, dev, file-heavy workflows on your daily machine | Sleeps; not 24/7 unless you keep it awake | Install Ā· No-terminal |
| Mac Mini home server | 24/7 at home, Apple Silicon, you can leave hardware on | Home IP, power, sleep updates | Mac Mini guide |
| VPS | Public uptime, teams bot, predictable remote host | You patch, monitor, pay monthly | VPS hub Ā· Compare providers |
| Managed hosting | Channels live fast, minimal ops | Less control, vendor pricing | Managed guide |
| BYOS | Your VPS account, someone else installs OpenClaw | Still your infra bill | BYOS |
| Docker on a server | Reproducible deploy on VPS or homelab | Container ops on top of host ops | Docker |
Gateway at home, you elsewhere? Use Remote access (Tailscale, SSH tunnels). Serverless subset? See Moltworkerāno browser/exec. Cost ranges: How much does OpenClaw cost? Ā· After install: Personal assistant checklist.
Running production-style upgrades? Use the dedicated Deployment Upgrade Runbook for preflight checks, smoke tests, and rollback flow.
Want a hands-on tutorial? Follow our step-by-step Deployment Tutorial to learn how to deploy OpenClaw with Docker. This page provides an overview of deployment options.
Slack, Microsoft Teams, Discordāquickstarts for Socket Mode, Azure HTTPS, and pairing before you open the firewall.
Choose a channel āRun OpenClaw on a virtual serverāHetzner, DigitalOcean, Vultr, Hostinger. Full control, 24/7 uptime. Compare providers and follow step-by-step setup guides.
VPS Guide āRun OpenClaw 24/7 on Apple Silicon at homeāsleep settings, remote access, and when a VPS is simpler.
Mac Mini guide āDeploy OpenClaw using Docker containers. Learn containerization, orchestration, and best practices for Docker-based deployments.
Docker Guide āDeploy OpenClaw on serverless platforms like Cloudflare Workers using Moltworker. Learn about serverless architecture and limitations.
Moltworker Guide āRun OpenClaw without managing servers. Clawi, xCloud, MyClaw.ai, OpenClaw CloudāWhatsApp, Telegram, Discord in minutes. No VPS, no SSH.
Managed Hosting Guide āYou provide the VPS; a provider installs and manages OpenClaw. OpenClawHosting.io, MoltBotHost, Elest.io, ClawRun.dev. Data on your chosen infra.
BYOS Guide āMulti-agent teams, shared workspaces, and team deployment. SSO, audit logs, and scaling patterns for organizations.
Enterprise āMost installs are a long-lived Gateway plus channels. Observability means you know when the process restarted, why a message failed, and whether disk or CPU is trending wrongāwithout leaking secrets into logs.
On a VPS you might use systemd, pm2, or Docker. The runtime captures stdout/stderr. Identify which unit or container owns the Gateway, then tail that stream only.
Assume logs will be pasted into a ticket: mask tokens, API keys, webhook secrets, and phone numbers before sharing. Chatty channels and debug flags fill disksāset rotation (journald limits, Docker log options, or logrotate). Pair logging with security hardening so you are not widening the attack surface for convenience.
At minimum watch process up and the Gateway TCP port. For richer signals, reuse incident alerting. Shipping lines to Grafana Loki, Datadog, or syslog is normal plumbingāpoint your collector after redaction rules exist. Flags and formats driftācheck docs.openclaw.ai on upgrade. See also Remote access and Deployment upgrade runbook.
For teams and organizations, OpenClaw can run as multiple agents with shared context, per-channel sandboxing, and controlled DM access. Key patterns:
agents.defaults.sandbox.mode to "non-main" so group sessions run in isolated containersallowFrom to restrict who can messageFor managed enterprise options, see Managed Hosting (some providers offer team plans). For self-hosted, use VPS or Docker with multiple Gateway instances or session routing.
When moving to a new server or reinstalling, back up config, credentials, and workspaceāsee Workspace Backup & Restore.