WACrew

Guide

A self-hosted WhatsApp AI inbox and CRM, open source

An open-source, self-hosted WhatsApp inbox with AI replies and a light CRM: every group and chat sorted by wait time, voice notes transcribed, replies in your voice and an MCP server for coding agents.

Updated 2 min read
On this page
  1. What you get
  2. How it is deployed
  3. Costs
  4. Honest limits
  5. Compared with other self-hosted options
  6. FAQ

Most WhatsApp inboxes with AI are SaaS: your client conversations live on someone else's servers, priced per seat or per conversation. If you would rather keep them on your own server, the open-source options narrow quickly. WACrew is one built for people who serve clients over WhatsApp, often in groups.

What you get

  • An inbox sorted by wait time. Every group and direct chat in one queue, oldest wait first. A client's group and private chat appear together; back-to-back messages collapse into one block.
  • Voice notes as text. Whisper large-v3, locally on Apple Silicon or through an API.
  • AI replies in your voice. Style measured from your own messages, reviewed by more than 25 code rules before sending, delivered with read receipt, typing and pauses.
  • Your call, per chat. Confirm mode by default; autonomous mode where you choose. Every message records who wrote it: you on the phone, you on the panel, a teammate or the AI.
  • A light CRM. Notes, tags, contract state and dates, deliveries per client and a dashboard with signals such as a renewal coming up.
  • Team access per conversation, Google Calendar in the panel and a live 2D office where a client's desk turns red when they write.
  • An MCP server with 36 tools, so Claude Code, Codex or Cursor can work the same inbox. See the tools.

How it is deployed

OptionWhat you do
Railway templateOne click; volume, login and password generated
Any VPSdocker compose up -d with PANEL_USER and PANEL_PASS
Prebuilt imageghcr.io/sumioshi/wacrew with a volume at /data
Your Macnpm run dev, with local MLX transcription

Data lives in data/<chat>/ as JSONL plus media and transcripts, easy to back up and inspect.

Costs

The code is free (Apache 2.0). You pay for the server if you run it in the cloud, and for the AI provider you choose, with your own key.

Honest limits

  • Not the official API. WACrew links as an extra device through Baileys. It is for people who already talk to you; bulk and cold messaging can get a number banned.
  • No history before pairing. Capture starts when you scan the QR code.
  • One number per deployment.
  • Not a marketing tool. No broadcast campaigns or chatbot flows.

Compared with other self-hosted options

Chatwoot is a general open-source support inbox with WhatsApp channels; Evolution API and WAHA are APIs you build on; lharries/whatsapp-mcp and its forks give an agent tools without an inbox. WACrew sits between them: an inbox and agent for one person or a small team answering clients. More in open-source WhatsApp CRM and the comparisons.

FAQ

Can my team use it? Yes. Mark who is on your team at setup, and grant access per conversation.

Do I need an AI key? For AI replies, video watching and API transcription, yes, from the provider you choose. Local transcription on a Mac runs without one.

Where are my messages stored? On your server, in the data volume. Nothing goes to WACrew, which has no hosted service.