How to Deploy OpenClaw on DigitalOcean - Simple Droplet Setup

DigitalOcean is one of the fastest ways to get a plain Linux box online, and the OpenClaw docs keep the setup accordingly direct. Instead of a container-focused guide, this page walks through a clean Ubuntu 24.04 Droplet, Node.js 24, the OpenClaw installer, and the onboarding wizard with daemon installation.

What the official docs support

The official guide is intentionally minimal and operator-friendly. You create a Droplet, install Node.js 24, run the OpenClaw installer, use openclaw onboard --install-daemon, and then choose how to reach the dashboard: SSH tunnel, Tailscale Serve, or tailnet bind. There is also a documented swap step for the 1 GB tier.

This route is good when you want the shortest path to a persistent gateway and you do not need to standardize on Docker from day one. It is especially attractive for solo operators or small teams who want a cheap VPS and are happy to let the onboarding wizard handle the first round of auth, channels, and daemon setup.

What you need first

• A DigitalOcean account and a new Ubuntu 24.04 Droplet
• SSH key or password access
• About 20 minutes for install and onboarding
• Enough RAM planning for your chosen workload, especially on 1 GB plans

Recommended setup flow

The clean path is one fresh Droplet, one installer run, and one secure access method to the dashboard.

1. Create the Droplet with Ubuntu 24.04 LTS, a small regular plan such as 1 vCPU and 1 GB RAM, and SSH-key auth if possible. The docs explicitly recommend a clean base image rather than a random Marketplace one-click image.
2. SSH in, update the system, install Node.js 24 from NodeSource, and run the OpenClaw install script. Finish by checking openclaw --version so you know the binary landed correctly.
3. Run openclaw onboard --install-daemon. The docs describe this as the wizard that handles model auth, channel setup, gateway token generation, and systemd user daemon installation in one pass.
4. If you chose a 1 GB Droplet, add the documented 2 GB swapfile before you get ambitious with channels or local workloads. That extra swap is cheap insurance against out-of-memory failures on tiny plans.
5. Choose your access method. SSH tunnel is the simplest, Tailscale Serve gives you tailnet HTTPS, and tailnet bind is a lighter-weight option when you do not need Serve. Then verify with openclaw status, systemctl --user status openclaw-gateway.service, and journalctl logs.

ssh root@YOUR_DROPLET_IP
apt update && apt upgrade -y
curl -fsSL https://deb.nodesource.com/setup_24.x | bash -
apt install -y nodejs
curl -fsSL https://openclaw.ai/install.sh | bash

Access, safety, and operational notes

The docs remind you that the gateway binds to loopback by default, which is a helpful safe default. SSH tunnel access keeps things simple, while Tailscale paths give you remote reach without casually opening the dashboard to the internet.

The swap recommendation is not fluff. On a 1 GB Droplet, it is one of the clearest documented ways to make a tiny instance behave a little more predictably, especially if you are using heavier tools or multiple channels. If the box still struggles, the docs suggest API-based models or a larger plan.

How to verify it is working

After onboarding, verify status from the shell and from your browser. Then send a message from one connected channel and watch journalctl --user -u openclaw-gateway.service -f so you know both the daemon and the chat path are healthy.

Common gotchas

• Use a clean Ubuntu image, not an unreviewed third-party one-click image
• Small 1 GB Droplets benefit from the documented swapfile step
• The dashboard is meant to stay private, reached through SSH or Tailscale

If you want the operator version with tighter rollout checklists, safer defaults, and more production patterns, The OpenClaw Playbook is the easiest shortcut.