Chatwoot: what an open-source helpdesk really costs
This is an adapted English version. Original (Russian): automata.sale/blog/development/chatwoot-otkrytaya-sluzhba-podderzhki/
There are two ways to sell open-source software in 2026. Cal.com chose one: close the production repository, hand the community a trimmed fork, keep the roadmap. Chatwoot chose the other: leave the core under MIT, put the commercial features in a directory with its own license, and sell subscriptions on top.
Both are legitimate. The difference is what you can count on two years from now. So let me read Chatwoot the same way I read cal.diy last week: what is open, what is paid, what it takes to run, and who should bother.
What Chatwoot is
A customer support platform you can host yourself. One inbox for website chat, email, WhatsApp, Instagram, Messenger, Telegram, Line, SMS and X. Plus a help center with its own domain and SSL, canned responses, labels, teams, automation rules, business hours, CSAT reports, and an API with webhooks.
The positioning on the site is blunt: an open-source alternative to Intercom and Zendesk. The repo has about 40,000 stars and 9,700 forks, the latest release is v4.19.1 from October 24, 2026, and the vendor claims 15,000+ businesses and SOC 2 Type II plus GDPR compliance.
For a Russian B2B audience there is an extra argument that has nothing to do with features: when you self-host, customer conversations and contact data sit in your database on your server. That is a compliance answer, not a marketing one.
The license line that matters
Chatwoot’s root LICENSE is short and unusually honest. Everything outside the enterprise/ directory is MIT Expat. The enterprise/ directory has its own license file, and that file says production use requires an agreed subscription for the correct number of seats.
So the correct sentence is not “Chatwoot is open source”. It is “Chatwoot’s core is open source, and one directory is source-available commercial code”. The repository looks monolithic, but the legal boundary is a folder.
Practically it means you can read, fork, modify and self-host the core for free. You cannot legally run the enterprise features in production without paying. That is a normal open-core model. What makes it fair is that the line is documented in the repo instead of hidden in a pricing page.
What the free edition actually does
The community edition is not a demo. No agent cap, all the channels, the help center, canned responses, labels, teams, automation rules, reports, the API and webhooks. For a small support team this is a working product, not a trial.
What is missing is exactly the part that costs the vendor money to run or that enterprises ask for in procurement: Captain AI, voice calls, custom branding, roles and permissions, SSO/SAML, SLA policies, audit logs.
What costs money
Two buying paths, and they are easy to confuse.
Cloud, per agent per month: Hacker $0 with 2 agents, 500 conversations and live chat only; Startups $19 with all channels and 300 Captain credits; Business $39 adds voice, teams and automation with 500 credits; Enterprise $99 adds SSO/SAML and audit logs with 800 credits. Extra Captain credits are $20 per 1,000.
Self-hosted, per agent per month: Community $0; Premium Support $19 adds Captain, voice, custom branding, agent capacity, roles and priority email; Enterprise $99 adds SSO/SAML, SLA policies and phone support with engineering office hours.
The number people miss is the second half of the bill. 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 is $95 a month plus a VPS plus your time. Cheap against Zendesk, not free against doing nothing.
And here is the honest counterweight: if AI support is the goal, the free edition does not include it. Captain is the paid brain. The workaround exists and the vendor confirms it: Agent Bots, webhooks and the API let you wire your own model and pay only for tokens. That is more engineering and less polish, but it keeps the whole stack open.
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, DigitalOcean Kubernetes and a manual install are all documented.
This is a mature monolith, and that is good news for stability and bad news for tinkering. Upgrades are Rails upgrades: migrations, asset rebuild, restart, sometimes a breaking change in configuration. If you have never operated a Rails app with background jobs, budget a day for the first deployment and a few hours per upgrade cycle.
The deployment surface is the usual self-hosted trio: a reverse proxy with TLS, a database with backups, and a queue worker that must be supervised. Nothing exotic, nothing automatic either.
Two models, one lesson
Cal.com last week and Chatwoot today are the same story from opposite ends. Cal.com kept the code and closed it, then handed out a snapshot. Chatwoot kept the core open and monetized a folder plus a managed AI.
For a buyer the practical 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. With a closed snapshot the line is whatever the vendor decides next quarter.
Who it fits
A support team that wants its conversations in its own database, several channels in one inbox, and is willing to run a Rails app. A company that needs SSO and SLA will pay $99 per agent and still save against enterprise Zendesk. A developer who wants an open base to embed into a product will find the API and webhooks sufficient.
It does not fit a team with no one to operate a server. And it does not fit anyone who expects free AI: the free edition has no Captain, and connecting your own model is a project, not a checkbox.
We build and run client infrastructure at automata.sale, so the operational part is familiar: the open-core split is not the problem, unmanaged servers are.
📞 +7 (906) 311-77-69 · ✉ hello@automata.sale · 💬 Telegram: @automatasale · 🌐 automata.sale
ИП Урядов Евгений Евгеньевич · ИНН 645112058391 · ОГРНИП 312645301900058 Работаем по России, Беларуси и Казахстану
Frequently asked questions
Is Chatwoot free?
The core is free: everything outside the enterprise directory is MIT Expat, and the community edition has no agent cap. Captain AI, voice calls and SSO are not included, they belong to the paid tiers.
What license is the enterprise directory under?
A separate Chatwoot Enterprise License. It allows production use only with a paid subscription for the correct number of seats. So the repository is open source except one directory, which is source-available commercial code.
How much does self-hosted Chatwoot cost?
Community edition is $0 per agent. Premium Support is $19 per agent per month and adds Captain, voice, custom branding and roles. Enterprise is $99 and adds SSO/SAML and SLA policies. Server, database, backups and upgrades are yours in all three cases.
Can I use my own AI instead of Captain?
Yes. The community edition exposes Agent Bots, webhooks and an API, so you can connect your own model and pay only for tokens. Captain is a managed product with credits, not the only way to get automated replies.
What is Chatwoot built on?
Ruby on Rails 8 with Sidekiq and Redis on the backend, Vue 3 and Vite with Tailwind on the frontend, PostgreSQL for storage, Node 24 and pnpm 10 for the asset build. Docker, Helm and Kubernetes deployments are documented.