Self-Hosted WhatsApp Gateway: Running Your Own Sending Engine

Most users are well served by the platform's shared sending infrastructure — it's simpler, requires no setup, and just works. But some teams have specific reasons to want their WhatsApp traffic running on hardware they control: data residency requirements, an existing VPS or spare machine they'd rather use than pay for shared capacity, or simply a preference for owning the full stack their business depends on. Self-hosted server mode exists for exactly that group.

What actually runs where

In self-hosted mode, the engine that maintains your WhatsApp connection and sends your messages runs on your own PC, VPS, or even a spare Android phone — not on the platform's shared servers. It connects back to your dashboard through a secure tunnel, so you keep the same login, the same inbox, the same automation rules, while the actual sending traffic and the WhatsApp session itself live on infrastructure you control.

What you'll need

A machine that can stay on and connected (a VPS is the most common choice, though a dedicated PC or phone works too), Node.js installed to run the connector, and a tunnel — the setup guide covers both zrok and Cloudflare Tunnel as supported options, so you're not locked into a single tunneling provider.

What's the same, and what's different

Core messaging — sending, receiving, the live chat inbox — works the same way it does on shared infrastructure. A few advanced automation surfaces (certain Forms/Poll/Subscribe-triggered flows) are still being extended to the self-hosted connector and aren't available there yet; that's a known, documented gap, not a bug, and it narrows with each update.

Partner mode: get paid for your uptime

If your self-hosted server has spare capacity, admin-approved partner mode lets it also serve as backup capacity for the platform's own shared fleet — with your wallet automatically credited for the uptime and messages it handles. It's opt-in and admin-approved on both sides, not something that happens without your knowledge.

Is self-hosting right for you?

If you're happy with shared infrastructure and don't have a specific reason to run your own, there's no need to change anything — it's genuinely optional. If you do have infrastructure requirements, or you'd simply rather manage the hardware your messaging depends on yourself, self-hosted mode gives you that control without giving up the dashboard, inbox, and automation you're already using.