Latest release What's new

Open Source WhatsApp API Gateway

The free, self-hosted WhatsApp HTTP API for developers who want to own their stack. Runs on your own server, MIT licensed, with no vendor lock-in.

  • 100% free
  • Open source
  • Self-hosted
01 / Capabilities

Sessions, messages, groups and webhooks over one API

A complete WhatsApp integration platform, free and open source, with no feature locks

Core

  • Full REST API
  • Multi-session support
  • Real-time webhooks (HMAC)
  • Web dashboard (15 locales)
  • Scoped API key auth
  • Swagger docs

Messaging

  • Text messages
  • Images & videos
  • Documents & audio
  • Message reactions
  • Bulk messaging
  • Delivery status

Advanced

  • Groups API
  • Channels & newsletters
  • Labels management
  • Proxy per session
  • CIDR IP whitelisting
  • Rate limiting & audit

Infrastructure

  • SQLite or PostgreSQL
  • Redis cache & queues
  • S3 or MinIO storage
  • Multi-arch Docker
  • Non-root container
  • Health checks & migrations
02 / Architecture

Built on a pluggable core

Swap your database, storage, cache and even the WhatsApp engine from config, with no code changes

Pluggable architecture

Database (SQLite / PostgreSQL), storage (Local / S3 / MinIO) and cache (Memory / Redis) are swappable adapters: configured, not coded. Move from local dev to production scale without touching application logic.

Dual WhatsApp engine

Choose your engine per deployment via ENGINE_TYPE. Ship with whatsapp-web.js by default, or switch to the lightweight baileys WebSocket engine when you'd rather skip the browser entirely.

03 / Comparison

OpenWA next to three WhatsApp API providers

Feature comparison between OpenWA and three commercial WhatsApp API providers
Feature OpenWA W. Core W. Plus W. Cloud
Price Free forever Free $50+/mo $30+/mo
Open source Yes No No No
Multi-session Yes Limited Yes Yes
Web dashboard Yes No Yes Yes
PostgreSQL Yes No Yes N/A
Webhook UI Yes No Yes Yes
Source code Yes No No No
Self-hosted Yes Yes Yes No

Comparison reflects publicly available feature listings as of 2026. Competitor names are abbreviated. Features and pricing may change, so verify on their official sites before deciding.

04 / Quick start

Three commands to a running gateway

Docker for a single-container start, or a local setup with hot reload for development

Terminal
# Clone and start with Docker (single-container quick start)
git clone https://github.com/rmyndharis/OpenWA.git
cd OpenWA
docker compose -f docker-compose.dev.yml up -d

# Dashboard & API are bundled on one port:
# http://localhost:2785
Terminal
# Clone and run locally
git clone https://github.com/rmyndharis/OpenWA.git
cd OpenWA

# Install dependencies (includes dashboard)
npm install

# Start API + Dashboard with hot reload
npm run dev

# Dashboard: http://localhost:2886
Dashboard:2785
REST API:2785/api
Swagger:2785/api/docs

In npm run dev (local) the dashboard runs on its own Vite server at :2886 with hot reload. In Docker it's bundled into the API image and served on :2785. For production, deploy using docker compose up -d, with optional scaling profiles: --profile postgres, --profile redis, --profile minio, or --profile full.

05 / Tech stack

NestJS on Node.js, with React for the dashboard

Tools chosen for reliability, not novelty

Node.js 22
NestJS 11
TypeScript 6
React 19
PostgreSQL
Redis + BullMQ
Docker multi-arch
Socket.IO

TypeORM for data access. Vite, TanStack Query and i18next power the dashboard. Helmet and NestJS Throttler harden the API. Pluggable WA engine: whatsapp-web.js (default) or baileys via ENGINE_TYPE.

07 / Plugins

Build a plugin without forking the gateway

A plugin comes alive on real WhatsApp events through typed lifecycle hooks. It can send replies, query chats and contacts and reach your own services, all behind a permission-gated API, with no core changes.

index.ts
// manifest.json
// "hooks": ["message:received"]
// "permissions": ["messages:send"]

export default class AwayNotice implements IPlugin {
  async onEnable(ctx: PluginContext) {
    ctx.registerHook('message:received', async (hook) => {
      const m = hook.data as IncomingMessage;
      if (hook.sessionId && !m.fromMe) {
        await ctx.messages.reply(
          hook.sessionId, m.chatId, m.id, 'Back at 9:00',
        );
      }
      return { continue: true };
    });
  }
}
  • after-hours
  • ai-responder
  • chat-flow
  • chatwoot-adapter
  • faq-bot
  • group-translate
  • gsheets-logger
  • http-action
  • supabase-otp-hook
  • typebot-connector
  • voice-transcription
08 / Changelog

Release notes, straight from CHANGELOG.md

Pulled live from the repository, with no copy-paste

Loading the latest releases…

View full changelog on GitHub
09 / FAQ

Frequently asked questions

Yes. OpenWA is 100% free and open source under the MIT license, with no licensing fees, no feature locks and full source code access. You can use it in personal and commercial projects without any restrictions.

No. OpenWA is an independent, community-driven open-source project and has no affiliation, association, authorization, endorsement, or official connection with Meta Platforms, Inc., WhatsApp LLC, or any of their subsidiaries or affiliates.

This software is developed independently to help developers integrate WhatsApp capabilities into their own applications using self-hosted infrastructure. All registered trademarks and logos belong to their respective owners.

Yes, there is always some risk. WhatsApp's anti-abuse systems look for unofficial automation, and no gateway can bring that risk to zero. Use a dedicated number you can afford to lose, never your primary one.

The two engines trade off differently. whatsapp-web.js drives a real headless Chromium, which looks like genuine WhatsApp Web traffic but uses more memory. baileys uses far less memory but is easier for WhatsApp to fingerprint.

OpenWA gives you controls that lower the chance of being flagged:

  • Simulated typing before each send, on by default
  • Randomized delays between bulk messages, on by default
  • A proxy per session
  • Send pacing with a per-session daily cap, off by default (SEND_PACING_ENABLED)

To keep your account safe, warm up new numbers, avoid cold outreach, and use OpenWA for replies and alerts to people who expect to hear from you.

Yes. OpenWA is designed for self-hosting with Docker. The API and the dashboard are bundled together on port 2785, making it easy to deploy to any cloud provider, VPS, or local server.

The default engine is whatsapp-web.js (a Puppeteer-based headless browser). You can also switch to the lightweight baileys engine (a WebSocket-based implementation) via the ENGINE_TYPE environment variable to save resources and run browserless.

Yes. OpenWA's pluggable architecture lets you swap the database (SQLite / PostgreSQL), media storage (Local / S3 / MinIO), and cache layer (Memory / Redis) purely from configuration without changing any code.

10 / Community

Built in the open

OpenWA is open from the first commit to the latest release. MIT licensed, free forever, and open to contributions of every kind: code, documentation, or a well-written bug report.

MITLicense
100%Free
OpenSource

How to contribute

  1. 01Fork the repository
  2. 02Create your feature branch
  3. 03Commit your changes
  4. 04Push to the branch
  5. 05Open a pull request

The people behind OpenWA

Every developer who has shipped code, docs or fixes, pulled live from GitHub. Thank you.

Loading contributors…