OpenClaw WhatsApp Bot on a Hostinger VPS

Shared hosting will not run this

OpenClaw runs as a long-lived process inside Docker. It has to stay online continuously: the WhatsApp session lives in that process, and inbound webhooks arrive at unpredictable times and need something listening for them.

Shared hosting gives you none of that. No persistent background process, no root, no Docker. Which WhatsApp API you pick makes no difference here, because the blocker is the runtime rather than the integration. A VPS, or any server where you control the container runtime, is the minimum.

Two ways to connect WhatsApp

Official WhatsApp Business Cloud API: hosted by Meta and compliant with WhatsApp's terms. Meta retired the older On-Premises API, so this is the only official route left. Getting on it means a WhatsApp Business Account, a phone number registered to that account, and business verification. Sending is billed per template message.

Unofficial libraries (Baileys and similar): drives WhatsApp Web with a number you already own. No Meta onboarding, no verification queue, no per-message fee. The trade is that the number can be banned, and that risk is real rather than a formality. Bulk or cold outreach is exactly what this route is worst at.

What it costs to host

OpenClaw itself is open source, so the recurring bill is the server plus whatever your WhatsApp route adds. The Cloud API adds Meta's per-template message charges on top; an unofficial library adds nothing. Hostinger VPS starts at $5.99/mo with 4 GB RAM, 1 vCPU and 50 GB NVMe of storage.

Can I run an OpenClaw WhatsApp bot on Hostinger shared hosting?

No. Shared hosting gives you no root access, no Docker and no persistent background process, and OpenClaw needs all three to keep the WhatsApp session alive between messages. The moment the process is stopped, the session drops and inbound webhooks have nothing listening for them. Move to a VPS or any server where you control the container runtime.

Do I need the official WhatsApp Business API?

You need it if the bot talks to customers, sends templates or handles volume, because the Cloud API is the only route Meta still supports after retiring the On-Premises API. It requires a WhatsApp Business Account, a phone number registered to that account, and business verification before you can send anything. For a personal automation on your own number, an unofficial library skips that onboarding entirely.

Will my WhatsApp number get banned?

On the unofficial route the risk is real, not theoretical: Baileys-style libraries drive WhatsApp Web with a number you own, which is outside WhatsApp's terms. Bulk sending and cold outreach are what get numbers pulled fastest, so use a number you can afford to lose. The Cloud API carries no such risk because Meta hosts the connection.

Which Hostinger plan do I need?

A KVM VPS plan, not a shared plan — the entry tier starts at $5.99/mo with 4 GB RAM and 50 GB NVMe of storage. That is enough for OpenClaw in Docker plus the WhatsApp connector process. Scale up only if you add local models, which is a GPU question rather than a VPS one.