WAHA vs Evolution API vs ZapZap: a 3-way comparison
WAHA and Evolution API are projects you install on your own server. ZapZap is the same kind of product (WhatsApp through an API, no Meta badge) operated by us, at a fixed price per number. The real difference between the three is not the send endpoint, which is similar, but who runs the connection, what the operator's time costs and what each one gives you beyond sending. Bias notice: ZapZap is the third option, so we say plainly when hosting it yourself is better. The facts about WAHA and Evolution come from the official sites and repositories, checked on 10/26 and 10/27/2026 and detailed in the comparison pages.
Published on · 5 min read
The short answer: who should pick which
Pick WAHA if you have DevOps, want the code and the data in your own environment and prefer to choose the connection engine. Pick Evolution API if you want an open source base that connects through Baileys or Meta's Cloud API and you are fine running Node, a database and Redis. Pick ZapZap if nobody at the company wants to be on call for the connection and you prefer a fixed price per number, with a dashboard, AI and automations already in the product.
On all three, the number runs through an unofficial channel. None of them removes the risk of restriction or ban, and anyone promising otherwise is promising what they do not control. For Meta's official route, read official API: costs and paths.
What each one is, in one sentence
WAHA: an unofficial, self-hosted HTTP API in a Docker container. The project site (waha.devlike.pro) describes it as free and open source, with no message limit and no license expiry, and the documentation lists engines such as WEBJS, NOWEB and GOWS, chosen with an environment variable.
Evolution API: open source, self-hosted software. The official repository (github.com/EvolutionAPI/evolution-api) states an Apache 2.0 license with extra brand-protection conditions, requires Node.js 20 or later, PostgreSQL or MySQL, recommends Redis and offers a Docker image. It connects through Baileys (a WhatsApp Web session) or Meta's Cloud API.
ZapZap: a managed unofficial API. Instances run on our infrastructure, you connect the number with a QR code and pay R$15 per active number per month, prepaid, with no per-message fee. See the one-to-one comparisons: ZapZap vs WAHA and ZapZap vs Evolution API.
Side-by-side table
| Criterion | WAHA | Evolution API | ZapZap |
|---|---|---|---|
| --- | --- | --- | --- |
| Who runs it | You | You | Us |
| Software license | Free and open source, per the project | Apache 2.0 with brand conditions | Paid service, no code to host |
| What you maintain | Docker server, updates, backups | Node 20+, database, recommended Redis, updates | No infrastructure |
| WhatsApp connection | WEBJS, NOWEB, GOWS engines and others | Baileys or Meta's Cloud API | Managed WhatsApp Web session, QR code |
| Per-message fee | None in unofficial mode | None on Baileys; Cloud API may charge | None |
| Dashboard, AI, funnel, groups | You build or integrate the business layer | Depends on what you install and integrate | Included in the product |
| Support | Community and issues | Community and issues | Vendor channel |
| Number ban risk | Yours | Yours | Yours |
The last row is the same in all three columns on purpose. The risk comes from unofficial use and from your sending behavior, not from where the server sits. See anti-ban on WhatsApp.
Real cost: where free stops being free
The code is free. The server running 24 hours, the database, the backup, the update when WhatsApp changes and the person who wakes up when the session drops all have a cost, even if it is hidden in someone's salary. For one number, hosting usually costs more in time than R$15 costs in money. For many numbers and an infrastructure team with spare capacity, the math can flip.
Build yours with the formula from the guide on the real cost (TCO) of Evolution and WAHA against a managed API, and check the current price on pricing. If you use the official Cloud API inside Evolution, Meta's cost still exists wherever the tool runs.
When hosting it yourself wins
Hosting wins when you already have an infrastructure team with spare capacity, must keep data in your own environment by contract, want to change the project code, or run many numbers and can automate maintenance. It also works for study: spinning up a test instance is a good way to learn how WhatsApp Web behaves. Just do not confuse a lab with running customers.
When the managed option wins
Managed wins when the team is small and each engineering hour is worth more than the price difference, when you need to start today, or when the operation depends on a stable channel to serve customers. You also get business features ready, such as AI per instance, Flow Builder, Funnel and group management, without assembling everything outside. The trade-off is depending on a third party and accepting the limits of the product.
How to test and how to leave, without lock-in
Since all three integrate through HTTP with a webhook, you can start on one and move later. Write your code against a thin layer, with the base URL and keys in environment variables, and switching stays cheap. If you are already on one of them, follow the right guide: migrate from WAHA or migrate from Evolution API.
Quick summary
- You host WAHA and Evolution API; ZapZap runs managed at R$15 per number per month, with no per-message fee.
- Ban risk is the same on all three: it comes from unofficial use and your sending behavior.
- Hosting wins with DevOps available, data in your environment or many numbers; managed wins with a small team and urgency.
- The code is free, the operation is not: add server, database, updates and on-call time.
Keep reading
Also read
Frequently asked questions
WAHA or Evolution API: which is better?
It depends on what you need. WAHA stands out for choosing the connection engine and running in a Docker container; Evolution API stands out for connecting through Baileys or Meta's Cloud API and requires Node, a database and a recommended Redis. Neither is best for every case, and the ban risk is the same.
Is ZapZap cheaper than hosting WAHA or Evolution?
For a few numbers, almost always, because the hidden cost of hosting is engineering time. For many numbers and an idle infrastructure team, hosting can come out cheaper. Calculate it with the TCO guide formula and your own numbers.
Is any of the three the official WhatsApp API?
Not in the default mode. All three work through an unofficial connection (Evolution can also use Meta's official Cloud API, with its rules and charges). For the full official channel, see the official API page.
Is moving from WAHA or Evolution to ZapZap a lot of work?
Usually it is a change of base URL, authentication headers and the format of a few fields, plus registering the webhook. The migration guides include the endpoint map.
Does any of them prevent a number ban?
No. No unofficial API removes the risk. Human pace, recipient consent, warm-up and gradual volume lower the odds, but do not bring them to zero.
Try ZapZap with one number
Connect with a QR code and run your first send in minutes. R$15 per active number per month, prepaid, no per-message fee.