WACrew

Guide

Open-source WhatsApp APIs, WAHA, Evolution API, WuzAPI and the libraries under them

The self-hosted WhatsApp REST APIs and the libraries they run on, compared by engine, language, license and maintenance, with GitHub data checked in November 2026.

Updated 2 min read
On this page
  1. REST servers
  2. Libraries
  3. When you want an app, not an API
  4. The shared caveat
  5. FAQ

An open-source WhatsApp API gives you REST endpoints and webhooks for a WhatsApp number without a monthly fee per number. Every one of them links your number the way WhatsApp Web does, so none of them is the official Business API. What changes between them is the engine underneath, the language and the license.

GitHub data checked on November 14, 2026.

REST servers

ProjectEngineLanguageLicenseStars
Evolution APIBaileys or the official Cloud APITypeScriptApache 2.0 plus extra conditions~10,100
WAHAWEBJS or WPP (browser), NOWEB (Node WebSocket), GOWS (Go WebSocket)TypeScriptApache 2.0~7,800
WuzAPIwhatsmeowGoMIT~1,050
WPPConnect ServerWPPConnect (browser)TypeScriptApache 2.0~1,060

Evolution API is the most popular in Brazil, with built-in integrations for Typebot, Chatwoot, n8n, Dify and OpenAI, and the option to switch to the official Cloud API. Its LICENSE adds two conditions to Apache 2.0: keep the logo and copyright in its UI components, and show users that Evolution API is in use.

WAHA lets you pick the engine per session, ships a dashboard and Swagger, and since its 2026.6 release the former Plus features are part of the main image.

WuzAPI is the lightweight option: whatsmeow talks to WhatsApp's WebSocket servers directly, with no headless Chrome, so it uses little memory and CPU.

Libraries

LibraryApproachLanguageLicense
BaileysWebSocket, no browserTypeScriptMIT
whatsmeowWebSocket, no browserGoMPL-2.0
whatsapp-web.jsHeadless browserJavaScriptApache 2.0
WPPConnectHeadless browserTypeScriptsee repo
VenomHeadless browserTypeScriptApache 2.0

Browser-based libraries are easier to reason about, because they do what WhatsApp Web does, but each session runs a browser. WebSocket libraries are lighter and break when WhatsApp changes its protocol until the library is updated.

When you want an app, not an API

These projects give you a pipe; you build the product on top. WACrew is a product built on Baileys: an open-source WhatsApp AI agent with a web panel, a queue by waiting time, voice note transcription, replies drafted in your voice and checked before sending, and an MCP server with 36 tools. If your goal is an agent answering clients, start there. If your goal is to connect your own system, pick one of the APIs above.

The shared caveat

WuzAPI's README says it plainly: using it against WhatsApp's terms can get your number banned, and commercial use at scale belongs on the official Business API. The same applies to every project on this page, WACrew included. Do not use them for spam or cold outreach.

FAQ

WAHA or Evolution API? Evolution API has more ready integrations and the Cloud API option. WAHA lets you choose the engine and ships a dashboard. Both are actively maintained.

Which one is the lightest? WuzAPI and anything on whatsmeow or Baileys, since there is no browser per session.

More in the comparisons index and the list of best WhatsApp APIs.