The best VPS for OpenClaw: real requirements, not guesswork
What OpenClaw actually needs from a server, measured rather than assumed, and how to choose a provider, size, and setup that won't bite you later.
A small instance suffices: 2 vCPU and 4 GB of RAM runs a personal OpenClaw agent with headroom: the idle agent measures around 540 MB, and a full browser workload runs on exactly that size once a swap file absorbs its bursts. Any reputable provider with that tier for $5–25/mo works; OpenClaw publishes official guides for the major ones. What separates a good setup from a regretted one isn’t the provider: it’s backups, a pinned version, and never exposing the Gateway.
Real requirements, measured
Measured numbers rather than guesswork (mid-2026, current stable line, Docker deployment):
- RAM is the binding constraint. The agent container idles around 540 MB; a 2 GB machine can run a lean agent, and 4 GB gives comfortable headroom for browser work (headless Chromium is the hungry part) plus the OS, with a swap file for the moments the browser piles up tabs. One sharp edge from the official docs: building the Docker image needs ~2 GB free or the build gets OOM-killed. On small machines, use the prebuilt images and the constraint disappears.
- CPU barely matters. The heavy thinking happens at your model provider’s end; the agent machine mostly orchestrates. 2 shared vCPUs are fine.
- Disk: 20–40 GB. OS, images, and an agent’s workspace fit easily; media-heavy use grows over time, not explosively.
- Location: near you is unnecessary. You never browse to the pod interactively for daily use (chat rides outbound channels), so your own distance to it never shows. Its distance to the model shows a little: through OpenRouter, a short model call started a tenth to half a second sooner from a US server than from one in Europe or Singapore (timed from five regions). Pick on price and jurisdiction preference first.
Choosing a provider
OpenClaw’s docs ship setup guides for the major VPS providers (Hetzner, DigitalOcean, Hostinger, Fly.io, and others), which is a practical shortlist by itself. At the ~4 GB tier the cheap end moves: on October 22, 2026, Hetzner’s cost-optimized line was marked not available, and its cheapest 2 vCPU, 4 GB server that could be ordered, the CPX22, cost more than three times as much. All of them run this job fine. Three things worth actually checking, because they differ more than compute does:
- Snapshot/backup pricing and restore workflow: you will want automatic backups on (typically ~20% of the instance price), and a restore you’ve tested once.
- A cloud firewall you can configure to expose SSH only.
- Actual availability: budget tiers at popular providers go in and out of stock, and when one is gone the next server you can order may cost several times as much (Hetzner’s, above), so check what you can order before you plan on a price.
The setup is the actual differentiator
The uncomfortable truth about “best VPS for OpenClaw”: provider choice is maybe a tenth of the outcome. The rest is the setup discipline on whichever box you pick: key-only SSH, the Gateway never on a public interface (double-check this in Docker setups, where the default bind is broader than you’d expect), a pinned version, state volume-mounted and backed up, and openclaw security audit run after setup and every change. The full standard is the safe-hosting checklist; it’s an afternoon to do well and a permanent duty to maintain.
If that list reads like a good weekend, a VPS is a great home for your agent. If it reads like a second job, Everpod’s OpenClaw pod is that same setup (a small dedicated machine, a private gateway, tested backups) operated for you at $29/mo, with up to $10 of model usage included each month. Same agent either way; the difference is whose checklist it is.