Evolution API Free: the Licence Is $0, the Running Cost Is Not

Is Evolution API free?

Evolution API is free to license and not free to run. The repository carries an Apache 2.0 LICENSE file — confirm it there before you deploy — so there is no seat count, no expiry and no royalty. Running it needs a host, PostgreSQL, Redis, TLS, backup and the send pacing the project does not provide. Its $0 is a licence price, not a total cost of ownership.

Five different questions hide inside the phrase “evolution api free”, and most pages answer only the first. This page answers all five: free to license, free to run, a free hosted tier, free of Meta verification, free of per-message fees.

The architecture explainer covers what the project is and how it reaches the WhatsApp Web protocol. This page stays on the word free.

One pin before the detail: every figure below is one to check on the day you deploy. The repository's licence file, its installation documentation and its commit history all move. This page describes the shape of the cost, not a snapshot of someone else's invoice.

What do the five meanings of “free” actually come to?

Three of the five are yes and two are no. Evolution API is free to license, free of Meta verification and free of per-message fees. It is not free to run, and the open-source project ships no hosted tier of its own — if a commercial hosted offering exists, its plans and any free tier are defined on that vendor's own pricing page, not here.

Free to license — yes

Apache 2.0, per the repository's LICENSE file. No seat count, no expiry, no royalty, commercial use permitted. The licence text is examined in the next section.

Free to run — no

A container needs a host. PostgreSQL needs disk, credentials and a restore path you have actually tested. TLS needs a reverse proxy. Monitoring needs someone to read it. None of that sits inside the licence grant.

Redis deserves its own line because its terms have moved before. Check the licence of the exact image tag your compose file pins rather than the one you remember. It is the dependency whose terms change most often.

Free of Meta Business verification — yes

Evolution API reaches WhatsApp through Baileys, the open-source WhatsApp Web implementation maintained by WhiskeySockets. That route needs no Meta Business portfolio, no dedicated number and no display-name review, which is why most people run this search. The official path is set out in our verification comparison.

Free of per-message fees — yes, because it does not meter

Nothing in the stack counts sends or prices them, so there is no meter, no ceiling and no invoice. A per-message fee needs a party sitting in the middle of your traffic; a self-hosted API has no such party. Keep the limits of that in view. A price of zero is not a pricing model, and it tells you nothing about what a send costs you in hours.

For contrast, Meta's WhatsApp Business Platform bills template messages per message, priced by market and message category, according to Meta's own developer documentation. Meta revises WhatsApp pricing periodically, so open that page on the day rather than trusting a cached table. The Cloud API comparison covers that route; the flat-rate analysis covers the arithmetic without re-deriving Meta's rates.

What does the licence actually cover?

Evolution API's repository carries an Apache 2.0 LICENSE file. Open it on the day you deploy and confirm what your fork carries; licences drift far less than blog posts, but they do drift.

Apache 2.0 grants a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright licence to use, modify and redistribute the code, including commercially, plus an express patent grant.

What it does not grant is any assurance that the code works, or that anyone will help you. The licence text says as much: the software is distributed on an “as is” basis, without warranties or conditions of any kind, express or implied.

Three practical consequences:

• A licence is not a support contract. Nobody is obliged to answer your issue or ship your fix.
• A licence is not a maintenance promise. The project can slow or stop; the grant survives it, and so does your operational exposure.
• A licence is not a trademark grant. Names and marks are handled separately from the code.

Read the LICENSE file once. It is the source of truth, and it changes far less often than blog posts do.

What do you still build or pay for yourself with Evolution API?

The API is the product. Everything a non-developer would call “the app” is your responsibility, and the project's installation documentation makes the shape explicit: PostgreSQL and Redis are required services, not optional extras. Budget for a host, a database, TLS, monitoring and a pacing layer before you budget for anything else.

A host

A VPS or a machine that stays on, with restarts, monitoring and patching. Container orchestration is yours.

PostgreSQL and Redis

Schema, credentials, disk growth and a restore path you have tested. Redis brings memory limits and an eviction policy. Message history lives in that database, and nobody else keeps a copy. Back it up before you need it.

TLS, a reverse proxy and monitoring

An API on the open internet without TLS is not a plan. Alerting nobody reads is not monitoring.

The manager interface — check your own release

The documented surface is the REST API, and the project is API-first. Community manager builds exist alongside it. Confirm what your deployed version exposes, because this is exactly where blog posts and release notes drift apart.

A send-pacing strategy

The send-message endpoint sends when you call it. Nothing in the stack decides how fast, how often, or to how many cold recipients. There is no session warming for a new number, no per-number daily budget the app enforces, no adaptive slow-down as risk rises, no duplicate-content guard and no risk score. Those decisions live in your code.

When the WhatsApp Web protocol shifts, every unofficial project waits for an upstream fix, redeploys and re-pairs sessions. SocialMate included. The install is not the hard part; the unplanned weekend six months in is.

How much does it cost to run Evolution API in 2026?

The honest total is a small server bill plus a larger labour bill that appears on no invoice. Budget the labour line first and the infrastructure line becomes a rounding error. PostgreSQL major-version upgrades, in particular, are yours to plan.

The infrastructure side, in the order it bites:

1. Compute. Hetzner, DigitalOcean and Contabo each publish small shared-instance prices on their own pages. Read the page, not a blog post — providers rename and reprice small tiers more often than articles update. Size up once if you queue media.
2. Managed database, if you take it. Convenience has a monthly price. Self-hosting Postgres on the same box has a different price, paid in risk.
3. Backups and snapshots. Usually a percentage of the storage you already pay for.
4. Monitoring and alerting. Free tiers exist; the routing that wakes you does not configure itself.
5. Your hours. Setup, upgrades, incident response and the pacing layer. The largest line item on this page.

Now the flat numbers, ours, stated exactly. SocialMate Free is $0 forever, no card. Pro is $99 per year ($8.25/month equivalent) or $10 per month, cancel anytime. One licence includes one device; extra concurrent devices are seats. WhatsApp accounts are unlimited on Pro. No per-message fee on either tier.

The comparison worth making: an evening of pacing engineering is the same work SocialMate ships on its free tier. If the labour line is the part you want removed, the free desktop app is the shortest way to test that claim.

Does Evolution API have an anti-ban engine?

No, in the sense that matters. Evolution API ships no adaptive anti-ban layer: the send endpoint sends when called. There is no session warming, no per-number budget, no adaptive throttle, no risk scoring and no duplicate-content guard. Pacing is a caller responsibility, and the project's own send-message documentation is the proof.

This is a scope difference, not a quality judgement. Evolution API is a widely used open-source project doing its stated job, a REST surface over WhatsApp, competently. Engineering human-like timing was never in the brief.

What building that layer means, concretely:

• Randomised delays and jitter, so gaps do not form a pattern.
• A warm-up ramp measured in days before a new number carries real volume.
• A per-number daily cap enforced in your code, not hoped for.
• A guard that refuses identical text to many recipients in a row.
• A read-then-type sequence before replying, because people open a chat before they answer it.
• A throttle that slows sends as your own risk signals climb, and a recovery path for a cooled account.

Each is a small feature. Together they are the layer that shapes whether a number lasts. SocialMate ships that layer on every tier, Free included, because it is the product rather than an add-on. Risk is reduced, never eliminated.

Will I get banned using a free, unofficial WhatsApp API?

Bans are possible on any unofficial WhatsApp tool, and no tool can promise otherwise — Evolution API, WAHA, Baileys-based stacks and SocialMate alike. A free licence does not lower that risk; it only means nobody charged you for it. Both statements belong in the same sentence, so here they are.

Two facts to hold together. Running the software is legal; using the unofficial WhatsApp Web protocol conflicts with WhatsApp's terms. Both are true at once. Protocol shifts hit every unofficial project the same way: wait for an upstream fix, redeploy, re-pair sessions.

The official route is not riskless either, it is differently framed. Meta's Cloud API documentation describes tiered per-number messaging limits that scale with business verification and quality — policy-defined, and adjustable by Meta. Every route answers to Meta's enforcement; only the mechanism differs.

The controllable variable is behaviour, not licensing. How fast you send, how many recipients are cold, whether everyone on the list is already waiting on an answer — those decide outcomes far more than which repository you cloned. Unsolicited bulk messaging is the fastest route to a ban on any stack.

The mechanics live elsewhere rather than being re-derived in a cost post: what self-hosting can and cannot change about a disabled account, and the plain answer in will I get banned.

Who should pick Evolution API, and who should pick SocialMate?

Pick Evolution API for a bare REST surface and full control, if you will write the pacing, retries and front-end yourself. Pick SocialMate for the same no-approval route with the operational and safety layer already built. Neither is the responsible choice in general; each is right for a particular person with a particular weekend.

Evolution API fits a developer comfortable with Docker, PostgreSQL and Redis who wants no vendor, no licence key and no activation server between their code and WhatsApp, and who will read the protocol library's changelog. That is a legitimate position held by competent engineers. n8n users reach it through HTTP Request nodes or community nodes. SocialMate's shape is different: a native n8n community node with its own credential and action and trigger nodes, plus a native MCP server for Claude Desktop, Cursor and any MCP client. MCP is an open protocol surface, not a per-service connector. If you already own an Evolution-shaped stack, keep it.

SocialMate fits a founder, marketer or agency messaging people who are already waiting on an answer — an order, a booking, a question asked — who does not want a week of Docker, Postgres and pacing design first. Two structural differences. Docker is SocialMate's option: the desktop app runs on Windows, macOS and Linux, and since 2.0 also headless on a VPS via Docker or systemd, managed from a browser console. With Evolution API, Docker is the obligation. Second, the desktop app connects from your own residential IP, usually the same home network as the phone that owns the number — the network picture WhatsApp already associates with the account. That removes a risk factor; it does not make anyone ban-proof, and no tool can. A VPS uses a datacentre IP, which is why Pro adds per-account proxy routing back out through a residential or mobile proxy.

The engine, on every tier: randomised delays and jitter, Safe/Balanced/Fast pacing profiles, per-number rate limits, session warming, a real typing indicator and read receipts before replying, an adaptive throttle, a duplicate-content guard, live 8-factor risk scoring with cold-outreach detection, and risk-based auto-resume. Pro adds High-Volume Mode, which scales toward 5,000 messages per day per account only after 72 hours of warming. Warming is never optional, and no volume is safe on day one.

What does SocialMate Free actually include for $0?

SocialMate Free is a $0 tier with one WhatsApp account capped at 200 messages per day, and it includes the full anti-ban engine, a desktop GUI, local storage and a local HTTP API that runs on Free for reads and plain text send. Three facts the table cannot carry:

• The local HTTP API runs on Free, not Pro. Read endpoints plus text send up to 200/day, 2 webhook endpoints, 100 deliveries/day and 9 of the 35 webhook events. That the API is not Pro-only is the most misunderstood fact about the product; the docs confirm it.
• Signal operations cost nothing on any tier: quoted replies, emoji reactions, mark-as-read and the typing indicator. No chat bubble, no message budget consumed, no change to the risk score.
• The free cache is live-only. Free receives messages over webhooks but cannot query the archive. Full history, full-text search and the smart queue are Pro.

Pro adds media send, polls, locations, contact cards, group operations, scheduled messages and batches, unlimited webhooks, the named tunnel, Agent Memory and the AI conversation-context export endpoint. AI replies generated by SocialMate remain coming soon. The 7-day Pro trial is opt-in inside the app, asks only for an email, and takes no card. Free versus Pro pricing has the exact boundary, and warming new numbers has the ramp protocol before you plan real volume.

Option	Pricing model	Licence / approval needed	What you install	Manager UI	Anti-ban / pacing built in	Daily send ceiling	Where data lives	Ban / account risk (stated fairly)
Evolution API	Free to license; you pay infrastructure and your own engineering hours	Apache 2.0 per the repository LICENSE file — confirm it there; no Meta approval, unofficial protocol	Docker + PostgreSQL + Redis	The REST API is the documented surface; community manager builds exist — verify what your release ships	None. The send endpoint sends when called: no warming, no adaptive pacing, no per-number budget, no duplicate-content guard, no risk score	None imposed by the software; WhatsApp's enforcement sets the real limit	Your server and your database	Bans possible on any unofficial protocol; the pacing discipline is yours to build and maintain
SocialMate Free	Flat licence at $0 — no per-message fee	No Meta approval; independent, not affiliated with Meta	Desktop app (Windows / macOS / Linux); Docker or systemd optional	Yes	Full engine: jitter, Safe/Balanced/Fast pacing, per-number limits, session warming, typing indicator, read receipts, adaptive throttle, duplicate-content guard, 8-factor risk scoring	200 per account per day	Your machine, local storage	Bans possible. The safety layer is included, but risk is reduced, never eliminated
SocialMate Pro	Flat licence: $99/yr ($8.25/mo equivalent) or $10/mo, cancel anytime; no per-message fee	No Meta approval; independent, not affiliated with Meta	Same app; desktop or headless VPS with browser console	Yes	Same engine, plus High-Volume Mode after 72h warming and per-account proxy routing for VPS deployments	500 per account per day, scaling toward 5,000 via High-Volume Mode after 72h warming	Your machine or your server volume	Bans possible. Higher ceilings require the warming protocol; no volume is risk-free on day one
WhatsApp Cloud API (official)	Metered per message: Meta's developer documentation bills template messages per message, priced by market and category — check Meta's page for current figures	Meta Business portfolio, business verification, dedicated number, display-name review	Nothing — hosted by Meta	Meta's own tooling	Not applicable — official route, governed by Meta policy	Tiered per-number limits set by Meta, scaled by verification and quality rating	Meta's cloud	Official route, so structurally different from any unofficial tool; Meta's policy enforcement, quality rating and number restrictions still apply

Run Evolution API yourself for free

1. Provision a host Choose a small VPS or an always-on machine you control, and set up patching, a firewall and SSH access before anything else. The licence is free; the host is not.
2. Stand up the required services Deploy Evolution API alongside PostgreSQL and Redis with Docker Compose, following the project's installation documentation for the release you pin. Confirm the licence of the exact Redis image tag you deploy.
3. Configure credentials and environment Set the database and cache connection strings, a strong global API key and per-instance tokens, all through environment variables as documented. Put TLS in front with a reverse proxy.
4. Create an instance and pair the number Create an instance through the API, pair the WhatsApp number by QR, and subscribe its webhook events. Test with a single message to your own phone before anything else.
5. Write the pacing layer before real traffic Before messaging anyone who is not expecting it, add randomised delays, a per-number daily cap, a warm-up ramp for the new number and a duplicate-content guard. The software will send as fast as you call it, which is the risk.

Frequently asked questions

Is Evolution API free forever?

The licence is. Apache 2.0 grants a perpetual, irrevocable, royalty-free right with no expiry clock, so the software cannot be re-priced under you — confirm the text in the repository's LICENSE file. Hosting, databases, backups and your own engineering hours carry no such guarantee.

Is there a free hosted Evolution API tier?

Not from the open-source project. The repository is self-hosted only: no account, no hosted endpoint, nothing to sign up for. If a commercial hosted offering exists, its plans and any free tier are defined on that vendor's own pricing page on the day you read this — check there, not here.

Can I use Evolution API commercially without paying a royalty?

Yes, per its Apache 2.0 LICENSE file. That licence permits commercial use without a royalty or a seat count, and it does not require you to open-source your own application. It also carries an express patent grant, which is the part most people miss. The same licence supplies the work without warranties or any support obligation.

Do I need a Meta Business account for Evolution API?

No. Evolution API connects through Baileys, the open-source WhatsApp Web protocol implementation, so there is no Meta Business portfolio, no business verification, no dedicated number requirement and no display-name review. That absence is the main reason people search for this. The trade is that the route is unofficial and conflicts with WhatsApp's terms.

How much does it cost to run Evolution API?

A small cloud instance plus the database and cache if you run them separately, plus backups — and then the line that dominates: your own hours for setup, upgrades, incident response and the pacing layer. Read your chosen provider's current price page before budgeting; small-tier names and prices change more often than articles do.

Do I need Docker for Evolution API?

In practice, yes. The documented deployment path is containerised alongside PostgreSQL and Redis. Running it from Node without containers is possible but leaves you maintaining the surrounding services by hand. Assume Docker, a database and a cache before you begin.

Does Evolution API have a dashboard?

Not in the documented product. Evolution API is API-first — the REST surface is the documented way to use it — and community manager builds exist alongside it. Check what your deployed release actually ships before you plan around a UI.

Does Evolution API have anti-ban protection?

No. The send endpoint sends when it is called, and that is the extent of it. There is no session warming for new numbers, no adaptive throttle, no per-number budget the app enforces, no duplicate-content guard, no live risk scoring and no automatic recovery for a cooled account. Those are yours to design.

Evolution API vs WAHA: which is freer?

Neither charges per message, and neither is free to run, so on the cost question the two are close. WAHA is another open-source WhatsApp HTTP API on the unofficial protocol, and both leave pacing and anti-ban engineering to you. Check each project's current licence yourself. The differences that matter are deployment shape and maintenance activity, which we set out in the self-hosted comparison.

Does Evolution API work with n8n?

Yes, through HTTP Request nodes pointed at the API and through community-built nodes, with webhooks driving the trigger side. SocialMate takes a different shape: a native n8n community node (n8n-nodes-socialmate) with its own credential and action and trigger nodes, plus a native MCP server for Claude Desktop, Cursor and other MCP clients.

How many messages can I send per day with Evolution API?

The software imposes no cap, which is not the reassurance it sounds like. WhatsApp's enforcement sets the real ceiling, and that ceiling is behavioural: pace, per-number history, duplicate content and how many recipients are cold. A cap you choose deliberately is safer than no cap at all.

Is Evolution API an official WhatsApp product?

No. It is an independent open-source project built on the unofficial WhatsApp Web protocol via Baileys, and it is not affiliated with, endorsed by or partnered with WhatsApp or Meta. Neither is SocialMate — it is independent too, and it is not the official WhatsApp Business API.