Pay per connected instance. Not per message.
Predictable monthly billing. Upgrade or downgrade in one click. No long-term commitments.
Starter
Solo builders and side projects.
- 1 connected instance
- Send and receive messages
- Media in and out
- Signed webhooks
- QR connect flow
- REST + SSE API
- Basic delivery logs
- Community support
Pro
Production teams running real workflows.
- 5 connected instances
- Advanced webhook retries
- Realtime event streams
- Webhook delivery logs
- API playground
- Higher rate limits
- Priority reconnect
- Team support
Max
High-throughput operations and SLA-ready infra.
- 25 connected instances
- Advanced observability
- Dedicated webhook workers
- Advanced delivery logs
- Premium support
- SLA-ready
- High throughput
- Audit logs
Compare plans
| Feature | Starter | Pro | Max |
|---|---|---|---|
| Connected instances | 1 | 5 | 25 |
| Messages | Unlimited | Unlimited | Unlimited |
| Webhook retries | 10× | 20× | 40× |
| Webhook delivery logs | 7d | 30d | 90d |
| Rate limits (req/min) | 60 | 300 | 1500 |
| Support | Community | Team (1 business day) | Premium (4h) |
| SLA | — | — | 99.9% |
Pricing questions
Why per instance instead of per message?
Messages are unmetered. WhatsApp infrastructure cost scales with stateful connections — one Baileys socket per instance — not with throughput. Pricing should match the cost shape.
What are the rate limits?
Starter is capped at 60 req/min, Pro at 300, Max at 1500. Webhook delivery is unlimited and queued; the cap is on inbound REST calls.
Can I downgrade?
Yes. If you exceed your new plan's instance count, the oldest instances move to read-only until you bring the total back under cap.
Can I self-host?
Yes. The gateway is a single Node process you can run on Railway, Fly, Hetzner, or your laptop. Self-hosted users get the same contracts package and a community-supported deployment guide.