The best open-source and self-hosted WhatsApp CRMs in 2026

If you want to run WhatsApp for your business without renting a seat on someone else's cloud, the open-source world has real options — but they are not interchangeable. Some are full CRMs, some are support desks, and some are just API gateways you assemble yourself. This guide sorts them out honestly, tells you what each is genuinely best for, and flags the one technical decision that matters more than any feature list.

Want the fundamentals first? See our complete guide to WhatsApp CRM.

Disclosure: wacrm publishes this guide, and we list our own project first for the specific "WhatsApp CRM" use case. We also tell you plainly where Chatwoot, Frappe CRM, and others are the better choice — because a roundup that only pushes its own tool isn't worth reading.

The one decision that matters most: official API vs WhatsApp Web

Before features, settle this. Open-source WhatsApp tools connect in one of two ways:

• The official WhatsApp Business API (Cloud API) — sanctioned by Meta. Stable, compliant, and safe for a business number.
• WhatsApp Web emulation (e.g. the Baileys library, used by some gateways) — connects by pretending to be the WhatsApp Web client. This is against WhatsApp's Terms of Service and can get your number banned.

For anything your business depends on, choose tools built on the official API. Web-emulation is fine for a throwaway experiment and a real risk for a number you can't afford to lose. We flag which camp each tool below falls into.

At a glance

Tool	What it is	Official API	Best for
wacrm	WhatsApp CRM (inbox + pipelines)	Yes	A WhatsApp sales/CRM on the official API
Chatwoot	Omnichannel support desk	Yes (Cloud API/Twilio)	Multichannel customer support
Frappe CRM	General CRM + WhatsApp add-on	Yes (via add-on)	Teams already on Frappe/ERPNext
Whatomate	WhatsApp calling / IVR / messaging	Yes	Voice, IVR, and messaging flows
Evolution API	WhatsApp API gateway	Both (incl. Web-emulation)	Developers building a custom stack

All are open source and self-hostable. Meta's messaging fees apply to any tool on the official API. Licenses and features change — check each project's repo before committing.

1. wacrm — a focused WhatsApp CRM

What it is: An MIT-licensed WhatsApp CRM: shared team inbox, contact hub, sales pipelines (kanban), broadcasts, no-code automations, and analytics, built on the official WhatsApp Business API. Data lives in your own Supabase project; it deploys on Hostinger Managed Node.js Hosting in about 30 seconds.

Best for: Teams that want a genuine WhatsApp CRM — pipelines and deals, not just a support inbox — with no per-seat cost and full data ownership. Lean teams and agencies who fork and rebrand it per client.

Watch-outs: WhatsApp-only by design — if you need email, SMS, or social in one inbox, look at Chatwoot. It's a younger project than the incumbents.

See the free open-source WhatsApp CRM guide for the full cost breakdown, or Getting started to try it.

2. Chatwoot — the open-source support desk

What it is: An MIT-licensed (Community Edition), omnichannel customer-support platform — live chat, email, WhatsApp (via Cloud API or Twilio), Instagram, Facebook, Telegram, SMS — with a shared inbox, routing, canned responses, and agent assignment. It has 50,000+ self-hosted installations.

Best for: Support teams that want a true multichannel help desk and treat WhatsApp as one channel among many. The most mature, battle-tested option here.

Watch-outs: It's a support desk, not a sales CRM — no native deal pipelines. The stack is heavier to self-host (Rails, PostgreSQL, Redis, a background worker), so it needs a real server, not a free tier.

3. Frappe CRM — if you already live in Frappe

What it is: A full open-source CRM in the Frappe/ERPNext ecosystem, with a clean modern UI and a WhatsApp integration (via the Frappe WhatsApp app) to send and receive messages from inside the CRM.

Best for: Businesses already running Frappe or ERPNext, who want their CRM, helpdesk, and accounting to share one data layer.

Watch-outs: WhatsApp is an add-on rather than the core, advanced tweaks lean on the Frappe framework (some coding), and it makes the most sense inside the Frappe stack rather than as a standalone WhatsApp tool.

4. Whatomate — WhatsApp calling and IVR

What it is: An open-source, self-hosted WhatsApp platform focused on inbound/outbound calling, a visual IVR builder, recordings, and messaging automation — with a native suite for the Frappe ecosystem.

Best for: Teams whose priority is WhatsApp voice and IVR flows rather than a sales pipeline.

Watch-outs: Narrower than a full CRM; strongest when paired with the Frappe ecosystem.

5. Evolution API — a gateway for developers

What it is: An open-source WhatsApp API gateway. It can run on the official Cloud API or, by default, via Baileys WhatsApp Web emulation, and is often combined with Chatwoot, n8n, or Typebot to assemble a custom stack.

Best for: Developers building their own WhatsApp automation from parts and comfortable operating infrastructure.

Watch-outs: It's a building block, not a CRM — you supply the interface and logic. And if you use its Web-emulation mode, mind the ban risk covered above; prefer its official Cloud API mode for business numbers. The same caveats apply to bare gateways like WAHA and OpenWA.

How to choose

• You want a WhatsApp CRM with pipelines, on the official API, cheaply → wacrm.
• You want an omnichannel support desk → Chatwoot.
• You already run Frappe/ERPNext → Frappe CRM.
• You need WhatsApp voice/IVR → Whatomate.
• You're a developer assembling a custom stack → Evolution API (or WAHA/OpenWA) on the official Cloud API.

Whatever you pick, favour tools on the official WhatsApp Business API, and remember the software being free doesn't remove Meta's messaging cost or your hosting bill — it removes the per-seat SaaS tax and hands you the data.

If a focused WhatsApp CRM is what you're after, wacrm is a fork away — start with Getting started or read the wacrm vs Kommo and wacrm vs Trengo comparisons if you're weighing it against hosted tools.