Chatwoot vs FreeScout: Choosing a Self-Hosted Support Platform (2026)
Chatwoot and FreeScout are both self-hosted customer support platforms with open-source roots. But they are not interchangeable — Chatwoot is a full omnichannel support suite, while FreeScout is a lean shared inbox focused on email. Picking the wrong one means either over-engineering a simple email workflow or under-building when live chat is a requirement.
TL;DR
| Chatwoot | FreeScout | |
|---|---|---|
| License | MIT | AGPL-3.0 |
| GitHub stars | ~29,000 | ~3,500 |
| Stack | Ruby on Rails + Vue.js | PHP / Laravel |
| Idle RAM | ~1.2 GB | ~256 MB |
| Channels | Live chat, email, WhatsApp, Facebook, Twitter/X, Telegram, API | Email only |
| Live chat widget | ✓ | ✗ |
| Plugin ecosystem | ✗ (integrations via webhooks/API) | ✓ (PHP modules) |
| Funding status | No public funding in 2+ years | Self-sustained (no known VC backing) |
What each tool does
Chatwoot: omnichannel support
Chatwoot is a Rails application that aggregates customer conversations from multiple channels into a shared team inbox. An agent can reply to a live chat widget message, a WhatsApp message, an email, or a Telegram message from the same interface. Key capabilities:
- Live chat widget embeds on your website (JavaScript snippet)
- Email inbox connects via SMTP/IMAP
- Social channels: WhatsApp Business API, Facebook Messenger, Twitter/X DMs, Telegram
- API channel: custom integrations that push messages into Chatwoot via REST
- CSAT surveys, labels, assignment rules, and canned responses
- Webhooks fire on conversation events (useful for n8n or Make integrations)
Sustainability note: Chatwoot has not announced new funding in more than two years as of 2026-05-03. The project remains active on GitHub, but teams with long upgrade cycles should monitor the project health before committing to it as critical infrastructure.
FreeScout: email shared inbox
FreeScout is a PHP/Laravel application that provides a multi-mailbox shared inbox for support teams. It is explicitly email-only — no live chat, no social channels. Key capabilities:
- Multi-mailbox with per-mailbox IMAP/SMTP configuration
- Conversation assignment and collision detection
- Saved replies (canned responses)
- Customer portal (optional)
- Plugin ecosystem with paid and free PHP modules (Zapier integration, Telegram notifications, custom fields, and more)
- Very low RAM — runs on a 2 GB VPS alongside other services
FreeScout is the conservative choice: a decade-proven architecture (it is inspired by HelpScout), simple PHP deployment, and no background Ruby job workers eating memory.
Feature comparison
| Feature | Chatwoot | FreeScout |
|---|---|---|
| Email inbox | ✓ | ✓ |
| Live chat widget | ✓ | ✗ |
| WhatsApp Business | ✓ | ✗ (plugin available) |
| Facebook Messenger | ✓ | ✗ |
| Telegram | ✓ | ✗ (notification plugin only) |
| Twitter/X DMs | ✓ | ✗ |
| API channel | ✓ | ✗ |
| Webhooks on events | ✓ | ✓ (limited) |
| CSAT surveys | ✓ | ✗ (plugin) |
| Collision detection | ✓ | ✓ |
| Assignment rules | ✓ | ✓ |
| Reports / analytics | ✓ | Basic |
| Plugin ecosystem | ✗ | ✓ |
| Mobile apps | ✓ (iOS + Android) | ✗ |
RAM and infrastructure
Chatwoot is a Rails app with Sidekiq for background jobs. It is memory-hungry:
| Container | Idle RAM |
|---|---|
| chatwoot (Rails) | ~520 MB |
| chatwoot-sidekiq | ~380 MB |
| PostgreSQL | ~200 MB |
| Redis | ~20 MB |
| Total | ~1,120 MB |
A 4 GB Managed VPS is the minimum comfortable tier for Chatwoot alone. On an 8 GB VPS you can co-locate Chatwoot with Twenty CRM or Listmonk — as demonstrated in the Twenty CRM + Chatwoot stack guide.
FreeScout runs on PHP-FPM behind Nginx:
| Container | Idle RAM |
|---|---|
| freescout (PHP-FPM + Nginx) | ~180 MB |
| MySQL/MariaDB | ~150 MB |
| Total | ~330 MB |
FreeScout leaves enough headroom on a 2 GB VPS to run alongside Listmonk, Twenty CRM, or another lightweight tool.
Chatwoot's funding situation
Chatwoot raised funding early in its life and grew quickly. As of 2026-05-03, there has been no public announcement of new funding in more than two years. The GitHub repository is active — issues are being addressed and releases are shipping — but the pace has slowed compared to 2022–2023.
For teams building critical customer support infrastructure, this is worth factoring in. FreeScout, by contrast, is a PHP project with a more conservative maintenance model: fewer features, but the kind of codebase that a competent PHP developer can fork and maintain independently if upstream activity ever stalls.
Which should you choose?
Choose Chatwoot if:
- You need a live chat widget on your website
- You support customers via WhatsApp, Facebook, or Telegram
- Your team handles conversations across multiple channels from one inbox
- You can absorb 1.2 GB idle RAM and want mobile apps for your agents
Choose FreeScout if:
- Your support workflow is entirely email-based
- You are running on a small VPS (2–4 GB) and need low overhead
- You want a plugin ecosystem to extend functionality incrementally
- The PHP deployment model is easier for your team to maintain long-term
- Chatwoot's funding uncertainty is a dealbreaker for your risk tolerance
Both tools are free to self-host. FreeScout's plugin marketplace has paid modules, but the core is AGPL-3.0 and fully functional without them.
Further reading
- Self-Host Chatwoot — Docker Compose setup, channel configuration, and sustainability flag details
FreeScout does not have a native live chat plugin that matches Chatwoot's capability. Third-party JavaScript widgets (Crisp, Tawk.to) can be embedded on your site independently, but they won't integrate into FreeScout's inbox natively. If live chat is a near-term requirement, Chatwoot is the better starting point — migrating email threads between tools later is painful.
Yes. The WhatsApp Business API channel requires a Meta Business account and a WhatsApp Business phone number, which has its own approval process. Chatwoot's email inbox and live chat widget work without any third-party API setup. You can start with email + live chat and add WhatsApp later once your Meta account is approved.
FreeScout supports an unlimited number of mailboxes in the core product. Each mailbox connects to an IMAP account for fetching and an SMTP account for sending. Agents can be assigned to specific mailboxes, and conversations are isolated per mailbox. This makes FreeScout well-suited for companies that support multiple brands or departments from a single instance.