Best VPS for OpenClaw on a Budget

Anything cheaper than ~$6/month either reduces one of these (1 GB RAM, 25 GB disk, weak CPU) or uses OpenVZ virtualization (less isolation). For OpenClaw, avoid OpenVZ — the memory overcommit can cause OOM kills under load.

Hostinger VPS plans for OpenClaw

Hostinger's KVM line is solid budget VPS with dedicated resources and full root access. Here is how they stack for OpenClaw:

Recommendation: Start with KVM 1 if you are just deploying one OpenClaw instance. Upgrade to KVM 2 if you plan to run additional services (PostgreSQL, Redis, multiple Docker containers) or expect higher agent traffic.

If you are a new customer, use this link to get the best available price — Hostinger frequently runs promos that drop the first term by 50% or more.

Setup costs beyond the VPS

The VPS price is not the whole story. Here are the other things you might need:

Total first-year cost estimate: ~$80–100 if you include domain and basic monitoring. That is still cheaper than managed SaaS alternatives that charge $30–50/month for a fraction of the control.

Step-by-step: get OpenClaw running on a new VPS

These commands assume you just provisioned a fresh Ubuntu 22.04 VPS with root SSH access.

1. Update the system

apt update && apt upgrade -y
apt install -y curl wget gnupg2 ca-certificates lsb-release

2. Install Node.js 18+

Ubuntu 22.04's default Node is too old. Use NodeSource:

curl -fsSL https://deb.nodesource.com/setup_20.x | bash -
apt install -y nodejs

3. Create a dedicated user

Never run OpenClaw as root:

useradd --system --shell /usr/sbin/nologin --create-home --home-dir /home/openclaw openclaw
mkdir -p /home/openclaw/.openclaw
chown -R openclaw:openclaw /home/openclaw/.openclaw

4. Install OpenClaw

As the openclaw user:

sudo -u openclaw -i
cd ~
npm install -g @openclaw/cli
openclaw init

Follow the init prompts to set up your gateway token and API keys. The workspace is now in /home/openclaw/.openclaw/workspace.

5. Install and configure Caddy

Caddy is the easiest reverse proxy with auto-TLS. One command:

curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/caddy-stable-archive-keyring.gpg] https://dl.cloudsmith.io/public/caddy/stable/deb/debian any-version main" | sudo tee /etc/apt/sources.list.d/caddy-stable.list
apt update
apt install caddy

Edit /etc/caddy/Caddyfile to proxy to OpenClaw:

your-domain.com {
    reverse_proxy localhost:8080
    file_server
}

Reload Caddy:

systemctl reload caddy

Caddy will automatically obtain and renew an SSL certificate from Let's Encrypt.

6. Create a systemd service for OpenClaw

Save /etc/systemd/system/openclaw.service:

[Unit]
Description=OpenClaw AI Agent Gateway
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=openclaw
Group=openclaw
WorkingDirectory=/home/openclaw/.openclaw/workspace

# If you have a .env file with secrets
EnvironmentFile=/etc/openclaw/openclaw.env

ExecStart=/usr/local/bin/openclaw gateway start

TimeoutStopSec=15
Restart=on-failure
RestartSec=5s
StartLimitIntervalSec=60
StartLimitBurst=5

StandardOutput=journal
StandardError=journal
SyslogIdentifier=openclaw

NoNewPrivileges=yes
PrivateTmp=yes
ProtectSystem=full
ProtectHome=read-only
ReadWritePaths=/home/openclaw/.openclaw

[Install]
WantedBy=multi-user.target

Then enable and start:

systemctl daemon-reload
systemctl enable --now openclaw
systemctl status openclaw

Common pitfalls on cheap VPS

Pitfall 1 — Forgetting to open the firewall

UFW is installed by default on Ubuntu. You need to allow HTTP/HTTPS (ports 80, 443) for Let's Encrypt and for Caddy to serve traffic:

ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

If you skip this, Caddy cannot get SSL certs (it needs port 80) and your site stays inaccessible.

Pitfall 2 — Running out of RAM on 2 GB plans

If you stubbornly try to run on a 2 GB VPS, you will hit swap and everything will slow to a crawl. The numbers above are not theoretical — OpenClaw + Caddy + OS + Docker (if used) add up fast.

Fix: either upgrade to 4 GB or aggressively prune services. Disable Docker if you are not using it. Shrink PostgreSQL buffers. But honestly, just get the 4 GB plan — it costs ~$3/month more and saves hours of headdesk.

Pitfall 3 — letting logs fill the disk

Journald and Docker can consume gigabytes if left unchecked. Set up log rotation:

For journald, limit to 100 MB:

echo "SystemMaxUse=100M" | sudo tee -a /etc/systemd/journald.conf
systemctl restart systemd-journald

For Docker (if used), add to /etc/docker/daemon.json:

{
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "10m",
    "max-file": "3"
  }
}

Then restart Docker: systemctl restart docker.

Pitfall 4 — forgetting automatic security updates

On a headless VPS, you are the sysadmin. Enable unattended upgrades:

Check that it is active: systemctl status unattended-upgrades. This keeps your OS patched without manual SSH sessions every week.

When to upgrade from KVM 1

Upgrade to KVM 2 or higher when you see these signs:

• Consistently less than 20% free RAM (check free -h)
• Swap usage above 50% for extended periods (check swapon --show)
• OpenClaw latency increases or agents time out under normal load
• You want to run additional services (monitoring agent, extra databases, CI runner)
• You plan to host multiple OpenClaw workspaces on the same box (multi-tenancy)

The jump from 4 GB to 8 GB is not just double the RAM — it is the difference between anxiously watching memory and forgetting it exists. For an extra ~$3/month on Hostinger, that peace of mind is worth it.

Alternative budget VPS options

Hostinger is solid, but here are other providers in the same price bracket that work for OpenClaw:

• DigitalOcean Droplet — $6/month for 1 GB / 1 vCPU / 25 GB; RAM is too low, get the $12 plan (2 GB) minimum.
• Linode — $10/month for 2 GB / 1 vCPU / 50 GB; good network, simple pricing.
• Vultr — $6/month for 1 GB / 1 vCPU / 25 GB; same RAM issue as DO, their $12 plan is the entry point.
• Hetzner CX11 — €4.51/month (~$5) for 2 GB / 1 vCPU / 20 GB; excellent price, but requires ID verification and EU-based support.

Why stick with Hostinger? For a first VPS, the control panel is beginner-friendly, IPv6 is enabled, and the KVM virtualization is reliable. If you already have a Hostinger account for domain registration, keeping everything in one place simplifies billing and support.

What is the absolute cheapest VPS that can run OpenClaw?

The KVM 1 plan (1 vCPU / 4 GB RAM / 50 GB SSD) at ~$5.99/mo is the practical minimum. OpenClaw itself uses 150-300 MB idle, but you need headroom for a reverse proxy, SSL, and occasional spikes. Under 4 GB you will be living on swap and that gets painful fast.

Can I run OpenClaw on a $2-3/mo VPS?

Technically yes, but not comfortably. Those plans usually have 1 GB RAM or less, shared CPU, and no SSD guarantees. OpenClaw plus Nginx/Caddy plus the OS will leave you with <500 MB for your actual workload — you will hit swap constantly and performance will be sluggish. For a hobby tinker, it works; for anything serious, it is false economy.

Do I need a reverse proxy if I only run OpenClaw?

Yes, even with a single app. A reverse proxy (Caddy or Nginx) handles SSL termination, HTTP/2, and gives you a single port to firewall. Caddy's automatic TLS makes it especially easy: one command and you have HTTPS with zero manual cert management. Skipping the proxy means OpenClaw handles TLS directly, which works but gives you less flexibility later if you add more services.

What OS should I choose for OpenClaw on a budget VPS?

Ubuntu 22.04 LTS or Debian 12 — both are stable, have long-term support, and package Node.js 18+. Ubuntu tends to have more tutorials; Debian is slightly more minimal. Avoid Alpine unless you are comfortable debugging musl libc issues; some Node modules expect glibc.

How much disk space does OpenClaw actually need?

The OpenClaw workspace itself is ~200-500 MB including Node modules. Your logs, memory files, and uploaded media will grow over time. Plan for at least 10 GB total, with 20+ GB if you expect to store images, run backups, or keep Docker images. The 50 GB SSD on Hostinger's KVM 1 is plenty for a single deployment.

Is it worth going with a managed hosting plan to save time?

For OpenClaw, managed hosting rarely makes sense — the whole point is self-hosting control. Managed WordPress is irrelevant; you need a VPS. The only exception is if you want a pre-configured Node.js platform (like Heroku or Railway) but those cost more and give you less control than a basic VPS.

Related reads

• Run OpenClaw on a Hostinger VPS
• Which VPS plan is enough?
• VPS vs cloud hosting for Docker
• First VPS setup checklist