What Chatwoot actually is

Chatwoot is an open-source live-chat, email support, and omni-channel desk aimed at teams that would otherwise end up paying for Intercom, Zendesk, or Salesforce Service Cloud. It gives support and customer-facing teams a shared place to handle conversations instead of stitching together a chat widget, an inbox, and several increasingly expensive SaaS add-ons. The pitch is straightforward: keep the customer-support interface under your control, either by self-hosting it or using Chatwoot’s official cloud. This is a better fit for companies that want a real support desk with ownership and flexibility, not just a tiny “chat with us” bubble bolted onto a landing page.

Live GitHub stats

Chatwoot has 35758 GitHub stars, which is substantial evidence that it has escaped the usual open-source customer-support graveyard. It also has 1317 open issues, a number large enough to be useful as a warning signal: there is meaningful activity and user demand here, but also a lot of unresolved work and potential maintenance overhead.

GitHub lists the primary language as Ruby. The reported license is NOASSERTION, so there is no clean license label to quote from the supplied GitHub data; check the repository’s current licensing files before building a commercial deployment around assumptions about what you can modify, redistribute, or offer to customers. The last push date is 2026-08-12, which indicates recent repository activity as of that snapshot. Recent commits are not the same thing as a frictionless release process, but they are preferable to discovering that your supposedly active alternative has been untouched for years.

What it's good at

Chatwoot’s strongest use case is replacing the basic support stack around Intercom. Its description explicitly covers live chat, email support, and an omni-channel desk, which puts it in the category of tools used to manage ongoing customer conversations rather than one-off contact forms. That matters for teams that need support work to live in a shared system instead of inside individual employees’ inboxes.

It is also a reasonable candidate for teams evaluating Zendesk or Salesforce Service Cloud but wanting a more controllable deployment model. The appeal is not that Chatwoot magically eliminates support operations, staffing, or process design. It is that the software itself can be self-hosted, inspected, and integrated without making the vendor’s cloud the only place where customer conversations can exist.

The project’s size is another practical advantage. 35758 stars does not guarantee that every workflow will be polished, but it does suggest a much broader user base than the average “open-source Intercom alternative” launched last weekend. The tradeoff is visible in the 1317 open issues: this is a serious, active project, not a tiny codebase where every request can be handled by one maintainer before lunch.

What to watch for

The first thing to investigate is the license. GitHub reports NOASSERTION, and that is not a license; it is an absence of a reliable classification in the supplied data. Do not treat “open-source” in the project description as a substitute for reviewing the actual repository terms, especially if you plan to modify Chatwoot, redistribute it, or run it as part of a hosted service. Deployment difficulty is 3 of 5: manageable for an experienced technical team, but not necessarily a weekend checkbox exercise once production reliability, upgrades, backups, email delivery, and customer data are involved. The recent last push date of 2026-08-12 is a positive maintenance signal, while the 1317 open issues are a reminder that active does not mean finished.

How to deploy

Chatwoot supports both self-host and official-cloud. Self-hosting is the option for teams that need control over data and infrastructure, while the official cloud is the sensible route if operating a Ruby-based support platform is not part of the job description. Docker and Docker Compose are common deployment choices for this kind of application stack, but production setup still requires attention to persistence, upgrades, outbound email, and backups. See the Chatwoot deployment guide for the supported path rather than copying an untested Compose file from a random blog post.

Related tools

For more projects positioned as alternatives to Intercom, see the Intercom alternatives page.

For other projects positioned as alternatives to Zendesk, see the Zendesk alternatives page.