OpenClawFor OpenClaw users

OpenClaw,
without the setup.

No VPS to provision. No SSH session. No API key wrangling. No config files, no exposed security flaws, no hidden costs. Deploy in seconds.

You've seen the demo. You wanted it.

You found OpenClaw on Twitter, watched someone's agent do something genuinely useful, went to the docs, and saw the install process. VPS. SSH. Node. Environment variables. Systemd. Reverse proxy. Firewall config.

And you closed the tab. We get it — that's exactly who Claws is for.

What's set up for you

Everything OpenClaw needs to run — pre-configured, secured, and ready.

OpenClaw, Pre-Configured

Latest stable version, already installed and running. You skip the git clone, the npm install, the env file, all of it.

LLM Connected Out of the Box

Claude, GPT-4o, Gemini, Groq — pick one in the setup flow. We handle the API keys and routing. Switch models anytime.

Telegram & WhatsApp Ready

Connect your chat apps during onboarding. Your agent is in your pocket before you finish your coffee.

Lobstash Plugins — One Click

Polymarket, EVM Wallet, Twitter, Vercel, Namecheap. Install from the dashboard. No API doc spelunking.

Dashboard, Not Terminal

Logs, restarts, status — all in your browser. SSH access is there if you want it. You just don't need it.

Your Server, Your Data

Hosted on Hetzner. Encrypted keys, UFW firewall, automatic updates. Nothing sits in a shared pool.

The normal way vs. our way

Nothing wrong with self-hosting. It's just a lot.

The DIY install

# 1. Provision a VPS (Hetzner, DigitalOcean, wherever)$ ssh root@your-server-ip # 2. Install Node.js$ curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -$ sudo apt-get install -y nodejs # 3. Install OpenClaw$ npm install -g openclaw # 4. Configure your .env$ cp .env.example .env && nano .env# (add ANTHROPIC_API_KEY, OPENAI_API_KEY, TELEGRAM_BOT_TOKEN...) # 5. Set up UFW firewall$ ufw allow 22 && ufw allow 80 && ufw allow 443 && ufw enable # 6. Configure systemd service$ nano /etc/systemd/system/openclaw.service$ systemctl enable openclaw && systemctl start openclaw # 7. Set up Caddy reverse proxy$ nano /etc/caddy/Caddyfile# ... point your domain, get SSL cert ... # 8. Debug why Telegram isn't connecting$ journalctl -u openclaw -f# (good luck)

The Claws way

1
Pick your plan
2
Choose your LLM
3
Connect Telegram (or WhatsApp, Discord)
4
Install any plugins you want
5
Hit deploy

That's it. Your agent is live. We handle the VPS, the firewall, the reverse proxy, the SSL cert, the systemd service — all of it.

Simple pricing

One plan. Your agent always on. Pay only for what you use.

Claws — Standard

Your agent, always on.

One plan. Everything included. No surprise bills.

  • Your own dedicated AI instance
  • All models — switch anytime
  • All plugins from Lobstash
  • Connect any messenger
  • $5 in free usage credits
  • Automatic OpenClaw updates

What does a credit buy?

$5 in free usage credits — about 29,000 messages with GPT-4o Mini.

ModelInput /1MOutput /1M
MiniMax M2.5$0.33$1.35
GPT-4o Mini$0.17$0.68
GPT-5.1 Codex$1.41$11.24
Claude Sonnet 4.6$3.37$16.85
Claude Opus 4.5$5.62$28.09

Want pricing for all 300+ supported models? View full model pricing →

You found OpenClaw for a reason.

Don't let a config file stop you.