Open-source project
chatwoot/chatwoot avatar
chatwoot/chatwoot

Chatwoot: A self-hosted omnichannel support desk with a Ruby core and an AI agent

Open-source live-chat, email support, omni-channel desk. An alternative to Intercom, Zendesk, Salesforce Service Cloud etc. 🔥💬

39,931 stars9,712 forksRubyNOASSERTION

At a glance

What is it?
Chatwoot is an open-source alternative to Intercom and Zendesk that centralizes live chat, email, and social messaging into one inbox. It offers a built-in help center, automation, and an AI agent called Captain, but its deployment and maintenance demand careful environment configuration.
Who is it for?
Adopt Chatwoot if you need a self-hosted, open-source support desk that keeps customer data on your infrastructure and you have the operational capacity to manage a Ruby on Rails app, background jobs, and environment variables. Skip it if you want a zero-maintenance SaaS or lack time to read the environment variables documentation.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly Ruby, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • chatwoot/chatwoot39,931 ★ · +3,984
Star history
Repository2026-08-182026-11-15
chatwoot/chatwoot35.9k39.9k

3,984 Stars in the last 89 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What Chatwoot actually solves

Chatwoot targets teams that want an open-source alternative to tools like Intercom or Zendesk and want full control over customer data. It is a customer support platform that pulls conversations from live chat, email, Facebook, Instagram, Twitter, WhatsApp, Telegram, Line, and SMS into a single inbox. The README positions it as a direct alternative to those commercial desks, but with a self-hosted twist. For a small startup or a privacy-conscious company, the appeal is clear: you run the software on your own servers, so customer conversations never leave your infrastructure. The project also adds a help center portal for publishing articles and FAQs, which reduces repetitive queries, and an AI agent called Captain that can automate routine responses. The intended user is a team that wants the feature set of a modern support desk without the recurring subscription cost or the data residency concerns.

The architecture you get: Ruby, git-flow, and a develop branch

The repository is written in Ruby, and the README explicitly follows the git-flow branching model. The default branch is develop, not master. That is a signal: if you want a stable version, you must use the master branch or a tag like v1.x.x. The README warns that there might be breakages if you do not set the relevant environment variables. This is not a single-file script; it is a full web application with a backend, a frontend, and likely background workers, though the README does not list the exact components. The presence of a Docker image and a Helm chart on ArtifactHub suggests a containerized deployment is the intended path. The release cadence is active: v4.19.1 was released on October 24, 2026, with v4.19.0 and v4.18.0 before it. That frequency means you get fixes and features regularly, but it also means you must track releases if you self-host.

The Captain AI agent: what the README promises and what it leaves out

Captain is described as an AI agent that automates responses, handles common queries, and reduces agent workload. The README links to a separate documentation page (chwt.app/captain-docs) but gives no technical details about how it works. There is no mention of model providers, prompt configuration, or data flow. This is a gap. If you are evaluating Chatwoot for AI automation, the README does not say whether Captain runs on your infrastructure or calls an external API. That matters for privacy and cost. The README says Captain helps customers get instant answers, but it does not say how to enable it, what the pricing is, or whether it requires a separate service. You should treat Captain as an add-on that needs its own documentation review before you rely on it.

Deployment paths: Heroku, DigitalOcean, Docker, and Helm

The README highlights two one-click options: a Heroku deploy button and a DigitalOcean Kubernetes marketplace app. For other options, it points to a deployment page. The Docker image is on Docker Hub, and there is a Helm chart on ArtifactHub, so Kubernetes users have a path. The Heroku route is the simplest for a small team, but the README warns that you must set the correct environment variables or the app may break. That is a concrete constraint. You cannot just click deploy and walk away. You need to read the environment variables documentation to configure things like database credentials, secret keys, and likely email settings. The DigitalOcean option is a Kubernetes app. If you are not familiar with Kubernetes, that path has a learning curve.

The feature list: what is actually in the box

The README lists a long set of features under collaboration, customer data, integrations, and reports. Private notes, @mentions, labels, canned responses, auto-assignment, custom views, and business hours are standard for a support desk. Contact management, segments, campaigns, custom attributes, and pre-chat forms cover customer data. Integrations include Slack, Dialogflow, Shopify, Google Translate, and Linear. Reports include live view, conversation/agent/inbox reports, CSAT, and downloadable reports. This is a broad feature set for an open-source project. However, the README does not say which features are stable, which are experimental, or whether all channels work equally well. For example, WhatsApp and SMS often require external providers, and the README does not mention those dependencies. You should verify each channel you need against the help center documentation before assuming it works out of the box.

Maintenance, licensing, and upgrade cost

The project is released under the MIT License, according to the README, though the GitHub API shows NOASSERTION for the license field. That is a discrepancy worth noting. The README clearly states MIT, so you have a permissive license that allows commercial use and modification. The maintenance cost is real: you are running a Ruby application, which means you need to handle Ruby version upgrades, gem dependencies, and database migrations. The active release cycle (three releases between September and October 2026) means you will want to track releases for security fixes. The README points to a SECURITY.md file for reporting vulnerabilities, but it does not summarize any security policy. There is no mention of a paid support option, so you rely on the community Discord and documentation. If you are not comfortable with operational duties, this could be a burden.

Alternatives and when Chatwoot is the wrong tool

The obvious alternatives are Intercom, Zendesk, and Salesforce Service Cloud, but those are closed-source SaaS. The real open-source comparison is with something like Zammad or FreeScout. Chatwoot is a Ruby on Rails app with a broad channel list. If you need a lightweight, single-purpose email help desk, Chatwoot may be overkill. If you need deep CRM integration like Salesforce, Chatwoot's built-in features may not match. Also, if you cannot handle the environment variable setup, any self-hosted tool will be a poor fit. Chatwoot is the wrong tool if you want a fully managed service or if your team lacks Ruby or DevOps expertise.

What to verify before you adopt

First, read the environment variables documentation listed in the README. That is the single most important step, because the README warns of breakages without proper configuration. Second, check the help center to confirm that the channels you need are supported and that any external service requirements (like for WhatsApp or SMS) are documented. Third, decide on a deployment path: Heroku for a quick start, DigitalOcean Kubernetes for scalability, or Docker/Helm for your own cluster. Fourth, evaluate Captain separately, since its documentation is external and its data handling is unspecified. Finally, pin to a stable tag like v4.19.1, not the develop branch, for production. The git-flow model means develop is not stable. These are concrete actions you can take before writing any code.

Editorial conclusion

Adopt Chatwoot if you need a self-hosted, open-source support desk that keeps customer data on your infrastructure and you have the operational capacity to manage a Ruby on Rails app, background jobs, and environment variables. Skip it if you want a zero-maintenance SaaS or lack time to read the environment variables documentation. Before committing, verify your channel needs against the supported list (live chat, email, Facebook, Instagram, Twitter, WhatsApp, Telegram, Line, SMS) and confirm that the built-in help center and Captain AI meet your self-service and automation expectations. The project is actively released (v4.19.1 in October 2026) and uses git-flow, so pin to a stable tag rather than the develop branch for production.

Frequently asked questions

What does Chatwoot do?

Chatwoot is an open-source, self-hosted customer support platform that pulls conversations from many channels into a single inbox. It supports live chat on your website, email, Facebook, Instagram, Twitter, WhatsApp, Telegram, Line, and SMS, and adds a help center portal, campaigns, and the Captain AI agent.

how to install chatwoot docker

The repository ships a docker-compose.yaml for development that runs the Rails app, Sidekiq, Vite, Postgres, Redis, and Mailhog together, alongside docker-compose.production.yaml for production. For hosted installs there are one-click deployment options for Heroku and for DigitalOcean as a Kubernetes app.

is chatwoot open source

Yes. The project states it is released under the MIT License, with Chatwoot Inc holding copyright from 2017 to 2026, and positions itself as an open-source alternative to Intercom, Zendesk, and Salesforce Service Cloud.

what is chatwoot used for

Managing customer conversations from one inbox rather than several, publishing a self-service help center, and distributing work among agents. That includes auto-assignment based on availability, labels, custom views and filters, business hours, canned responses, and agent capacity management.

how to setup chatwoot

The Makefile has a setup target that runs gem install bundler, bundle install, and pnpm install, followed by database targets named db_create, db_migrate, db_seed, and db_reset. Local development then starts through Overmind using the Procfile.dev process file, with a run target that refuses to start if an instance is already running.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/chatwoot-chatwoot.svg)](https://hysenlabs.com/projects/chatwoot-chatwoot)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/chatwoot-chatwoot.svg)](https://hysenlabs.com/projects/chatwoot-chatwoot)

Was this useful?