rmyndharis /OpenWA

Free, Open Source, Self-Hosted WhatsApp API Gateway

★ 16,871⑂ 3,964👁 88⑃ 1,731● 294▤ 128
TypeScriptMITCreated 2026-02-02www.open-wa.org
Download: v0.30.2v0.30.2 ↓0.30.22026-11-15
+20
Daily
16,871
stars
3,964
forks
88
watchers
1,731
prs
294
issues
128
releases

README

OpenWA

  Open Source WhatsApp API Gateway



  Features •
  Quick Start •
  Docs •
  API •
  Contributing



  
  
  
  
  
  
  
  


---

 ✨ Why OpenWA?

OpenWA is a free, open-source WhatsApp API Gateway designed for developers who need full control over their messaging infrastructure—without vendor lock-in or hidden paywalls.

Built on a pluggable architecture, OpenWA lets you select database engines (SQLite/PostgreSQL), media storage backends (Local/S3), and an optional Redis (queue, rate limits, WebSocket fan-out) through configuration rather than application-code changes. The storage backend is the live store for status media and, when chat-media archiving is enabled, archived chat media; other message media is returned inline to API and webhook consumers. Of the media, scripts/backup.sh archives only the local media directory, so an S3 bucket needs a backup of its own.

|                               |                                                                                                                                          |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| 🔓 100% Open Source       | No licensing fees, no feature locks, full source code access                                                                             |
| 🏗️ Pluggable Architecture | Swap adapters for database and storage via config                                                                                        |
| 🖥️ Full Dashboard         | Modern React UI for session, webhook, and API key management                                                                             |
| 🔹 Multi-Session Ready    | Run multiple WhatsApp sessions concurrently on one instance                                                                              |
| 🐳 Docker Native          | Production-ready with zero configuration                                                                                                 |
| 🧩 Official Plugins       | Chatwoot, Typebot & more as sandboxed plugins on the Integration Fabric — OpenWA-plugins |
| 🔗 n8n Integration        | Community nodes for workflow automation                                                                                                  |
| 🧩 Community Adapters     | Third-party integrations (e.g. ioBroker) — see docs                                               |
| 🔐 Session-scoped keys    | Operator and viewer (reader) tokens can be limited to chosen sessions — or all sessions if none are selected                             |
| 🔒 Chat-scoped keys       | Those same tokens can also be limited to chosen chats — a few groups and contacts — so an agent on a shared account sees only its own    |

 Session-scoped operator & viewer tokens

When you create or edit an operator or viewer API key in the dashboard, you can tick the WhatsApp sessions that key may use.

Top issues

Discussions

Latest release

v0.30.2 v0.30.2 2026-11-15
Added

- Report poll votes as poll.vote on Baileys, as whatsapp-web.js already does. A vote is read while the poll's creation message is still in the session's message store (BAILEYS_MESSAGE_STORE_LIMIT); earlier votes are not backfilled (2063). Thanks @Shreyas1702003 for the report.

 Fixed

- whatsapp-web.js: an entry WhatsApp Web keeps in a chat that nobody sent (a group or security notice, or a kind the library does not list that carries neither text nor media) is no longer stored or announced as an unknown message, returned by the chat history, seeded as an empty status or reported as a c

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON