SELF-HOSTED OPENCLAW
WHY OPENCLAW BELONGS ON A VPS
An assistant that can act for you needs three things your laptop cannot promise: it never sleeps, it stays in its lane, and it answers fast.
Always Actually On
- OpenClaw runs as a daemon and keeps working while you are offline, so its home needs real uptime
- Credit-backed 99.9% network uptime SLA with redundant switching behind every node
- Scheduled tasks, reminders, and long-running jobs keep firing at 3am without your help
A Clean Blast Radius
- OpenClaw can execute commands and manage files, which is the point, and also the reason it should not live on your personal machine
- A dedicated VPS is a crisp isolation boundary with full root for you and nothing else on it
- Pairs with OpenClaw's own tokens, allowlists, and safety controls
Snappy Where It Counts
- The gateway is a Node.js process, so 4.5 GHz single-core clocks keep every reply quick
- Direct Tier-1 peering out of Seattle keeps round trips to model APIs short
- TB-scale monthly transfer covers browsing, media, and busy group chats without rationing
The Gateway is OpenClaw's single source of truth for sessions, routing, and channel connections. It runs on your VPS, and only the model calls leave the box.
The Gateway itself is lightweight; headroom is for what you ask it to do. Every plan is online in under 3 minutes with full root access, and the benchmarks behind it are published.
- 2 vCPU
- 4 GB RAM
- 50 GB RAID NVMe Storage
- 8 TB Monthly Bandwidth
- Comfortable for a personal agent
- 2 vCPU
- 8 GB RAM
- 100 GB RAID NVMe Storage
- 16 TB Monthly Bandwidth
- Headroom for browsing and busy skills
- 3 vCPU
- 12 GB RAM
- 150 GB RAID NVMe Storage
- 24 TB Monthly Bandwidth
- Room for several workspaces at once
Isolation Is A Feature, Not Paranoia
We will be straight with you: an autonomous agent that reads messages and runs commands deserves respect. OpenClaw ships pairing tokens, allowlists, and safety controls, and its docs recommend keeping the dashboard private behind SSH or a tailnet. Use them.
What we add is the part you cannot configure in software: a dedicated, isolated server with nothing else on it, full root for you, and engineers keeping the infrastructure honest underneath, 24/7.
This is an unmanaged deployment. You own the agent and its guardrails; we own the uptime.
- MIT-Licensed Open Source developed by the OpenClaw Foundation
- Dedicated Isolation Boundary the agent gets its own box, not your laptop
- Always-On Daemon Home 99.9% network uptime SLA, credit-backed
- 4.5 GHz Single-Core Clocks benchmarks published on VPSBenchmarks
- Dedicated IPv4 Included stable pairing for every channel
- Full Root Access your keys, your rules, your kill switch
OpenClaw's onboarding wizard does most of the work. Bring a model API key and one chat app to pair.
Pick a plan and check out. Your server is online in under 3 minutes with full root access and a dedicated IPv4 address.
OpenClaw wants a current Node.js (22.22.3 or newer; 26 recommended). Then npm install -g openclaw and run the onboarding wizard with its daemon install.
Connect Telegram, WhatsApp, Discord, Slack, or any supported channel, and add the API key for your model provider.
Set allowlists for who may talk to it, keep the dashboard behind SSH or your tailnet, and hand your assistant its first standing job.
Explore the knowledge base or open a ticket in the Console. An engineer answers.
Order a VPS, run the onboarding wizard, and your assistant answers its first message today.
