How to Deploy OpenClaw on a VPS (The Easy Way and The Hard Way)
So you've decided you want your own AI agent. Not some shared ChatGPT wrapper — your own private instance, running on your own server, under your full control. Smart move.
OpenClaw is one of the best open-source AI agent platforms out there. It supports multiple AI providers (OpenAI, Anthropic, OpenRouter, and more), comes with built-in channel integrations like Telegram, and has a proper skills system for extending what your agent can do.
But here's the thing: deploying it isn't exactly "click a button and you're done." There are two ways to do it — the manual way and the easy way. Both are valid. Let's walk through each so you can pick the right one.
What Is OpenClaw?
OpenClaw is an open-source AI agent platform. Think of it as a self-hosted alternative to hosted AI tools. You install it on a server, connect your AI provider API keys (OpenAI, Anthropic, etc.), and you get a fully functional AI agent that you own.
Key features:
- Multi-provider support — Switch between OpenAI, Anthropic, OpenRouter, and others from a dashboard
- Channel integrations — Connect your agent to Telegram, with more channels coming
- Skills system — Extend your agent's capabilities with custom skills
- Full privacy — Your conversations stay on your server, period
The Hard Way: Manual Deployment
If you're a developer who wants full control over every piece of the stack, here's what the manual setup looks like. I'm not going to sugarcoat it — it's doable, but it takes time and some Linux experience.
What You'll Need
- A VPS with at least 4 vCPU, 8GB RAM, 80GB SSD (Hetzner, DigitalOcean, or Linode all work)
- Ubuntu 22.04 or similar Linux distro
- A domain name pointed at your server's IP
- About 60-90 minutes of focused time
Step-by-Step
1. Provision a server. Sign up for Hetzner (cheapest for the specs) and create a CPX31 or similar instance. Note your server's IP address.
2. SSH into your server.
ssh root@your-server-ip
3. Update the system and install dependencies.
apt update && apt upgrade -y
curl -fsSL https://deb.nodesource.com/setup_20.x | bash -
apt install -y nodejs git build-essential
4. Clone the OpenClaw repository.
git clone https://github.com/openclaw/openclaw.git
cd openclaw
5. Install Node.js dependencies.
npm install
6. Configure environment variables. This is where it gets tedious — you need to create a .env file with your database credentials, API keys, secret tokens, and more. The OpenClaw docs list all required variables, but expect to spend 15-20 minutes getting this right.
7. Set up a reverse proxy. You need Nginx or Caddy to handle HTTPS and route traffic to your OpenClaw instance.
apt install -y nginx certbot python3-certbot-nginx
Then configure your Nginx site, set up SSL with Certbot, and restart the service.
8. Set up DNS. Point your domain (or subdomain) to your server's IP address. Wait for DNS propagation (5 minutes to 48 hours, usually fast).
9. Set up a process manager. Use PM2 or systemd to keep OpenClaw running after you close your SSH session.
npm install -g pm2
pm2 start npm --name "openclaw" -- start
pm2 save
pm2 startup
10. Test everything. Visit your domain in a browser. If you see the OpenClaw dashboard — congrats, you did it.
The Reality Check
That's 10 steps, but each step has sub-steps. Configure the wrong environment variable? White screen. SSL cert not renewing? Your site goes down in 90 days. Nginx config has a typo? 502 Bad Gateway.
It's absolutely doable if you're comfortable with Linux servers. But it's not a 5-minute job.
The Easy Way: ActivateClaw
ActivateClaw exists precisely because that manual process is a pain, even for developers.
Here's what happens when you sign up:
- You pick a subdomain (e.g.,
yourname.botlive.me) - Optionally enter a Telegram bot token (if you want instant Telegram integration)
- Click deploy
- In a few minutes, you get a dedicated Hetzner VPS with OpenClaw fully installed, SSL configured, Caddy reverse proxy running, and everything wired up
What You Actually Get
- Dedicated server — 4 vCPU, 8GB RAM, 80GB SSD on Hetzner (EU). Not shared, not containerized — it's your machine
- OpenClaw pre-installed with SSL and Caddy reverse proxy
- Custom subdomain at
yourname.botlive.me - Telegram integration connected at checkout if you provide a bot token
- Dashboard to manage AI providers, connect channels, and configure your agent
- SSH access if you want to dig into the server yourself
The cost is a flat monthly fee. That includes the server, the setup, the managed infrastructure, everything. See current pricing on the homepage.
Which Approach Is Right for You?
Here's the honest breakdown:
| Manual | ActivateClaw | |
|---|---|---|
| Setup time | 60-90 minutes | A few minutes |
| Linux experience needed | Yes | No |
| Monthly cost | $5-15 (server only) | One flat fee (server + managed setup) |
| SSL/proxy setup | You handle it | Done for you |
| Updates | You manage them | You manage them |
| SSH access | Yes | Yes |
| Full control | 100% | 100% (it's your server) |
Pick manual if: You enjoy server administration, want to learn, or need to run OpenClaw on specific infrastructure you already have.
Pick ActivateClaw if: You want OpenClaw running today without touching a terminal. You're a business owner, solopreneur, or developer who'd rather spend time building with your AI agent than setting it up.
Both options give you full ownership and full control. The difference is just how you get there.
Ready to Deploy?
If you're going the manual route, the OpenClaw documentation has the full setup guide.
If you'd rather skip the DevOps and have it running in a few minutes, head to activateclaw.com and deploy your own private AI agent today.
Either way — welcome to self-hosted AI. You're going to love it.