DEV Community

Cover image for Chatwoot: reading the license before the landing page
Evgeniy Uryadov
Evgeniy Uryadov

Posted on Originally published at automata.sale

Chatwoot: reading the license before the landing page

I went through Chatwoot's licenses, pricing page and code this week. Here's my read, because the popular one-liner ("free Intercom alternative") hides the actual shape of the deal.

The license is a folder

The root LICENSE is MIT Expat. Short and clear: everything outside the enterprise/ directory is open. The enterprise/ directory carries its own license, and I read that file too: production use requires an agreed subscription for the correct number of seats.
So the accurate sentence isn't "Chatwoot is open source". It's "Chatwoot's core is open source and one folder is source-available commercial code". The repository looks monolithic. The legal boundary is a directory.
What that buys you: read, fork, modify and self-host the core for free. What it doesn't: enterprise features in production without paying. That's a normal open-core model, and what makes it fair is that the line is documented in the repo, not buried in a pricing page.

What the community edition actually does

No agent cap. All channels: web chat, email over Gmail/Outlook/IMAP-SMTP, WhatsApp, Instagram, Messenger, Telegram, Line, SMS, X. A help center with your own domain and SSL, multiple portals, canned responses, labels, teams, automation rules, business hours, CSAT reports, the API and webhooks.
For a small support team this is a product, not a trial, and that surprised me in a good way. The missing pieces are exactly what costs the vendor money or what procurement asks for: Captain AI, voice calls, custom branding, roles and permissions, SSO/SAML, SLA policies, audit logs.

The bill has two halves

Cloud, per agent per month: Hacker $0 (2 agents, 500 conversations, live chat only), Startups $19 (all channels, 300 Captain credits), Business $39 (adds voice, teams, automation, 500 credits), Enterprise $99 (adds SSO/SAML and audit logs, 800 credits). Extra credits are $20 per 1,000.
Self-hosted, per agent per month: Community $0, Premium Support $19 (adds Captain, voice, branding, capacity, roles, priority email), Enterprise $99 (adds SSO/SAML, SLA, phone support with engineering office hours).
The half people skip: at $19 per agent you buy a license, not infrastructure. You still own the server, PostgreSQL, Redis, backups, monitoring, security patches and the upgrade treadmill. For five agents that's $95 a month plus a VPS plus your time. Cheap against enterprise Zendesk. Not free against doing nothing.

If you want AI, be precise about which AI

Captain is not in the free edition. It's a managed product with credits. The vendor confirms the workaround: Agent Bots, webhooks and the API let you connect your own model and pay only for tokens. More engineering, less polish, but the whole stack stays open and the data stays yours.

Stack and ops reality

Rails 8.0.5 with Sidekiq 7.3 and Redis, PostgreSQL, Vue 3.5 with Vite 6 and Tailwind on the front, Node 24 and pnpm 10 for assets. Docker, Helm and Kubernetes paths are documented.
A mature monolith. Good for stability, bad for tinkering. Upgrades are Rails upgrades: migrations, asset rebuild, restart, sometimes a breaking configuration change. I've operated enough Rails apps to know this is boring in the good way, but if you haven't, budget a day for the first deploy and a few hours per upgrade cycle.
Deployment surface is the usual self-hosted trio: a reverse proxy with TLS, a database with backups, and a supervised queue worker. Nothing exotic. Nothing automatic either.

Who it fits

A support team that wants its conversations in its own database, several channels in one inbox, and will run a Rails app. I'd take that trade. A company that needs SSO and SLA pays $99 per agent and still saves against enterprise Zendesk. A developer embedding support into a product will find API and webhooks enough.
Not a team with nobody to operate a server. Not anyone expecting free AI. I'd say this plainly to anyone who asks me whether to self-host it.

One last thing worth noticing. Last week I reviewed cal.diy, the fork Cal.com handed out after closing its source. Chatwoot is the opposite choice: the core stays open and a folder plus a managed AI are monetized. For a buyer the question is identical in both cases: where is the line, and will it move? With Chatwoot the line is written in the repository, which is the most you can ask.

This article was prepared with AI assistance (drafting and adaptation) and reviewed by the author before publishing.
Originally published at https://automata.sale/en/blog/development/chatwoot-open-source-helpdesk/
tags: opensource, selfhosting, webdev, rails

Top comments (0)