“"Whatever is MIT now, will stay as MIT" — pranav_rajs, Chatwoot founder, Hacker News (https://news.ycombinator.com/item?id=26501527), 2021”
You're running customer support across WhatsApp Business, email, Instagram DM, and live chat simultaneously. Your agents switch between five browser tabs, lose conversation context between channels, and have no way to see that the angry email and the WhatsApp follow-up are from the same customer. Hosted solutions like Intercom start at $74/seat/month and lock your conversation data behind their API. You need data residency, a sub-$10/seat cost, and full API access — none of which the incumbents give you.
You deploy Chatwoot on your own server using Docker Compose — it runs a Rails API, a Vue.js dashboard, PostgreSQL for storage, Redis for queuing, and ActionCable for real-time WebSocket delivery. You connect your channels (WhatsApp Business API credentials, email IMAP/SMTP, Facebook App tokens, etc.) through the admin panel. Every inbound message — regardless of channel — creates or updates a unified conversation object in PostgreSQL, which your agents see in one inbox sorted by priority and assignment. Captain, the AI agent layer, uses retrieval-augmented generation over your help center articles and past conversation history to auto-draft or auto-send tier-1 replies; it runs on Chatwoot's own inference backend, so you don't configure an OpenAI key.
If you're an engineering or DevOps lead at a startup or mid-sized company with existing Docker infrastructure, and your support team is drowning in tab-switching between WhatsApp, email, and Instagram — Chatwoot is built for your setup. It's also the right call if you operate in a sector where data residency requirements rule out SaaS tools or where per-seat costs from Intercom or Zendesk would exceed $500/month at your team size. Not yet the right fit if you need mature out-of-the-box voice/phone support (WhatsApp/Twilio calling only landed in v4.14.1, May 2026) or if no one on your team can...
Chatwoot is production-proven by adoption numbers (15,000+ businesses, SOC 2 Type II) and by release velocity (monthly releases, v4.12–v4.14 in 90 days). The primary risk is self-hosted operational complexity — you manage Sidekiq, Redis, PostgreSQL, and S3 alongside the Rails app. Meta channel integrations (Facebook and Instagram) are the most fragile surface, acknowledged by the maintainer as structurally dependent on Meta's app review cycle. If your support volume is email-first or WhatsApp-first, that fragility matters less.
Deep-dive insight, Easy and Pro modes, plus action playbooks — the full breakdown is one tap away.