Best VPS for OpenClaw in 2026: A Hosting Comparison

TL;DR: The best VPS for OpenClaw depends on your budget and location. For most users, Hetzner Cloud offers the best value with their CX22 plan (2 vCPUs, 4 GB RAM, 40 GB SSD) at about $4.50/month, meeting OpenClaw's minimum requirements. DigitalOcean and Linode offer friendlier dashboards at $24/month for comparable specs. AWS Lightsail ($12/month for 2 GB) is adequate for testing but tight for production. Vultr lands between Hetzner and DigitalOcean on both price and usability. For production deployments, we recommend 4 GB of RAM minimum and 8 GB for agents handling multiple service integrations. All providers support Ubuntu 22.04 or 24.04, which is the best-supported OS for OpenClaw's Docker stack. Don't run OpenClaw on shared hosting or serverless platforms. It needs a persistent, always-on server with root access and enough resources for Docker to run multiple containers simultaneously.

What kind of VPS does OpenClaw need?

A VPS (Virtual Private Server) for OpenClaw is a cloud-hosted Linux server where your autonomous AI agent runs continuously. Unlike standard web hosting, OpenClaw needs root access for Docker, enough memory for multiple containers, and 24/7 uptime for the agent runtime, memory store, web gateway, and tool integrations.

If you're new to OpenClaw, start with our complete guide for business leaders. If you're ready to install, our installation guide walks through the full process.

What are the minimum specs for hosting OpenClaw?

The table below reflects real-world deployments, not marketing copy from VPS providers. OpenClaw's Docker stack uses 1.5-3 GB of RAM at idle and spikes higher under load, so 4 GB works but leaves little headroom. 8 GB prevents the OOMKill crashes that plague undersized deployments.

| Spec | Minimum (Testing) | Recommended (Production) | Heavy Use (Multi-Agent) | |------|-------------------|--------------------------|------------------------| | RAM | 4 GB | 8 GB | 16 GB | | vCPUs | 2 | 4 | 4-8 | | Storage | 20 GB SSD | 50 GB SSD | 100 GB SSD | | Bandwidth | 1 TB/month | 2 TB/month | 4 TB/month | | OS | Ubuntu 22.04 LTS | Ubuntu 24.04 LTS | Ubuntu 24.04 LTS |

Which VPS providers work best for OpenClaw?

We evaluated five major providers on specs, pricing, reliability, and how well they work for OpenClaw deployments. Prices are as of March 2026. Each provider has distinct strengths, so the right choice depends on your priorities.

Hetzner Cloud: Best value

Hetzner consistently delivers the most server for the money. Their European roots (Nuremberg, Falkenstein, Helsinki) are supplemented by US locations in Ashburn and Hillsboro, with 20 TB of bandwidth included at every tier. Hourly billing means you only pay for what you use. The dashboard is functional rather than polished, support is email-only on cheaper plans, and there's no managed database add-on. But for developers comfortable with Linux who want to minimize hosting costs, nothing else comes close.

| Plan | vCPUs | RAM | Storage | Bandwidth | Price/mo | |------|-------|-----|---------|-----------|----------| | CX22 | 2 | 4 GB | 40 GB | 20 TB | ~$4.50 | | CX32 | 4 | 8 GB | 80 GB | 20 TB | ~$8.50 | | CX42 | 8 | 16 GB | 160 GB | 20 TB | ~$16.50 |

DigitalOcean: Best dashboard and documentation

| Plan | vCPUs | RAM | Storage | Bandwidth | Price/mo | |------|-------|-----|---------|-----------|----------| | Basic $12 | 1 | 2 GB | 50 GB | 2 TB | $12 | | Basic $24 | 2 | 4 GB | 80 GB | 4 TB | $24 | | Basic $48 | 4 | 8 GB | 160 GB | 5 TB | $48 |

DigitalOcean's strength is the experience around the server, not just the server itself. The documentation library and community tutorials are the best in the VPS market. The dashboard is clean and intuitive, with one-click Docker installation and multiple US data centers (New York, San Francisco, Atlanta). You pay 3-4x what Hetzner charges for equivalent specs, and the 2 GB plan is too small for production OpenClaw. But if you value a polished UI and community resources, the premium can be worth it.

Linode (Akamai Cloud): Solid middle ground

Linode is worth considering if you want US-based hosting with low latency to Nashville (their Atlanta data center is the closest option). Performance is reliable and the API is good. Since the Akamai acquisition, the dashboard has been in transition, and pricing matches DigitalOcean without the same depth of community resources. Here's how the plans compare:

| Plan | vCPUs | RAM | Storage | Bandwidth | Price/mo | |------|-------|-----|---------|-----------|----------| | Nanode | 1 | 2 GB | 50 GB | 2 TB | $12 | | Linode 4GB | 2 | 4 GB | 80 GB | 4 TB | $24 | | Linode 8GB | 4 | 8 GB | 160 GB | 5 TB | $48 |

Vultr: Price-performance sweet spot

| Plan | vCPUs | RAM | Storage | Bandwidth | Price/mo | |------|-------|-----|---------|-----------|----------| | Cloud Compute | 1 | 2 GB | 50 GB | 2 TB | $10 | | Cloud Compute | 2 | 4 GB | 100 GB | 3 TB | $20 | | Cloud Compute | 4 | 8 GB | 200 GB | 4 TB | $40 |

Vultr slots between Hetzner and DigitalOcean on both price and polish. With 32 data center locations worldwide, fast provisioning, and generous storage at every tier, it's a solid pick for users who want more than Hetzner's interface without paying DigitalOcean prices. Support responses can be slow, and community tutorials are limited compared to DigitalOcean.

AWS Lightsail: For AWS ecosystem users

If you're already in the AWS ecosystem, Lightsail offers simplified pricing (no surprise bills), a three-month free trial, and easy integration with services like S3 and Route 53. US-East-1 (N. Virginia) provides excellent connectivity. The tradeoff: it's less flexible than full EC2, offers fewer CPU options at each tier, and migrating to EC2 later is more work than switching VPS providers. The 2 GB tier is insufficient for production OpenClaw.

| Plan | vCPUs | RAM | Storage | Bandwidth | Price/mo | |------|-------|-----|---------|-----------|----------| | $12 | 2 | 2 GB | 60 GB | 3 TB | $12 | | $24 | 2 | 4 GB | 80 GB | 4 TB | $24 | | $48 | 2 | 8 GB | 160 GB | 5 TB | $48 |

What do we recommend?

For most OpenClaw deployments, the right VPS depends on where you fall on the budget-vs-convenience spectrum. Hetzner's CX32 (4 vCPUs, 8 GB RAM) at ~$8.50/month handles a single production agent with headroom, and the CX22 at $4.50/month works for testing. DigitalOcean's $24 plan (2 vCPUs, 4 GB RAM) is the pick if dashboard quality, documentation, and one-click Docker setup matter more than price. For production with growth plans, Vultr's $40 plan (4 vCPUs, 8 GB RAM, 200 GB storage) balances price, performance, and the storage headroom your agent's memory will need over time.

How do you set up OpenClaw on a VPS?

Setting up OpenClaw on a VPS takes about 30 minutes if you follow the steps below. This walkthrough uses Hetzner's CX32, our best-value recommendation, but the process is nearly identical on any provider once you have SSH access to an Ubuntu server.

1. Create your server

Sign up at Hetzner Cloud. Create a new project. Click "Add Server."

• Location: Ashburn (US East) or Hillsboro (US West) for US-based deployments
• Image: Ubuntu 24.04 LTS
• Type: CX32 (4 vCPU, 8 GB RAM)
• Networking: Enable IPv4
• SSH Key: Add your public key (strongly recommended over password auth)
• Name: Something like openclaw-prod

Click "Create." Your server will be ready in about 30 seconds.

2. Initial server configuration

SSH into your new server:

ssh root@YOUR_SERVER_IP

Run initial security setup:

# Update the system
apt update && apt upgrade -y

# Create a non-root user
adduser openclaw
usermod -aG sudo openclaw

# Set up SSH key for new user
mkdir -p /home/openclaw/.ssh
cp ~/.ssh/authorized_keys /home/openclaw/.ssh/
chown -R openclaw:openclaw /home/openclaw/.ssh

# Disable root SSH login
sed -i 's/PermitRootLogin yes/PermitRootLogin no/' /etc/ssh/sshd_config
systemctl restart sshd

# Set up firewall
ufw allow OpenSSH
ufw allow 443/tcp  # For HTTPS via reverse proxy
ufw enable

3. Install Docker

# Switch to your new user
su - openclaw

# Install Docker using the official script
curl -fsSL https://get.docker.com | sudo sh

# Add your user to the docker group
sudo usermod -aG docker $USER

# Log out and back in for group changes to take effect
exit
ssh openclaw@YOUR_SERVER_IP

# Verify installation
docker --version
docker compose version

4. Install OpenClaw

From here, follow our complete OpenClaw installation guide starting at Step 1. The guide covers cloning the repository, configuring environment variables, Docker Compose setup, OAuth configuration, and security hardening.

5. Set up a reverse proxy

Install Caddy for automatic HTTPS:

sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
sudo apt update
sudo apt install caddy

Configure Caddy to proxy to OpenClaw with basic authentication (and read our OpenClaw security guide for the full hardening checklist):

yourdomain.com {
    basicauth * {
        admin $2a$14$your_hashed_password_here
    }
    reverse_proxy localhost:3000
}

Caddy automatically provisions and renews Let's Encrypt TLS certificates. No manual certificate management required.

What about managed cloud services?

Managed platforms like Railway, Render, and Fly.io simplify deployment but add constraints that make them a poor fit for OpenClaw's multi-container architecture. Railway and Render struggle with multi-container orchestration and have unpredictable pricing under sustained workloads. Fly.io handles containers well, but OpenClaw's multi-service design means managing multiple Fly apps, which gets complicated fast. AWS ECS/Fargate is enterprise-grade but massive overkill for a single agent.

A VPS with Docker Compose remains the simplest, most cost-effective, and most predictable hosting for OpenClaw. Our OpenClaw Docker setup guide explains the multi-container architecture you'll be running on whichever provider you choose. You get full control, predictable billing, and no platform abstraction fighting against the multi-container architecture.

What does self-hosting actually cost?

VPS hosting is just one line item. The full monthly picture for a self-hosted OpenClaw agent often surprises people because the biggest cost isn't the server:

| Line Item | Monthly Cost | |-----------|-------------| | VPS hosting | $5-50 | | LLM tokens (OpenAI/Anthropic) | $50-500 | | Domain name (annualized) | ~$1 | | Your time (3-5 hrs/week at $200/hr) | $2,400-4,000 | | Total | $2,456-4,551 |

The real cost of autonomous AI agents is dominated by the time you spend maintaining them, not the hosting bill. Whether the DIY trade-off makes sense depends on how you value your time. We broke down that decision in detail in why you shouldn't set up OpenClaw yourself.

Related guides

• What Is OpenClaw? A Guide for Business Leaders -- understand what you're hosting before choosing a server
• How to Install OpenClaw: Complete 2026 Guide -- the full installation walkthrough once your VPS is ready
• OpenClaw Docker Setup: Container Config Explained -- configure the multi-container stack on your VPS
• AI Agent Costs: What They Do and Whether You Need One -- hosting is just one part of the total cost picture

Key takeaways

• Hetzner Cloud offers the best price-to-performance ratio, with production-ready plans starting at ~$8.50/month for 8 GB RAM.
• DigitalOcean and Linode charge 3-4x more than Hetzner but provide better dashboards, documentation, and community support.
• OpenClaw needs at least 4 GB of RAM for testing and 8 GB for production; anything less invites OOMKill crashes.
• A VPS with Docker Compose is simpler and more predictable than managed platforms like Railway, Render, or Fly.io for OpenClaw's multi-container stack.
• The real cost of self-hosting is your time (3-5 hours/week), not the $5-50/month server bill.
• Any US East Coast data center provides sub-50ms latency to Nashville; server location matters less than you'd expect.
• Start with Hetzner CX22 ($4.50/month) for testing, then scale up once you've validated your agent's workload.

Frequently asked questions

Can I run OpenClaw on a $5/month VPS?

Technically yes. Hetzner's CX22 at $4.50/month meets the bare minimum requirements with 4 GB of RAM. It works for a single agent with basic workflows. You'll hit memory pressure if you add multiple service integrations or run memory-intensive skills. Starting small and upgrading is a reasonable strategy for testing.

Should I pick a VPS location close to Nashville?

For OpenClaw, server location matters less than you might think. Your agent's latency-sensitive operations are API calls to LLM providers and service integrations (Gmail, Slack, etc.), not the connection between you and the server. Any US East Coast data center provides sub-50ms latency to Nashville. Ashburn (Virginia) or Atlanta are the closest options from most providers.

How do I migrate OpenClaw to a different VPS?

Back up your data volumes and .env file. On the new server, install Docker, clone OpenClaw, restore your .env, and copy the data volumes. Run docker compose up -d and verify. The entire migration takes under an hour if you've done it before. Test on the new server before shutting down the old one.

Do I need a domain name for OpenClaw?

Not strictly, but yes for any production deployment. A domain enables HTTPS (required for secure OAuth callbacks), gives you a stable address if you change servers, and looks professional. Any $10-15/year domain works. Point an A record at your VPS IP address. You'll also need a domain if you plan to use Telegram webhooks for messaging your agent.

Hosting is the easy part. Configuration, security hardening, OAuth setup, and ongoing maintenance are where the real time goes. If you want an agent that's deployed, secured, and managed without thinking about servers — that's what we do.