rmyndharis/openwa

Free, Open Source, Self-Hosted WhatsApp API Gateway

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 17 minutes ago
Added to GitGenius on September 1st, 2026
Created on February 2nd, 2026
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 3,221
Total Stargazers: 13,910 (+2)
Total Subscribers: 77 (+1)

Repository Insights (GitGenius)

Median issue/PR response: 4.1 hours
Mean response time: 2.2 days
90th percentile: 6.8 days
Tracked items: 217

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 12% of issues opened in the past year have been closed. Three people close 95% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 11
Closed in 7 days: 19
Avg open age: 30 days
Stale 30+ days: 2
Stale 90+ days: 0

Recent activity

Opened in 7 days: 6
Closed in 7 days: 18
Comments in 7 days: 16
Events in 7 days: 47

Top labels

  • bug (85)
  • enhancement (44)
  • needs-info (17)
  • question (7)
  • upstream-blocked (4)
  • not-a-bug (3)
  • documentation (2)
  • engine:baileys (2)

Detailed Description

OpenWA is a self-hosted WhatsApp API gateway that enables developers to build messaging applications and automations without relying on commercial services or official APIs.

The tool solves the problem of vendor lock-in and cost barriers for WhatsApp integrations by providing an open-source alternative that connects to WhatsApp through reverse-engineered clients rather than Meta's official Cloud API. It uses a pluggable architecture allowing developers to swap database engines (SQLite or PostgreSQL), storage backends (local or S3), and cache layers (disabled or Redis) through configuration alone. Message media is returned inline to API and webhook consumers rather than automatically persisted to storage. The project includes a React-based dashboard for managing sessions, webhooks, and API keys, supports multiple concurrent WhatsApp sessions on a single instance, and offers official plugins for integrations like Chatwoot and Typebot through a sandboxed Integration Fabric.

Developers should adopt this tool if they need full control over their messaging infrastructure and want to avoid vendor fees or feature restrictions. It suits projects requiring multi-session WhatsApp automation, custom integrations, or self-hosted deployments. The tool is production-ready with Docker support and zero-configuration deployment. However, potential users must understand that OpenWA is an unofficial, community-maintained gateway using reverse-engineered clients, not Meta's official API, which carries real consequences for stability and compliance that should be evaluated before connecting a phone number.

The project maintains active continuous integration with automated testing. Development activity shows ongoing work across multiple areas including core functionality, plugin ecosystem expansion, and community adapter support through documented third-party integrations.