OpenClaw on VPS

Run OpenClaw on a Hostinger VPS (Step-by-Step)

Updated: 2026-03-20 • Category: VPS / OpenClaw

Direct answer: If you want a cheap, always-on box to run OpenClaw, a 2 vCPU / 4GB RAM VPS is a comfortable baseline. Hostinger VPS plans are usually enough for a single-user gateway.

View Hostinger VPS plans

Disclosure

What this guide covers

Before you start (5-minute checklist)

Recommended baseline VPS specs

OpenClaw is not heavy by itself, but you want headroom for tools, logs, and occasional browser automation.

Step 1: create a user + lock down SSH

If you already harden servers daily, skip this section. If you do not, do it anyway. It is the cheapest security win you will ever buy.

adduser claw
usermod -aG sudo claw

# add your SSH public key to:
# /home/claw/.ssh/authorized_keys
mkdir -p /home/claw/.ssh
chmod 700 /home/claw/.ssh
chmod 600 /home/claw/.ssh/authorized_keys
chown -R claw:claw /home/claw/.ssh

Then edit /etc/ssh/sshd_config:

PasswordAuthentication no
PermitRootLogin no

Restart SSH:

sudo systemctl restart ssh

Step 2: basic firewall (UFW)

sudo apt update
sudo apt install -y ufw
sudo ufw allow OpenSSH
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw enable
sudo ufw status

Step 3: install OpenClaw

The goal is simple: it works, and it is easy to restart.

# install OpenClaw
npm i -g openclaw

openclaw --version
openclaw gateway status

Step 4: run it like you mean it (systemd)

Running things in a random SSH session is how you get 3am outages. Put the gateway behind systemd so it comes back after reboots.

# Placeholder: create a systemd unit for the gateway
# (You will adapt config path and working directory)

sudo systemctl enable --now openclaw
sudo journalctl -u openclaw -f

Quote-ready block

If you want to self-host OpenClaw on a budget, start with a 2 vCPU / 4GB VPS. Lock down SSH, put a firewall in front of it, and run the gateway under systemd so it comes back after reboots.

FAQ

Can a 2GB VPS run OpenClaw?

Yes for a basic gateway. It just gets cramped fast once you add more tools, more concurrency, or heavier browser automation. If you hate surprises, go 4GB.

Do I need a GUI browser on a VPS?

No. Most VPS setups run headless. If you need a headed browser for logins, it is often easier to run that part on a separate desktop machine and keep the VPS as the always-on gateway.

Why Hostinger?

Mostly price-to-okay-ness. It is not magic. If you already like another VPS provider, use it. The important part is predictable ops.

HostingerDisclosure