OpenClaw Setup: Install It Safely and Keep It Running (2026)
OpenClaw installs with one command on macOS, Linux or WSL2 (curl -fsSL https://openclaw.ai/install.sh | bash), then a guided onboarding connects your model and chat apps. Run it as a service on a small VPS to keep it on 24/7, keep the dashboard off the public internet, and run openclaw security audit before you connect anything important.
Disclosure: Some links on this page are affiliate links. If you buy through them, we may earn a commission at no extra cost to you. It never changes our verdicts or rankings. How we make money.
A careless OpenClaw install can expose your accounts: researchers found hundreds of malicious skills on its marketplace in 2026 (details below). A careful one gives you an AI agent on your own machine that you can reach from WhatsApp, Telegram, Slack, Discord or iMessage.
OpenClaw (formerly Clawdbot, then Moltbot) is the open-source assistant that went viral in early 2026; its GitHub repo had about 392,000 stars on 17 October 2026. This guide covers install, onboarding and running it 24/7, then locks it down. Setup takes about fifteen minutes; doing it safely takes a few more.
What you need
| Requirement | Detail | Source |
|---|---|---|
| Node.js | 24.16+ or 26.1+ (26 recommended); the installer adds it if missing | OpenClaw docs |
| Operating system | macOS, Linux, Windows (native or WSL2) | OpenClaw docs |
| Memory | No official minimum; the official DigitalOcean guide uses 1 vCPU, 1 GB RAM plus 2 GB swap, with cloud models | OpenClaw on DigitalOcean |
| A model | An API key from your chosen provider (Claude, OpenAI and others), or a local model | OpenClaw docs |
You don’t need a Mac mini. A Mac only matters if you want iMessage or to run local models; see where to host OpenClaw.
Step 1: install
macOS, Linux or WSL2:
curl -fsSL https://openclaw.ai/install.sh | bash
Windows PowerShell:
iwr -useb https://openclaw.ai/install.ps1 | iex
Or with npm:
npm install -g openclaw@latest --allow-scripts=openclaw
openclaw onboard --install-daemon
(Drop --allow-scripts=openclaw on npm 11.15 and earlier.) Check it worked with openclaw --version, openclaw doctor and openclaw gateway status.
Step 2: onboarding
The installer starts onboarding for you. Choose Quick start, which checks your model with a real request and opens the dashboard, or Custom setup for every option (openclaw onboard --classic gives the step-by-step wizard).
- Paste your model provider’s API key. The docs recommend the strongest current model you can use, for quality and for resisting prompt injection.
- Connect a chat channel (WhatsApp, Telegram, Slack and others).
- Open the dashboard with
openclaw dashboard. It runs athttp://127.0.0.1:18789/. - When someone new messages your agent, they get a pairing code. Approve them with
openclaw pairing approve <channel> <code>.
Your settings live in ~/.openclaw/openclaw.json. Start by restricting who can message it (for example channels.whatsapp.allowFrom).
Step 3: keep it running 24/7
After Quick start, stop the foreground gateway (Ctrl+C) and install it as a service:
openclaw gateway install
That creates a systemd user unit that restarts automatically. On a VPS, the official guide runs OpenClaw as a non-root user and enables lingering so the service survives logout:
loginctl enable-linger openclaw
Step 4: lock it down
OpenClaw can read your messages and run tools on the machine, so treat setup as a security job:
- Keep the gateway private. A normal install binds to loopback. Reach the dashboard through an SSH tunnel (
ssh -L 18789:localhost:18789 user@host) or Tailscale, not an open port. If you bind it to a network, setgateway.auth.tokenor a password (security docs). - Update. CVE-2026-25253 (rated 8.8) let a crafted link leak the gateway token in versions before 2026.1.29 (OSV).
- Be picky about skills. Koi Security found 341 malicious skills among 2,857 on ClawHub in February 2026, most installing a password stealer (The Hacker News). Read a skill before you install it; see agent skills safety.
- One person per gateway. The docs say a gateway is one trust boundary, not a safe multi-user host.
- Audit. Run
openclaw security auditafter changes.
What it costs to run
The software is free (MIT licence). Your costs are the server and the model:
| Item | Typical cost | Source |
|---|---|---|
| Small VPS | DigitalOcean 1 GB Droplet $6/mo; Hostinger KVM 1 (4 GB) $6.49/mo intro, $11.99 renewal | DigitalOcean, Hostinger |
| Managed OpenClaw | Hostinger’s managed app from $5.99/mo on a 24-month term (renews at $11.99) | Hostinger |
| Model API | Pay per use with your provider; usually the bigger bill | Your provider’s pricing page |
Want your agent to read the web reliably? A scraping API such as Firecrawl (1,000 free credits a month) is a common add-on.
Next: OpenClaw hosting compared, or automate workflows alongside it with n8n.
Tools in this guide
Hostinger
Automation & AgentsRun n8n or OpenClaw on a KVM VPS with ready templates and a managed OpenClaw app.
DigitalOcean
AI CodingRun your own server from $4/mo, launch a hardened OpenClaw 1-Click or rent GPU Droplets.
Firecrawl
Automation & AgentsTurn any website into clean, LLM-ready data through one scraping and search API, priced in credits.
Questions people ask
What do I need to install OpenClaw?
Node 24.16+ or 26.1+ (the installer adds it if missing), macOS, Linux, Windows or WSL2, and an API key from a model provider. The official docs have no RAM minimum; their DigitalOcean example uses a 1 GB server with 2 GB of swap.
How do I install OpenClaw?
On macOS, Linux or WSL2 run curl -fsSL https://openclaw.ai/install.sh | bash. On Windows PowerShell run iwr -useb https://openclaw.ai/install.ps1 | iex. Or use npm: npm install -g openclaw@latest, then openclaw onboard --install-daemon.
How do I keep OpenClaw running 24/7?
Install the gateway as a service with openclaw gateway install (or openclaw onboard --install-daemon), which sets up a systemd user unit that restarts automatically. On a VPS, also run loginctl enable-linger for that user so it survives logout.
Is OpenClaw safe?
It can be, if you keep it updated and private. A 2026 vulnerability (CVE-2026-25253) let a crafted link leak the gateway token until version 2026.1.29, and researchers found hundreds of malicious skills on ClawHub. Keep the gateway on loopback, reach the dashboard over an SSH tunnel or Tailscale, and only install skills you've read.