OpenClaw VPS & Hosting: Docker Setup Guide (2026)

Picking the Right OpenClaw VPS

OpenClaw isn't a web app you sign up for. It's software that runs on a server — your server.

If you followed our beginner's tutorial, you probably ran OpenClaw on your laptop to test it. That works fine for poking around. But the moment you want scheduled posts, an always-on Telegram bot, or anything that needs to run while you sleep — you need a VPS.

A VPS (Virtual Private Server) is just a computer in a data center that stays on 24/7. You rent it by the month. Prices start around $4.

This guide covers the full OpenClaw VPS setup: what specs you need, which providers are worth it, the complete Docker installation, and a real cost breakdown. We'll also be straight about when self-hosting makes sense and when PostClaw is the smarter call.

Hardware Requirements

OpenClaw isn't resource-hungry. Here's what it actually needs:

• RAM: 2GB minimum, 4GB recommended. Each skill adds a bit of overhead, and if you're running Content Forge alongside Social Poster and Schedule Bot, 2GB gets tight.
• CPU: 2 vCPUs is plenty. OpenClaw spends most of its time waiting for API responses, not doing heavy computation.
• Storage: 20GB SSD minimum. Docker images eat about 2-3GB. Logs and conversation data grow slowly — you won't hit 20GB for months.
• Bandwidth: 1TB/month is more than enough. API calls are tiny payloads.
• OS: Ubuntu 22.04 or 24.04 LTS. Debian works too. Anything that runs Docker.

That cheap Hetzner box? It handles OpenClaw without breaking a sweat.

Best VPS Providers for OpenClaw Hosting

I've tested OpenClaw on all of these. Here's what matters in practice.

Hetzner — Best value, full stop. Their CX22 plan gives you 2 vCPUs, 4GB RAM, and 40GB SSD for $4.35/month. Datacenters in Germany, Finland, and Ashburn (Virginia). Only downside: no US West Coast or Asian servers yet.

DigitalOcean — Most beginner-friendly. The $12/month droplet gets you 2GB RAM with a clean dashboard and solid docs. Their one-click Docker image saves about 10 minutes of setup. You're paying extra for the polish, but it's genuinely nice.

Vultr — Good middle ground. Same $12/month for 2GB RAM, but with servers in 32 locations worldwide. Slightly better global network performance in my testing.

Contabo — Cheapest raw specs. 8GB RAM for $7/month. But the network is noticeably slower and support tickets take days. Fine if you're penny-pinching and don't mind the occasional sluggishness.

Oracle Cloud Free Tier — An ARM instance with 4 vCPUs and 24GB RAM, completely free. Sounds too good. It is — you'll spend days refreshing the provisioning page trying to actually get one. If you land it, great for OpenClaw. But don't count on it.

My pick: Hetzner CX22 if you're in Europe or US East Coast. DigitalOcean $12 droplet if you want the smoothest setup experience and don't mind paying a bit more.

Installing OpenClaw with Docker: Step by Step

This walks through a fresh Ubuntu server. If you're on a different distro, the Docker commands are identical — only the package manager changes.

Step 1: SSH Into Your Server

ssh root@your-server-ip

First time connecting? You'll get a fingerprint warning. Type yes. Then either set a strong password or (better) add your SSH key.

Step 2: Install Docker

sudo apt update && sudo apt upgrade -y
sudo apt install docker.io docker-compose-plugin -y
sudo systemctl enable docker && sudo systemctl start docker

Verify both installed:

docker --version
docker compose version

Both should print version numbers. If either fails, your apt sources might be stale — run sudo apt update again.

Step 3: Create the OpenClaw Directory

mkdir -p /opt/openclaw && cd /opt/openclaw

Step 4: Write the Docker Compose File

nano docker-compose.yml

Paste this:

version: '3.8'

services:
openclaw:
image: openclaw/openclaw:latest
container_name: openclaw
restart: unless-stopped
ports:
- "3000:3000"
volumes:
- ./data:/app/data
- ./config:/app/config
env_file:
- .env
logging:
driver: "json-file"
options:
max-size: "10m"
max-file: "3"

Save with Ctrl+O, exit with Ctrl+X.

Step 5: Add Your API Keys

nano .env

# AI Model (pick at least one)
ANTHROPIC_API_KEY=sk-ant-your-key-here
# OPENAI_API_KEY=sk-your-key-here

# Telegram Bot
TELEGRAM_BOT_TOKEN=your-bot-token-from-botfather

# Server
PORT=3000
NODE_ENV=production

Get a Telegram bot token from @BotFather on Telegram — takes 30 seconds.

Step 6: Launch

docker compose up -d

Done. OpenClaw is running.

Check the logs to make sure it started clean:

docker compose logs -f

You should see startup messages and a "ready" confirmation. Ctrl+C exits the log stream — the container keeps running in the background.

Step 7: Test It

Message your Telegram bot. Send anything — "hello" works. If it responds, you're live.

No response? Check three things:

1. Bot token is correct in .env
2. Port 3000 isn't blocked by your firewall
3. Logs show no error messages (docker compose logs --tail 50)

What Each Docker Compose Setting Does

If you copied the config and it's working, skip this. If you want to understand what you pasted — or customize it — read on.

image: openclaw/openclaw:latest — Pulls the official Docker image. The latest tag tracks the most recent stable release. Pin to a specific version (like openclaw/openclaw:2.4.1) if you want predictable updates.

restart: unless-stopped — Automatic restart on crash or server reboot. "Unless-stopped" means Docker won't restart it if you manually shut it down with docker compose down. This is the behavior you want.

ports: "3000:3000" — Maps port 3000 on your server to port 3000 inside the container. If something else uses 3000, change the left number (e.g., "3001:3000").

volumes — This is critical. These two lines persist your data between container restarts:

• ./data:/app/data — Brand memory, conversations, scheduled tasks, skill data
• ./config:/app/config — Skill configurations and platform credentials

Without volumes, every docker compose down would wipe your data. Don't remove these.

env_file: .env — Loads API keys from a separate file instead of hardcoding them in the compose file. Cleaner and slightly more secure.

logging — Caps log files at 10MB with 3 rotations (30MB max total). Without this, Docker logs grow until your disk is full. I learned this the hard way on a Saturday morning.

Installing Skills on Your VPS

OpenClaw without skills is a brain without hands. For social media specifically, you want three skills — the same ones covered in our OpenClaw for social media guide:

docker compose exec openclaw openclaw skills install social-poster
docker compose exec openclaw openclaw skills install content-forge
docker compose exec openclaw openclaw skills install schedule-bot

Verify what's installed:

docker compose exec openclaw openclaw skills list

Social Poster handles publishing to platforms. Content Forge generates platform-adapted content from your prompts. Schedule Bot adds timing and calendar features.

For the full rundown of which skills do what, see our guide to OpenClaw skills for marketing.

Domain and SSL Setup

This part is optional. OpenClaw works fine on a raw IP address. But if you want a clean URL like openclaw.yourdomain.com with HTTPS encryption, here's the setup.

Install Nginx and Certbot:

sudo apt install nginx certbot python3-certbot-nginx -y

Create an Nginx config:

sudo nano /etc/nginx/sites-available/openclaw

server {
listen 80;
server_name openclaw.yourdomain.com;

location / {
proxy_pass http://localhost:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_cache_bypass $http_upgrade;
}
}

Enable the site and get a free SSL certificate:

sudo ln -s /etc/nginx/sites-available/openclaw /etc/nginx/sites-enabled/
sudo nginx -t && sudo systemctl reload nginx
sudo certbot --nginx -d openclaw.yourdomain.com

Certbot handles SSL automatically, including renewals. HTTPS in under a minute.

Point your domain's DNS A record to your server's IP address first. Without that, Certbot will fail.

One thing worth noting: the Telegram bot doesn't need a domain. It talks through Telegram's servers, not yours. A domain is mainly useful for the web dashboard and admin interface.

Maintenance: Updates, Backups, and Monitoring

Self-hosting means self-maintaining. Here's what that looks like week to week.

Updating OpenClaw

cd /opt/openclaw
docker compose pull
docker compose up -d

Pulls the latest image and restarts. Your data and config survive because they're in mounted volumes.

OpenClaw ships updates roughly every two weeks. Not every update is critical — check the release notes before updating a production instance.

Backups

Two things matter: your data directory and your .env file.

tar -czf openclaw-backup-$(date +%Y%m%d).tar.gz data/ config/ .env docker-compose.yml

Run this weekly. Store the backup somewhere off-server — your laptop, an S3 bucket, a different VPS. A backup on the same server as your data isn't really a backup.

Losing data/ means losing brand memory, conversations, and scheduled tasks. Losing .env means re-entering all your API keys. Both are fixable, but annoying enough that you should avoid it.

Basic Monitoring

Quick health check:

docker compose ps

"Up" with a runtime = good. "Restarting" or "Exit" = check the logs.

For a personal OpenClaw instance, manually checking once a day is enough. If you want automated alerts, a simple cron job that hits the health endpoint and sends you a notification on failure does the trick.

Firewall

Lock down your VPS. Only three ports need to be open:

sudo ufw allow 22/tcp # SSH access
sudo ufw allow 80/tcp # HTTP (redirects to HTTPS)
sudo ufw allow 443/tcp # HTTPS
sudo ufw enable

If you skipped the domain/SSL setup, replace 80 and 443 with 3000. Don't leave ports open that nothing is listening on.

The Real Cost of Self-Hosting OpenClaw

The software is free. Everything else isn't. Here's the actual breakdown.

Monthly Costs

Item | Cost | Notes

VPS (Hetzner CX22) | $4.35 | 2 vCPU, 4GB RAM

AI API (Claude or GPT-4) | $10-30 | Depends on usage

Domain (optional) | ~$1 | ~$12/year averaged

**Total** | **$15-35/month** |

On DigitalOcean, the VPS jumps to $12/month, pushing the total to $22-42/month. Heavy users who post to 10+ platforms multiple times daily might hit $40-50/month in API costs alone. But most people land between $15 and $30.

The Time Cost

This is the part people underestimate.

• Initial setup: 1-3 hours depending on your comfort with terminals
• Connecting social media APIs: 1-2 hours (each platform has its own developer portal dance)
• Weekly maintenance: 15-30 minutes for updates, log checks, occasional troubleshooting
• Fixing things when they break: unpredictable, maybe once or twice a month

If you enjoy server management, this is fine — maybe even fun. If you'd rather not think about Docker containers or API key rotation, it's a real cost on top of the dollars.

Self-Host or Use PostClaw?

Honest comparison time.

Self-host OpenClaw if you:

• Want it for more than social media — research, coding, DevOps, custom workflows
• Already run a VPS for other projects (marginal cost is just the API)
• Enjoy configuring and tinkering with server setups
• Want maximum control over prompts, skills, and data
• Prefer spending time over money

Use PostClaw if you:

• Only need social media management
• Don't want to touch Docker, SSH, or API portals
• Value setup speed over customization
• Would rather pay $29/month than spend an afternoon on server config
• Want 13 platforms connected through a dashboard instead of individual API keys

PostClaw runs OpenClaw under the hood. Same AI, same content generation, same Telegram interface. Everything's just preconfigured: platform connections through a simple dashboard, content skills built in, scheduling included, brand voice learning from day one.

The price gap is smaller than you'd think. Self-hosting runs $15-35/month. PostClaw runs $29/month flat. You're not saving much money by self-hosting — you're buying control and flexibility. Whether that trade is worth it depends entirely on your use case.

Getting Started

Two paths.

Self-host: Grab a Hetzner CX22 (or whatever VPS you prefer), follow the Docker setup in this guide, install your skills, connect your platforms. Budget an afternoon for the full setup.

Managed: Sign up at PostClaw, connect your social accounts, message your Telegram bot. You'll be posting in under 10 minutes.

Either way, you end up with the same OpenClaw engine handling your content. If you're still getting oriented, start with our overview of what OpenClaw is — it covers the big picture before you commit to a hosting path.