Most "best VPS for OpenClaw" threads on Reddit end the same way: someone starts on a $5 Hetzner box, runs fine for two weeks, then loses a Saturday to gateway binding errors, OAuth refresh loops, or headless Chrome failing on Ubuntu's snap-packaged Chromium. The VPS line item was never the problem.
This guide is the honest version of that conversation. We cover the actual hardware OpenClaw needs, the VPS providers operators pick most often (Hetzner, Contabo, Hostinger, OVHcloud, DigitalOcean, IONOS), what "cheap" really costs once you count your time, and the case for skipping the VPS entirely in favour of managed hosting.
TL;DR — which VPS should you use for OpenClaw?
- Cheapest that actually works: a Hetzner CX22 / CPX22 at ~$4.99–$6.99/mo. 2 vCPU, 2–4 GB RAM is enough for the gateway, a headless browser, and a Telegram bot.
- Best raw specs per dollar: Contabo, up to 16 vCPU / 64 GB RAM / 500 GB NVMe. Clunky UI, but hard to beat on price.
- Easiest click-path (with trade-offs): Hostinger VPS with their nexos.ai-backed OpenClaw template — fast to set up, but a 24-month term, ~$14.99/mo renewal, and ~10% markup on Anthropic inference.
- Best docs, highest bill: DigitalOcean at ~$24/mo for the recommended spec. Great community, poor value at this tier.
- Enterprise infra, full DIY: OVHcloud and IONOS. Fine compute, no OpenClaw-specific path. You're building from scratch.
- Skip the VPS if you want always-on agents, don't want to own updates, OAuth rotation, and 3 AM reboots. Managed options like KiloClaw run $9/mo with Firecracker-VM isolation and 500+ AI models at zero markup — often cheaper than a DIY VPS once you add inference.
OpenClaw VPS requirements — what the agent actually needs
OpenClaw does not run inference on your server. It runs the gateway, a headless browser, a Telegram / Slack / Discord bridge, and some background workers. Inference is offloaded to whichever model provider you configure. That keeps the hardware bar genuinely low.
Reddit users who have actually deployed OpenClaw to a VPS consistently report that a 2 vCPU / 2 GB RAM box is enough for a single always-on agent — the gateway, a headless Chrome, and a Telegram bot don't need more. The most-upvoted Hetzner setup guide on r/openclaw recommends stepping up one tier to the CPX22 at ~$6.99/month (2 vCPU / 4 GB RAM) as the comfortable everyday spec, and nearly every community install script defaults to that range.
Rule of thumb
| Use case | vCPU | RAM | Disk | Notes |
|---|---|---|---|---|
| Single personal agent, light browsing | 1–2 | 2 GB | 20–40 GB | Hetzner CX22 tier. Fine for Telegram-only agents. |
| Everyday agent + headless Chrome + a few tasks | 2 | 4 GB | 40–80 GB | Hetzner CPX22, Contabo VPS S. Most operators land here. |
| Multi-agent team, heavy browser / scraping | 4 | 8 GB+ | 80–160 GB | Contabo VPS M, Hetzner CPX32. Headroom for multiple workers. |
| Local LLM on the same box | 8+ | 16 GB+ | 200 GB NVMe | Realistic only on Contabo, bare metal, or a used Mac Mini M1/M2. |
Don't spec a VPS against local inference unless you're actually running a local model — you'll pay 3–5x for compute you'll never use.
What "cheap OpenClaw VPS" really costs
The recurring theme across r/openclaw cost threads: the VPS is the smallest line item on the bill. A £6.99 / $7-ish VPS is more than enough for the gateway and orchestration — the real money goes to model inference. Operators who let their agent run loose on premium models all day regularly spend 3–5× the VPS cost on tokens.
Several community members who have migrated from self-hosted VPS to managed hosting report similar math: $10/mo VPS plus $15–25/mo in OpenAI API tokens works out to roughly $25–35/mo all-in, at which point a managed plan with included credits comes out cheaper for mid-range usage.
The VPS is rarely where you save money. You save money by choosing cheaper models (Kimi K2.5, DeepSeek, Gemini Flash) and by not leaving the agent in an infinite loop. For a full breakdown see how much OpenClaw costs and how to reduce OpenClaw API costs.
The best VPS options for OpenClaw
These are the providers that actually show up repeatedly in r/openclaw, r/VPS, r/hetzner, and r/Hostinger threads — in rough order of popularity.
Hetzner — the default pick (when it's in stock)
Hetzner is the runaway favourite across r/openclaw. CPX22 at €5.83/mo (~$6.99) gets you 2 vCPU, 4 GB RAM, 40 GB NVMe, and 20 TB of traffic. The most-upvoted setup guide on r/openclaw is built around it, and the "$4.99/mo deploys in one command" community CLI defaults to Hetzner plus OpenRouter. The short community verdict: "Hetzner is a fine choice."
The catches you will hit:
- Capacity. During the OpenClaw rush, Hetzner's r/hetzner subreddit filled with users reporting that every CX tier sold out across every region — even the less-used Finland data centers. Stock has recovered but still fluctuates.
- Rate limiting and bot detection from datacenter IPs. This isn't Hetzner-specific but it bites hardest there because so many OpenClaw agents share that IP space. Operators repeatedly report that any headless browser step hits Cloudflare challenges or outright blocks when it runs from a well-known VPS range.
- Signup friction. Multiple users on r/VPS describe Hetzner's verification process as unusually strict, including photo ID checks for some regions — not a blocker, but a surprise if you expected a one-click signup.
- Gateway binding. The default OpenClaw install binds to loopback. On a VPS that means the Control UI is invisible from the internet until you set
OPENCLAW_GATEWAY_BIND=lanand configuregateway.controlUi.allowedOrigins.
If you want a VPS and you can get one, get a Hetzner CPX22. That's what most of Reddit is actually using.
Contabo — maximum compute per dollar
Contabo is where people go when they've outgrown Hetzner's tiers or need big RAM for local models and scraping workers.
The community quote: "I use Contabo. Very cheap and works good, but the UI sucks."
From the Contabo alternative page: Contabo offers the best raw specs per dollar with plans up to 16 vCPU / 64 GB RAM / 500 GB NVMe — but you own updates, security, crashes, and 3 AM debugging.
When Contabo makes sense: you need maximum compute per dollar (up to 16 vCPU / 64 GB RAM / 500 GB NVMe), unlimited traffic, and full root access for a custom stack. You're comfortable that the control panel looks like it was designed in 2014.
When it doesn't: Contabo provisioning is slower than Hetzner (sometimes hours, not minutes), and their network/IO can be noisier under load. Fine for long-running agents, less fun when you're trying to debug a boot loop.
Hostinger — the "I just want a template" path
Hostinger is the managed-ish story inside the VPS category. Their Hostinger VPS with the OpenClaw template is backed by nexos.ai and gets you to a running agent faster than the DIY providers.
The community quote: "I use Hostinger. It's been a fine experience. It's cheap."
From the Hostinger alternative page: Hostinger is a hosting company that bolted an AI agent onto their VPS business. Their $6.99 starter requires a 24-month commitment, renews at $14.99, and routes inference through nexos.ai with ~10% markup on Anthropic models.
When Hostinger makes sense: you want a 1-click path with some AI credits bundled, and you're okay with a 24-month term. Operators who have migrated from self-hosted VPS to Hostinger's managed OpenClaw setup consistently highlight two things: the deployment and ongoing maintenance work disappears, and the bundled AI credits end up being a bigger deal than they expected for light-to-moderate usage.
When it doesn't: you want month-to-month pricing, zero inference markup, or BYOK across more than four providers. That renewal rate — $14.99/mo after the intro term — is a real cost that rarely shows up in the first comparison.
OVHcloud — enterprise infrastructure, DIY everything
OVHcloud has the strongest infrastructure story in the cheap VPS category: anti-DDoS on every plan, NVMe SSD, and global data centers with genuine peering. The problem is they don't meet OpenClaw halfway.
From the OVHcloud alternative page: OVHcloud provides enterprise-grade infra with anti-DDoS and global data centers — but it's full DIY with manual Docker/npm setup for OpenClaw.
When it makes sense: you already use OVH for other workloads, you need their anti-DDoS story, or you're deploying in a region (India, Singapore, Canada East) where other providers are weaker. Expect to write your own install scripts.
DigitalOcean — best docs, worst pricing
DigitalOcean is where first-time Linux users end up because its docs are outstanding. For OpenClaw, though, the $4/mo droplet is under-spec'd; the recommended spec is the $24/mo 4 GB / 2 vCPU Droplet, which makes it one of the most expensive cheap VPS options by the time you're comfortable running an agent on it.
From the DigitalOcean alternative page: DigitalOcean has the best documentation and community in the VPS category — but at ~$24/mo for the recommended spec with full DIY management, KiloClaw is cheaper and zero-maintenance.
When it makes sense: you already use Droplets for other workloads, or you want to graduate to their Cloudways managed layer for a more polished experience. The $200 new-account credit also makes it a zero-risk place to test an OpenClaw install for the first 60 days.
IONOS — cheapest on paper
IONOS wins pure spec-for-dollar with ISO 27001 data centers and DDoS protection from ~$2/mo. The OpenClaw problem is purely ecosystem: there is no template, no installer, no guide that's specific to them.
From the IONOS alternative page: IONOS offers the best price-to-resource ratio with ISO 27001 data centers — but they don't even have a 1-click OpenClaw template, so you're building from scratch.
When it makes sense: you only trust big-brand hosts, or you need ISO 27001 for a compliance box-tick at absurdly low prices. You'll spend a weekend on the install.
Oracle Cloud Free Tier, AWS Lightsail, Google Dev Cloud — honourable mentions
The Oracle Cloud free tier comes up regularly on r/oraclecloud from people wondering if it's viable for OpenClaw. Short answer: you can run inside the Always Free ARM Ampere A1 allowance (4 OCPUs / 24 GB RAM), and it's the only way to run OpenClaw genuinely for $0 — but Oracle reclaims idle instances aggressively, so you'll end up writing a cron job to keep yours active.
AWS Lightsail has an OpenClaw blueprint too, but r/VPS users describe its dashboard as overwhelming if you're not already comfortable with AWS. Early adopters on Google Dev Cloud report that it works but the experience is pretty rough — enough friction that most end up migrating off.
None of these are where most operators end up. They're fine for a tinkering weekend, not a production agent.
OpenClaw VPS providers — at a glance
| Provider | Starting price | Recommended spec for OpenClaw | OpenClaw template | Best for | Biggest catch |
|---|---|---|---|---|---|
| Hetzner | ~$4.99/mo | CPX22 — 2 vCPU / 4 GB | No (community) | Default pick for everyday agents | Capacity sell-outs, ID-verification signup |
| Contabo | ~$6/mo | VPS S / M — 4 vCPU / 8 GB | No | Heavy RAM, scraping, local models | Clunky UI, slower provisioning |
| Hostinger | $6.99/mo* | VPS w/ nexos.ai template | Yes (1-click) | Fastest "click to running agent" | 24-mo term, $14.99 renewal, ~10% Anthropic markup |
| OVHcloud | ~$4/mo | VPS Comfort | No | Anti-DDoS, global regions | Pure DIY install, docs gaps |
| DigitalOcean | ~$24/mo (rec.) | 4 GB / 2 vCPU Droplet | No | Best docs + community | Expensive at recommended spec |
| IONOS | ~$2/mo | VPS M | No | Cheapest by raw specs, ISO 27001 compliance | No OpenClaw ecosystem, DIY from zero |
| Oracle Free | $0 | ARM Ampere A1 free tier | No | Genuinely free, generous specs | Aggressive idle reclaim, steep UX |
* 24-month intro; renewal ~$14.99/mo.
Why a cheap OpenClaw VPS gets expensive fast
The VPS costs $5. The work is everything else. These are the pain points that show up again and again in Reddit threads — every single one is a thing you'd stop owning the minute you moved to a managed host.
1. Gateway binding and the "pairing required" wall
A top search result across r/openclaw and r/clawdbot is the fresh-VPS gateway connect failed: Error: pairing required error — the default install binds the gateway to loopback and the device configuration file is missing the operator.admin scope. The fix is a config edit (OPENCLAW_GATEWAY_BIND=lan, an explicit allowedOrigins, and correct device scopes), but you only find it after an hour of port-mapping and reverse-proxy debugging.
2. OAuth refresh storms
Self-hosting means owning every OAuth token in your integration list. Google Workspace caps apps at 100 refresh tokens and silently invalidates the oldest. GitHub's new granular tokens expire in seven days by default. The recurring community complaint: a single expired token can cascade into reinstalling OpenClaw, at which point you lose two weeks of configuration state unless you backed up the workspace directory.
3. Headless browser breakage
Ubuntu ships Chromium as a snap, and snap's AppArmor confinement fights OpenClaw's browser supervision. Multiple r/openclaw threads describe hours spent debugging Failed to start Chrome CDP errors before realising the snap-packaged Chromium is the culprit. Fix: uninstall the snap, install real chrome.deb, restart the gateway. You'll find this out the hard way.
4. Bot detection on datacenter IPs
Every major VPS range — Hetzner especially, but Contabo, DigitalOcean, and OVH too — is pre-classified by Cloudflare and friends. The OpenClaw community consensus is blunt: the moment your agent starts browsing, it hits bot-detection walls because headless Chromium is running from a known VPS IP range and most sites treat it like a scraper.
No amount of stealth plugins fully fixes this. Some operators route browser traffic through residential proxies; others host the browser component at home and keep the gateway on a VPS. Either way, it's another thing to build.
5. Security surface you now own
Running OpenClaw as root is fast and dangerous, and every community setup guide opens with a warning about it. You're responsible for disabling root SSH, disabling password auth, patching the kernel, rotating API keys, watching for CVEs in the OpenClaw Docker image (recent scans found thousands — see the OpenClaw Docker guide for details), and keeping Telegram/Slack tokens off disk in plaintext.
On a managed host, that entire list is someone else's problem.
When managed hosting beats a cheap VPS
Managed OpenClaw hosting is the cleaner version of the same idea most people are actually trying to reach with a VPS: an always-on agent, isolated from your laptop, that you don't have to babysit.
KiloClaw is managed OpenClaw hosting — an optimized, hosted, production-ready version of the OpenClaw framework. Setup takes under two minutes. Each tenant runs inside a dedicated Firecracker micro-VM (the same isolation AWS Lambda uses), with AES-256 encrypted credential vaults, no SSH access, tool allow-listing by default, and an independently audited security architecture.
Pricing is $9/month for hosting (or $8/mo on a 6-month term for $48 up front), with a 7-day free trial and AI inference billed separately at zero markup through Kilo Gateway's 500+ model catalog. You don't edit gateway.controlUi.allowedOrigins. You don't rotate OAuth tokens. You don't lose a weekend to snap-packaged Chromium.
For a category-by-category comparison of every managed OpenClaw provider — including the VPS shops with OpenClaw templates — see the managed OpenClaw alternatives guide.
When a VPS is still the right answer
Not every workload needs managed hosting. A self-hosted VPS is still a good pick if:
- You're a tinkerer who enjoys Ansible playbooks and wants an exact OpenClaw build pinned to disk.
- You're in an air-gapped or regulated environment and can't use a third-party cloud at all.
- You already run a home lab or company Kubernetes where one more VM is free.
- You need the biggest specs for the least money (Contabo, IONOS) because you're running heavy local workers on the same host.
- You want the VPS purely as an offsite dev box, not an always-on agent.
For everything else — Telegram bots that need to answer at 2 AM, Slack agents for your team, agents with OAuth into Google and GitHub and Notion — the VPS is a means to an end, and managed hosting is a shorter line to the same end.
Bottom line
If you're going to run OpenClaw on a VPS, the Reddit consensus is simple: Hetzner CPX22 at ~$6.99/mo if you can get one, Contabo if you want more specs per dollar, Hostinger if you want a click-through template and don't mind the lock-in. Start at 2 vCPU / 4 GB RAM. Set OPENCLAW_GATEWAY_BIND=lan. Install real Chrome, not the snap. Lock down SSH. Expect to lose a weekend.
If your goal was "always-on agent, no DevOps", the cheapest VPS isn't the cheapest path — it's the slowest. KiloClaw gets you there in under two minutes with Firecracker-VM isolation, managed OAuth, credential vaulting, and 500+ models at zero markup built in.
FAQ
What are the minimum VPS requirements for OpenClaw?
OpenClaw runs the gateway, a headless browser, and your messaging bridges — inference is offloaded to your model provider. A 2 vCPU / 2 GB RAM box with 20–40 GB NVMe SSD is enough for a single always-on agent. 2 vCPU / 4 GB is the comfortable everyday spec most operators land on (e.g. Hetzner CPX22). Step up to 4 vCPU / 8 GB only if you're running multiple agents, heavy browser scraping, or a local LLM on the same host.
What is the best VPS for OpenClaw?
For most operators on Reddit, Hetzner (CX22 or CPX22) is the default pick — it's cheap, fast to provision, and has the most community guides. Contabo wins on raw specs per dollar when you need big RAM. Hostinger wins on ease of setup because their OpenClaw template is a true 1-click install, at the cost of a 24-month term and ~10% inference markup. If you want no VPS at all, a managed host like KiloClaw is cheaper than a DIY VPS once you include your time.
What's the cheapest OpenClaw VPS that actually works?
Under $5/mo: a Hetzner CX22 (~$4.99/mo) or IONOS VPS (from ~$2/mo). Hetzner is the community default because the OpenClaw ecosystem — install scripts, Reddit guides, CLI tools — assumes it. IONOS is cheaper on paper but has no OpenClaw-specific tooling. Oracle Cloud's Always Free ARM Ampere A1 tier is genuinely $0 if you're willing to fight Oracle's idle-reclaim policy. Note: the VPS is rarely your biggest OpenClaw cost — model usage usually is.
Is Hetzner the best VPS for OpenClaw?
For most operators, yes — Hetzner is the single most recommended VPS for OpenClaw on Reddit, and the short community verdict is simply that it's a fine choice. The CPX22 ($6.99/mo, 2 vCPU / 4 GB) is the spec most operators recommend. The catches: Hetzner has had capacity sell-outs during OpenClaw spikes, requires ID verification at signup for some regions, and its IP range is known to bot-detection services — so headless Chrome browsing can hit Cloudflare walls more often than from a residential IP. None of those are deal-breakers; all of them are real.
Does Hetzner rate-limit OpenClaw?
Hetzner itself doesn't rate-limit OpenClaw traffic, but third-party sites do rate-limit Hetzner IPs because OpenClaw agents share datacenter IP space with every other scraper and bot. Operators report Cloudflare challenges and outright bot-detection blocks when the agent's headless browser hits sites from a Hetzner IP. Fixes include routing browser traffic through a residential proxy, hosting the browser component separately, or using a managed host that manages IP reputation for you.
Is Contabo good for OpenClaw?
Yes, especially if you need more RAM than Hetzner's cheap tiers offer or you're running multiple agents on one box. The community summary is that Contabo is very cheap and works well, though the UI is dated. Its advantage is raw resources per dollar (up to 16 vCPU / 64 GB RAM / 500 GB NVMe). Its disadvantages are a dated control panel, slower provisioning than Hetzner, and occasional noisy-neighbour network performance.
Is Hostinger VPS good for OpenClaw?
Hostinger has the fastest setup path because their OpenClaw template (backed by nexos.ai) is a real 1-click install, not a DIY job. The community feedback is consistent — a fine, cheap experience, especially for non-technical buyers. The trade-offs: their $6.99/mo price requires a 24-month commitment, the renewal rate is ~$14.99/mo, and inference through their nexos.ai integration carries ~10% markup on Anthropic models. For month-to-month pricing or zero-markup inference, look at DIY on Hetzner or a managed host with its own gateway.
Should I use DigitalOcean for OpenClaw?
Only if you're already on it. DigitalOcean's $4/mo basic droplet is under-spec'd for OpenClaw; the recommended 4 GB / 2 vCPU Droplet is ~$24/mo, which makes it one of the most expensive "cheap" VPS options. Its redeeming feature is docs — DigitalOcean has the best beginner documentation and community in the VPS category. For real OpenClaw workloads, Hetzner or Contabo give you 3–4× the resources for the same money.
Can I run OpenClaw on Oracle Cloud's free tier?
Yes, within the Always Free ARM Ampere A1 allowance (up to 4 OCPUs and 24 GB RAM across your free instances). That's more than enough for a single OpenClaw gateway. The catch is Oracle's idle-reclaim policy: they reclaim instances that look unused, so you'll need to generate enough baseline activity to stay off the reclaim list. Treat it as a "run for free while I'm experimenting" option, not a production agent home.
Is managed OpenClaw hosting cheaper than a VPS?
Often, yes — once you count your time and your inference bill. A bare VPS looks cheapest on paper ($5–10/mo), but you own updates, OAuth rotation, security patching, bot-detection workarounds, and gateway debugging. Managed OpenClaw hosting like KiloClaw runs $9/mo with AI inference billed separately at zero markup, versus Hostinger's ~10% markup on Anthropic or OpenClaw Cloud's $39.90/mo. For most operators, the break-even is the first weekend they'd otherwise spend fixing a broken gateway. See how much OpenClaw costs for the full breakdown.