1
Step 1Open the server Apps tab
Select the tutorial-vps VPS, open the Apps tab, and start a new app deployment. Keep sensitive server details hidden before capturing or sharing screenshots.
Deploy OpenClaw in 3 Steps
1
Connect Your VPS
Add your server credentials to Server Compass
2
Select OpenClaw
Choose from our template library
3
Deploy & Configure
Fill in settings and click Deploy
No Docker knowledge required
Step-by-step deployment guide
Deploy OpenClaw on a VPS with Server Compass
Use the OpenClaw template in Server Compass to deploy a localhost-only AI agent gateway on your VPS, then verify the gateway UI through an SSH tunnel.
About 10 minutesBrowser verified
2
Step 2Choose an app template
Click New App and choose the template deployment path so Server Compass can load the built-in catalog.
3
Step 3Search for OpenClaw
Use the template picker search to find OpenClaw in the Server Compass template catalog.
4
Step 4Select the OpenClaw template
Choose the OpenClaw template. Server Compass fills the gateway service, persistent `.openclaw` data directory, localhost-bound gateway port, bridge port, and generated gateway token.
5
Step 5Review the OpenClaw settings
Confirm the app name and compose services. In this run, the app was named openclaw-demo and used host port 18789.
6
Step 6Deploy OpenClaw
Review the generated compose settings, confirm the localhost-bound gateway and bridge ports are available, keep the generated gateway token hidden, and click Deploy Now.
7
Step 7Watch the deployment progress
Keep the deployment modal open while Server Compass uploads the compose file, builds the OpenClaw gateway image, starts the container, and verifies the stack.
8
Step 8Confirm OpenClaw is running
After deployment finishes, return to the Apps tab and confirm the OpenClaw app is marked Running. The gateway is intentionally bound to localhost on the VPS.
9
Step 9Open OpenClaw through an SSH tunnel
Open an SSH tunnel to the gateway port, then load the local tunnel URL in a browser. The OpenClaw gateway UI confirms the service is reachable without exposing it directly to the public internet.
After OpenClaw Opens
- Keep the generated gateway token secret because it grants access to the OpenClaw control UI.
- Use Server Compass or SSH to open a tunnel before accessing the gateway UI.
- Configure Claude or other model provider credentials only inside the intended OpenClaw control surface.
- Keep the gateway bound to localhost unless you add a reviewed reverse proxy and authentication layer.
- Back up the `.openclaw` directory before relying on the gateway for production workflows.
Verified Result
The OpenClaw gateway UI loaded successfully through a local SSH tunnel.
OpenClaw deployment questions
What does the OpenClaw template deploy?
It builds and deploys the OpenClaw gateway container with persistent `.openclaw` storage and localhost-bound gateway and bridge ports.
Which port did the tutorial use?
The tutorial used remote gateway port 18789, bound to 127.0.0.1 on the VPS and accessed through a local SSH tunnel.
Why does the browser verification stop at the first web UI screen?
A fresh OpenClaw deployment is considered reachable when the gateway UI loads through the SSH tunnel. Token authentication and model-provider configuration depend on your own production credentials.
Should this become a blog post?
No. The deployment guide should live on the OpenClaw template detail page and be linked from the reusable template deployment docs page.
CLI Deployment
Deploy OpenClaw Yourself
Want full control? Here's how to deploy OpenClaw yourself using Docker Compose.
1
Establish SSH Connection
Connect to your remote server using SSH. Make sure you have your server credentials ready.
terminal
# Log into your server
ssh root@<your-server-ip>
# If using key-based auth
ssh -i ~/.ssh/my-key root@<your-server-ip>First time? Docker not installed? Run: curl -fsSL https://get.docker.com | sh
2
Create Project Directory
Set up a directory to store your Docker configuration.
terminal
# Create and navigate to project directory
mkdir -p ~/apps/openclaw
cd ~/apps/openclaw3
Configure Docker Compose
Add this configuration to your docker-compose.yml file:
docker-compose.yml
services:
openclaw-gateway:
build:
context: .
dockerfile: Dockerfile
ports:
- "127.0.0.1:18789:18789"
- "127.0.0.1:18790:18790"
environment:
HOME: "/home/node"
TERM: "xterm-256color"
NODE_ENV: "production"
OPENCLAW_GATEWAY_TOKEN: "<your-gateway-token>"
volumes:
- ./.openclaw:/home/node/.openclaw
- ./.openclaw/workspace:/home/node/.openclaw/workspace
init: true
restart: unless-stopped
command:
- "openclaw"
- "gateway"
- "--allow-unconfigured"
- "--bind"
- "lan"
- "--port"
- "18789"
Required Settings
PORTGateway host port(default: 18789)BRIDGE_PORTBridge host port(default: 18790)GATEWAY_TOKENGateway authentication token4
Start the Services
Execute the deployment and check the container status.
terminal
# Deploy the application
docker compose up -d
# Check container health
docker compose ps
# Monitor logs
docker compose logs -f --tail=1005
Allow Incoming Connections
Enable network access by updating your firewall rules.
terminal
# Allow the application port through firewall
sudo ufw allow 18789/tcp
sudo ufw reload
# Access your app at:
# http://your-server-ip:18789Skip the Terminal
Too complicated? Let Server Compass handle it.
Skip the terminal and deploy OpenClaw with a visual interface. Configure everything with clicks, not commands.
- Intuitive dashboard
- Deploy in 3 minutes
- Free SSL included
- Blue-green deploys
- Real-time logs
- Version history
Download Server Compass$29 one-time • Lifetime license
After Deployment
After deploying OpenClaw with Server Compass, complete these steps to finish setup
1
Open an SSH tunnel via Server Compass to access the Gateway UI
2
Authenticate with your GATEWAY_TOKEN
3
Configure Claude API keys in the Control UI
Need help? Check out our documentation for detailed guides.
OpenClaw FAQ
Common questions about self-hosting OpenClaw
How do I deploy OpenClaw with Server Compass?
Simply download Server Compass, connect to your VPS, and select OpenClaw from the templates list. Fill in the required configuration and click Deploy. The entire process takes under 3 minutes.
What are the system requirements for OpenClaw?
OpenClaw requires a minimum of 256MB RAM. We recommend a VPS with at least 1024MB RAM for optimal performance. Any modern Linux server with Docker support will work.
Can I migrate my existing OpenClaw data?
Yes! Server Compass provides volume mapping that allows you to import existing data. You can also use standard OpenClaw backup and restore procedures.
How do I update OpenClaw to the latest version?
Server Compass makes updates easy. Simply click the Update button in your deployment dashboard, and the latest OpenClaw image will be pulled and deployed with zero downtime.
Is OpenClaw free to self-host?
OpenClaw is open-source software. You only pay for your VPS hosting (typically $5-20/month) and optionally Server Compass ($29 one-time). No subscription fees or per-seat pricing.
Related Templates
View all Development
PocketBase
Open-source backend in a single file with realtime database, auth, and file storage
Appwrite
Open-source backend-as-a-service - self-hosted Firebase alternative
Parse Server
Open-source backend framework with dashboard
Supabase
Full Supabase self-hosted with Kong, GoTrue Auth, Realtime, and Studio
Ready to Self-Host OpenClaw?
Download Server Compass and deploy OpenClaw to your VPS in under 3 minutes. No Docker expertise required.
Download Server Compass