Intermediate ~25 minutes

Set Up OpenClaw on Vultr

This page applies the official clean-Ubuntu VPS flow to Vultr. OpenClaw docs mention Vultr in provider comparisons, but do not currently ship a dedicated Vultr walkthrough.

Prerequisites

  • A Vultr account or active VPS
  • A computer with internet access
  • About 25 minutes for provisioning + onboarding
Affiliate disclosure

Some links on this page are affiliate links. If you buy through them, we may earn a commission at no extra cost to you.

1Create a Vultr account

Plan to use a clean Ubuntu VPS, not a one-click app image.

See Vultr plans →

Official docs list 1 vCPU / 1GB RAM as the absolute minimum and 1-2 vCPU / 2GB+ as a safer starting point for a long-running gateway.

2Deploy a Server

In your Vultr dashboard, deploy a new server:

  1. Click Deploy New Server
  2. Choose a standard cloud compute plan
  3. Select a server location (choose the one closest to your users)
  4. Choose Ubuntu 24.04 LTS as the OS
  5. Start with a small plan and scale up only if you need more headroom
  6. Deploy the server and note its IP address

Vultr is workable, but this page is a provider adaptation rather than an official OpenClaw walkthrough.

3Connect to Your Server

Open a terminal and connect to your server via SSH:

bash
ssh root@YOUR_SERVER_IP

Replace YOUR_SERVER_IP with your actual server IP address. Enter the root password from your Vultr dashboard when prompted.

4Install OpenClaw CLI

Update the machine and install OpenClaw using the official installer:

bash
sudo apt update && sudo apt upgrade -y
curl -fsSL https://openclaw.ai/install.sh | bash
openclaw --version

5Run onboarding

Start the onboarding flow and install the Gateway service:

bash
openclaw onboard --install-daemon

Use onboarding to configure model auth, channels, and the gateway token.

6Open the dashboard securely

Prefer an SSH tunnel or Tailscale instead of exposing the Control UI publicly:

bash
ssh -N -L 18789:127.0.0.1:18789 root@YOUR_SERVER_IP
# Then open http://127.0.0.1:18789/ locally

7Verify the gateway and pair your first channel

Back on the server, confirm the service and reopen the dashboard link when needed:

bash
openclaw status
openclaw dashboard

Use `openclaw status` for a quick health check. If auth is required, paste the token into the Control UI settings.

Congratulations!

Recommended next steps:

  • Open the Control UI with `openclaw dashboard`
  • Connect your first channel or device
  • Back up `~/.openclaw` and use provider snapshots only as an extra recovery layer
  • Keep the dashboard private; SSH tunnel or Tailscale is safer than public exposure