Deploy openclaw.ai on Vultr
Vultr offers globally distributed cloud compute suitable for an always-on OpenClaw Gateway.
Global Reach
Choose a current location close to you for lower latency. Region availability, hardware, and pricing vary over time.
Check current Vultr offers
Review current regional availability, pricing, and new-customer promotions.
Get Started âđ Prerequisites
Create & Connect to Your Server
Log in to the Vultr Customer Portal and deploy a new Cloud Compute instance:
- Click Deploy + â Deploy New Server
- Choose Cloud Compute â Shared CPU
- Select your preferred server location (pick the region closest to you)
- Under Server Image, select Ubuntu 24.04 LTS or a newer supported LTS release
- Choose a current Shared CPU plan with at least 2 GB RAM
- Under SSH Keys, add your public key (recommended) or use the auto-generated root password
- Click Deploy Now
Wait for the server status to show Running (usually 1â2 minutes), then connect:
# Replace with your server's IP from the Vultr dashboard
ssh root@your-server-ip
Finding Your IP
Your server's IP address is shown on the Vultr dashboard under your instance details. You can also copy it from the Server Information page.
System Update & Dependencies
Update the package index and upgrade all installed packages to their latest versions:
sudo apt update && sudo apt upgrade -y
Install supported Node.js version
openclaw.ai requires Node.js 22.22.3+, 24.15+, or 25.9+ (installer defaults to Node 26). Install it from the official NodeSource repository:
curl -fsSL https://deb.nodesource.com/setup_26.x | sudo -E bash -
sudo apt-get install -y nodejs
node --version # Should show v26.x.x
Install openclaw.ai
Run the official one-line installer:
curl -fsSL https://openclaw.ai/install.sh | bash
Run Onboarding
Launch the interactive onboarding wizard. The --install-daemon flag automatically configures openclaw.ai to run as a background service:
openclaw onboard --install-daemon
The wizard will walk you through:
- Authentication setup (API keys for your LLM provider)
- Gateway configuration (port, allowed origins)
- Optional channel setup (Slack, Discord, etc.)
Verify Installation
Confirm everything is running correctly:
# Check system configuration
openclaw doctor
# Verify the gateway is healthy
openclaw health
# Print the authenticated dashboard URL
openclaw dashboard --no-open
# On your local computer, forward the private Gateway port
ssh -N -L 18789:127.0.0.1:18789 root@your-server-ip
# Then open http://127.0.0.1:18789
Configure Vultr Firewall
Create a Vultr Firewall Group for SSH while keeping the Gateway private:
- In the Vultr dashboard, go to Products â Network â Firewall
- Click Add Firewall Group and give it a name (e.g.,
openclaw-fw) - Add the following Inbound Rules:
Protocol Port Source Description
TCP 22 My IP SSH access
- Go back to your instance â Settings â Firewall and attach the firewall group
Keep the Gateway Private
Do not add a public rule for port 18789. Keep the default loopback bind and use the SSH tunnel from Step 6.
Keep Running with systemd
The --install-daemon flag from Step 5 already set up a systemd user service. To check its status:
# Check gateway status via openclaw CLI
openclaw gateway status
# Or check directly via systemd
systemctl --user status openclaw-gateway
# View live logs
journalctl --user -u openclaw-gateway -f
The service will automatically restart on failure and start on boot.
đ§ Troubleshooting
If node --version shows an older version, the system Node.js may be taking priority. Remove it and reinstall:
sudo apt remove nodejs
curl -fsSL https://deb.nodesource.com/setup_26.x | sudo -E bash -
sudo apt-get install -y nodejs
Check the Gateway on the Vultr instance, then restart the tunnel on your local computer:
# On the Vultr instance
openclaw gateway status
ss -tlnp | grep 18789
# On your local computer
ssh -N -L 18789:127.0.0.1:18789 root@your-server-ip
The Vultr Firewall Group only needs SSH from your IP; port 18789 stays private.
Ensure your server status is Running in the Vultr dashboard. If you set up a Firewall Group, confirm port 22 is open for your IP. You can also use the Vultr web console as a fallback from the dashboard.
Ready to deploy? Get started with Vultr â
Was this helpful?