Run OpenClaw on a VPS: The Cheap Always-On Setup

A local install proves whether OpenClaw fits your workflow, but it has an obvious limit: the gateway is only reachable while your computer is awake. A small VPS (virtual private server) is the cheapest way to answer the next question — what changes when OpenClaw is online all the time — without buying hardware or paying a hosted service's markup.

This guide covers what a VPS setup actually costs, how to choose a provider, the setup sequence, and the security boundary a public server demands. Commands change; follow the official installation docs for the install itself and treat this page as the operational checklist around it.

What it really costs

Budget two line items, because people routinely forget the second:

• The VM: roughly $4–6 per month. A small instance with 1–2 vCPUs and 2 GB of RAM is enough for a personal OpenClaw gateway. Hourly billing means a short experiment costs cents, not a month.
• Model usage: variable, and on you. OpenClaw is open source, but every conversation calls a paid model API. Set a monthly spending limit or budget alert with your provider before the first chat. For many users this is the larger of the two costs.

"Free trial" credits from cloud providers can cover the VM for an experiment — they never cover model tokens.

Choosing a provider

The mainstream options are closer than marketing suggests. For a personal gateway, compare them on three practical axes rather than benchmarks:

• Price and billing granularity. Hetzner is typically the cheapest per month in its regions; DigitalOcean and Vultr are competitive and bill hourly, which suits disposable experiments.
• Region. Pick a region close to you (or close to your model provider's endpoints) to keep latency and any data-residency questions simple.
• Operational extras. Backups, snapshots, and a usable firewall layer are worth more to a beginner than raw CPU. Snapshots in particular make experiments reversible: snapshot before you change anything important.

Do not over-buy. If a $6 instance feels slow for a single-user gateway, the bottleneck is almost never the VM size.

The setup sequence

1. Create a fresh, dedicated VM. Do not reuse a server that hosts anything else. Choose the current Ubuntu LTS image unless you have a reason otherwise.
2. Lock down SSH first. Key-based login only, password login disabled, and a non-root user for daily work. Most providers can apply a basic cloud firewall at creation — enable it and allow only what you need.
3. Install OpenClaw using the official installer or npm route, exactly as you would locally — the install guide walks through it and covers the common errors.
4. Run onboarding with minimum scope. One model provider, one channel, a tight allowed-sender list. Test one real conversation end to end.
5. Make it survive reboots. Set up the process manager or systemd unit the official docs recommend so the gateway restarts with the VM.
6. Schedule the end. Even a "permanent" experiment benefits from a calendar reminder: review in two weeks whether the always-on setup earned its cost, and snapshot before major upgrades.

The security boundary a public server demands

Moving from localhost to a public IP changes your threat model — treat it that way:

• Never expose the gateway broadly. Restrict network access to the ports and sources you actually need; a provider firewall plus the application-level allowlist is the minimum, not the maximum.
• Use the official security tooling. The official security guide documents access controls such as allowlists and includes a security audit command. Run it after setup and after every config change.
• Keep credentials boring. Fresh API keys for the VM, a provider spending cap, and a written list of every token on the machine so teardown is complete.
• Do not copy your life onto it. A trial VM needs one test channel, not your entire personal archive. Limit what the assistant can reach and treat third-party skills and plugins as code that receives the privileges you grant.

VPS or hosted?

A VPS trades money for effort: cheapest always-on control, but you own updates, backups, and exposure. A hosted service trades control for convenience at a higher monthly price. If you are still weighing that choice, read Hosted OpenClaw vs Self-Hosting: How to Choose before committing to either.