
Deploying CloudBot on a VPS: A Hands-On Guide for Developers
Table of Contents
TL;DR
- Pick a cheap VPS (Hostinger KVM 2) with 2 vCPU, 8 GB RAM, 100 GB NVMe, 8 TB bandwidth for $7/month.
- Run the one-liner npx cloudbot install –init after installing Node.js via NPM or BUN.
- Add API keys for OpenRouter, OpenAI, Google Calendar, Google Places, ElevenLabs, WhatsApp, Telegram, Discord, and Slack.
- Link channels via QR codes or tokens, then let CloudBot orchestrate your AI agents.
Why this matters Every dev who’s set up a self-hosted AI assistant has felt the same headaches: pricey hardware, a maze of manual installs, and the fear that a powerful model will crash your main machine. CloudBot flips that pain into a single, reproducible workflow. It runs entirely on your own VPS, keeps persistent memory on-device, and lets you talk to it from any chat app—WhatsApp, Telegram, Discord, Slack, even iMessage. The result? Zero data leakage to the cloud and full visibility into every request and response.
Core concepts CloudBot is a conductor for multiple AI agents. Picture a band where each instrument is a different model (OpenAI, Anthropic, ElevenLabs). The conductor decides which instrument plays at any moment, keeping the music in time. Internally, CloudBot uses Node.js to spawn lightweight processes, stores context in a local SQLite database, and offers browser control for tasks that need a headless browser.
Key facts
- CloudBot is a self-hosted AI assistant that you can message from any app. Clawdbot — GitHub Repository (2025)
- It runs on your own machine and does not delegate data to Anthropic or OpenAI. OpenAI — API Reference (2023)
- Persistent memory lives on the VPS, so every conversation stays private.
- It can orchestrate dozens of agents—pull-request merging, calendar scheduling, invoice generation, and voice calls via ElevenLabs.
How to apply it
- Choose a VPS – Hostinger’s KVM 2 plan gives you 2 vCPU, 8 GB RAM, 100 GB NVMe, and 8 TB bandwidth for $7/month. I bought a 24-month plan with a 10 % discount using coupon “David” – it saved me about $80 a year. Hostinger — KVM 2 VPS Plan (2026)
- SSH into the server – ssh user@your-vps.
- Install Node.js – CloudBot supports NPM and BUN. I prefer BUN for speed: curl https://bun.sh/install | bash; bun add -g cloudbot. (If you’re on Ubuntu 22.04, you can also use the official Node.js docs.) Node.js — Official Documentation (2023)
- Install CloudBot in one line – cloudbot install –init. It pulls the latest release, sets up the daemon, and creates ~/.cloudbot/config.yaml.
- Create a .env file with your API keys: OPENROUTER_API_KEY=sk-…; OPENAI_API_KEY=sk-…; GOOGLE_CALENDAR_API_KEY=AIza…; GOOGLE_PLACES_API_KEY=AIza…; ELEVENLABS_API_KEY=sk-…; WHATSAPP_BUSINESS_API_TOKEN=…; TELEGRAM_BOT_TOKEN=123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11; DISCORD_BOT_TOKEN=…; SLACK_BOT_TOKEN=…. Keep the file out of source control.
- Link chat channels – for WhatsApp, run cloudbot channels login –channel WhatsApp and scan the QR code. For Telegram, run cloudbot channels login –channel Telegram –token YOUR_TELEGRAM_BOT_TOKEN. For Discord and Slack, use the respective tokens.
- Add skills – install voice and image skills: cloudbot skill add whisper; cloudbot skill add image-gen; cloudbot skill add elevenlabs. whisper uses OpenAI Whisper; image-gen uses OpenAI Image Gen; elevenlabs provides voice playback.
- Connect Google Calendar – cloudbot channel set calendar google to auto-block time and remind you of events.
- Start the service – systemctl –user start cloudbot and systemctl –user enable cloudbot.
- Debug and monitor – cloudbot status and cloudbot logs –follow show every API call and agent output.
Table: API keys side-by-side
| API | Use Case | Limitation |
|---|---|---|
| OpenRouter API Key | Access many models at lower cost | Requires credit management; rate limits apply |
| OpenAI API Key | Direct access to OpenAI models | Higher cost; strict usage limits |
| Google Calendar API Key | Manage calendar events | OAuth scopes; quota limits |
| Google Places API Key | Get place details for bookings | Daily quota; missing data handling |
Pitfalls & edge cases
- API key rotation – revoke and replace compromised keys; CloudBot continues with the new key once .env is updated.
- Rate limits – CloudBot can hit provider quotas if many agents run; monitor cloudbot metrics.
- Model hallucinations – use the “–trust-store” flag to filter outputs.
- Concurrent agents – many agents can exhaust CPU or memory; start small and scale.
- Persistent memory corruption – back up agent_memory.db regularly.
Quick FAQ Q1: Can I run CloudBot on Windows? A1: CloudBot is designed for Linux; use WSL2 or a lightweight Ubuntu VPS. Q2: How do I change the default AI model? A2: Edit config.yaml and set default_model: gpt-4o. Then restart. Q3: Is my data safe? A3: Yes—everything stays on your VPS; no data leaves unless you explicitly send it to a provider. Q4: Can I add my own custom skill? A4: Yes—create a folder under ~/.cloudbot/skills and follow the template. Q5: How do I get support? A5: Open-source project—open an issue on GitHub or join the Discord community.
Conclusion CloudBot gives devs a full-stack AI assistant you own. Cheap VPS + CloudBot beats expensive hardware and keeps data local. Follow the steps above, test commands, and scale when needed.
Reference list
- Node.js — Official Documentation (2023) (https://nodejs.org/en/docs/)
- OpenAI — API Reference (2023) (https://platform.openai.com/docs/api-reference)
- Hostinger — KVM 2 VPS Plan (2026) (https://www.mamboserver.com/hosting/hostinger-vps-review/)
- OpenRouter — API Authentication (2025) (https://openrouter.ai/docs/api/reference/authentication)
- Google — Calendar API v3 Reference (2025) (https://developers.google.com/workspace/calendar/api/v3/reference)
- Google — Places API Overview (2025) (https://developers.google.com/maps/documentation/places/web-service/overview)
- ElevenLabs — API Reference (2025) (https://elevenlabs.io/docs/api-reference/introduction)
- WhatsApp Business — Developer Hub (2025) (https://business.whatsapp.com/developers/developer-hub)
- Telegram — Bot API (2025) (https://core.telegram.org/bots/api)
- Clawdbot — GitHub Repository (2025) (https://github.com/clawdbot/clawdbot)





