Run Clawdbot (OpenClaw) on a VPS in Minutes

TL;DR

• Clawdbot is now called Moltbot OpenClaw.
• Fastest setup: get a VPS → SSH → clawdbot onboard → connect messengers → send a test message.
• Specs: 2 GB RAM works for basic chat, but 4 GB+ is a better starting point if you’ll use automation (especially browser skills).
• On is*hosting, start with Medium (3 vCPU / 4 GB RAM / NVMe / 1 IPv4) for a smooth run.
• Want the quickest deploy? Use Ubuntu 22 + Clawdbot (OpenClaw) and skip the install glue.

What Is Clawdbot (and Why People Self-Host It)

Clawdbot is an open-source, self-hosted AI assistant built to work where you already talk: messaging apps. Instead of another tab to babysit, you message it like a teammate.

At a high level, people use it for two things: continuity and leverage. Continuity means persistent memory and long-lived context, so you don’t re-explain the same stuff every day. Leverage means proactive tasks and automation – up to browser-based actions like filling forms, if you enable that.

Where it fits best:

• A personal “ops buddy” that remembers preferences and recurring tasks;
• A private assistant for notes, reminders, and lightweight coordination;
• A chat-native interface for running small routines without switching tools.

Self-hosting is the default if you want full control. You decide where it runs, what it can access, and what gets stored. Your data, your tokens, your logs, your settings. And if something goes wrong, you can troubleshoot and fix it immediately.

Why a VPS: Cheaper Than a Mac mini, Faster Than DIY

Running Clawdbot at home works right up until you need it to work every day. A VPS is the fully predictable option: it stays on, it has a public IP, and it doesn’t share power with your coffee machine.

With a home box, you’ll eventually deal with:

• router resets, IP changes, flaky DNS;
• updates you postpone because you’re busy;
• “why is it slow today?” with no clear answer.

With a VPS, you get the boring benefits that make tools usable:

• always-on uptime;
• root access for tuning and debugging;
• location choice (put it near you for low chat latency).

And yes, cost matters. A Mac mini is a $700+ purchase before you count your time, backups, and maintenance. A VPS that matches Clawdbot’s recommended resources is $21/month on is*hosting. If you want a tool that runs 24/7, renting the correct compute is usually the smarter deal.

Recommended VPS Specs

Clawdbot can run on 2 GB RAM for basic chat. If your goal is “respond in chats and keep some memory,” that can be enough.

But if you’re planning to use automation seriously – especially browser automation and skills – 4 GB+ is the sane baseline. The moment you add background tasks, logs, and anything headless-browser-shaped, memory becomes the first bottleneck.

A simple way to think about it:

• Minimum: 2 GB RAM (basic chat, minimal extras);
• Recommended: 4 GB RAM+ (automation, skills, smoother updates).

And the practical baseline we see working well:

• CPU: 3 vCPU (stays responsive under load);
• Storage: NVMe (fast installs, fast logs, less friction).

That’s why our Medium plan is the default starting point: 3 vCPU / 4 GB RAM / NVMe / 1 IPv4. It’s a balanced config that stays responsive and leaves room to grow without overpaying.

Deploy Clawdbot in 2–3 Minutes on is*hosting

If you want speed, use the ready image and the onboarding flow.

Here’s the fast path:

1. Order a VPS (Medium or higher);
2. Select: Ubuntu 22 + Clawdbot (OpenClaw);
3. SSH in: ssh root@YOUR_IP;
4. Run: clawdbot onboard;
5. Connect messengers in the wizard;
6. Send a test message and confirm that it replies.

Once you see a successful reply inside your chat app, you’re operational. Everything after that is optional tuning.

Using the “Ubuntu 22 + Clawdbot (OpenClaw)” Ready Image

The ready image exists for a simple reason: you shouldn’t spend your evening rebuilding the same base stack from scratch.

What changes is not the end result, but the path:

• You skip the install glue work;
• You go straight to configuration via onboarding.

A reliable workflow looks like this:

• SSH in as root;
• Run clawdbot onboard;
• Connect one messenger first;
• Test in a dedicated chat;
• Add more messengers after the first one works.

That “one messenger first” rule saves time. It keeps debugging linear. If something fails, you know exactly which step introduced it.

If You Don’t Use the Ready Image (Upstream Install on Ubuntu)

If you’re deploying on a generic Ubuntu VPS (or you prefer upstream setup), use the official installer and wizard:

curl -fsSL https://clawd.bot/install.sh | bash

exec bash

clawdbot setup --wizard

Use this route when:

• You already have an Ubuntu server you don’t want to rebuild;
• You provision everything via scripts/Ansible and want a vanilla flow.

The trade-off is simple: you save on rebuilding, but you spend a bit more time on setup. If your goal is “fastest time to first message,” the ready image is still the clean win.

Quick Security Notes

The biggest rule: don’t expose admin/control interfaces directly to the public internet. If you need remote access, use an SSH tunnel, or put a reverse proxy in front with real authentication. A random port is not a lock.

Also:

• Use SSH keys (disable password login if you can);
• Handle messenger tokens like passwords (store properly, rotate if leaked);
• Patch the OS regularly;
• Start automation with minimal permissions, expand only when needed.

Wrap-Up

Clawdbot is built for people who want an assistant that always on, living in chat, with memory and optional automation. A VPS makes it stable and predictable, and the ready image makes it fast.

If you want the quick path: start with is*hosting’s Medium plan, deploy Ubuntu 22 + Clawdbot (OpenClaw), SSH in, and run clawdbot onboard. You’ll have a self-hosted assistant responding in minutes.