EvolutionAPI · Overview
What EvolutionAPI is, when to use it, how it compares to Meta's Official API and the architecture Rollin Host recommends for production use.
EvolutionAPI is an open-source wrapper around WhatsApp Web (via Baileys) that exposes a REST/WebSocket API for sending and receiving messages. It is the most widely used solution in Brazil for WhatsApp automation because it is free, multi-instance and has native integration with n8n.
When to use EvolutionAPI
Use it when...
- You want full control of the number (without depending on a third-party provider)
- You need multi-instance (several numbers in the same stack)
- You integrate directly with n8n / Make / Zapier
- You have low to medium volume (up to ~10k messages/day per number)
Do not use it when...
- You need the official Meta Cloud API (mass campaigns, marketing)
- You want a contractual SLA guarantee from WhatsApp (use the official API)
- You have >50k messages/day per number (a ban is likely)
Guides
Connect a WhatsApp number
From scratch to a scanned QR code, with the webhook receiving messages.
Webhooks
How to configure message, status and presence webhooks, with retries and idempotency.
Multi-instance
Run multiple numbers on the same installation. Limits, isolation and horizontal scaling.
Recommended server
| Scenario | Plan | Why |
|---|---|---|
| 1 number, < 5k msgs/day | VPS Inicial | EvolutionAPI alone uses ~512 MB of RAM |
| 1 number + n8n + LLM | VPS Pro | Leaves room for Postgres + Redis |
| 5+ numbers | VPS Plus | Each instance uses ~400 MB extra |
| 20+ numbers | VPS Boost+ | Consider moving EvolutionAPI to a dedicated server |
Last updated:
