What Is Chatwoot? The Open-Source Customer Engagement Platform (2026)

This guide is a plain-English explainer of what Chatwoot actually is: how it's positioned, the core capabilities it ships, the licensing nuance that trips people up (it's MIT for the core, not for everything), how self-hosting compares to Chatwoot Cloud, what it costs, who it's genuinely built for, and where it's strong versus where it frustrates real users. We verified the facts below against Chatwoot's own site and GitHub repository in June 2026 and cite the sources.

A quick disclosure up front: Macha — the company publishing this — makes a proprietary AI agent layer that runs on top of Zendesk and Freshdesk. It does not integrate with Chatwoot, and Chatwoot isn't a competitor to it, so we have no product stake in how you read this. We'll keep it an even-handed explainer and save the one honest note about where we do (and don't) fit for the end.

How we researched this

Positioning, capabilities, and pricing come from Chatwoot's own website, docs, and GitHub repository, cross-checked against G2 for aggregate ratings and recurring user feedback. The GitHub star count and the two license files were read directly from the repo, not from search snippets. Where a number moves fast — stars, ratings, Captain credit prices — we flag it and date it. Pricing and open-source projects change quickly, so confirm current figures before you commit; our next review is scheduled for December 2026.

Chatwoot in one line: an open-source alternative to Intercom and Zendesk

Update (June 2026): Salesforce has agreed to acquire Fin (formerly Intercom) for ~$3.6 billion and plans to fold it into Salesforce's Agentforce — the deal was announced June 15, 2026 and is expected to close around Q4 of Salesforce's FY2027, worth weighing in any long-term Intercom/Fin decision.

Chatwoot describes itself, in the words of its own GitHub repository, as "open-source live-chat, email support, omni-channel desk — an alternative to Intercom, Zendesk, Salesforce Service Cloud." That framing is the fastest way to understand it. It plays in the customer engagement / shared-inbox + live-chat category dominated by expensive proprietary SaaS, and its pitch is simple: most of what those tools do, with the option to own the software and the data yourself.

What makes it stand out is community scale. Chatwoot has roughly 33.1k stars and 7.8k forks on GitHub (verified on the repo, June 2026) — by a wide margin the most-starred open-source support tool, and a strong signal of an active project with frequent releases, plenty of documentation, and a large self-hosted install base. Chatwoot says it's used by 15,000+ organizations worldwide. On G2 it carries about 4.5/5, though on a small review count (~16), so treat that rating as directional rather than statistically robust.

For the wider open-source field — osTicket, Zammad, FreeScout, GLPI and more — see our roundup of the best open-source ticketing systems, where Chatwoot sits alongside its peers. This guide goes deep on Chatwoot specifically.

Core capabilities: what Chatwoot actually does

Chatwoot is more than a chat widget. Its feature set spans the things a small-to-mid support team needs day to day:

• Omnichannel shared inbox. The heart of the product. Conversations from website live chat, email, WhatsApp, Instagram, Facebook Messenger, SMS, and API-based channels all land in one unified inbox, so an agent works every channel from a single screen instead of tab-hopping.
• Live-chat widget. An embeddable website chat widget with customizable branding, pre-chat forms, and the ability to continue conversations by email when a visitor leaves — the classic Intercom-style messenger, self-hostable.
• Captain AI. Chatwoot's built-in AI layer (more on this below) — an AI agent that answers customer questions, drafts agent replies, and surfaces knowledge gaps.
• Automations and macros. Rule-based automations route, assign, tag, and respond to conversations on triggers; macros let agents run multi-step actions in one click for repetitive workflows.
• Help center / knowledge base. A built-in portal for public help articles, which doubles as the source material Captain AI draws on to answer questions.
• CSAT surveys. Post-conversation customer-satisfaction surveys to measure how resolutions land.
• Agent collaboration. Private notes, @mentions, teams, labels, and conversation assignment — the internal-coordination plumbing that keeps a multi-agent queue from descending into chaos.

The through-line is that Chatwoot is conversation-first. It thinks in terms of ongoing customer conversations across channels, more than in terms of formal IT-style tickets with strict problem/change workflows. That shapes who it fits — and who it doesn't — which we'll get to.

Captain AI: Chatwoot's AI agent layer

Captain is Chatwoot's native AI offering, and it's built from four distinct parts rather than a single chatbot:

1. Assistant — answers customer questions automatically from your knowledge base and conversation history, and hands off to a human agent when it's unsure.
2. Co-Pilot — works alongside human agents, drafting and translating replies so agents respond faster.
3. Smart FAQs — analyzes conversations and flags gaps in your help center so you know what documentation to write next.
4. Memories — retains per-customer context across conversations so the AI isn't starting from scratch each time.

Captain is metered in credits. Paid Cloud plans include a monthly allowance — 300 credits on Startups, 500 on Business, 800 on Enterprise — and you top up beyond that at $20 per 1,000 credits, billed pay-as-you-go and non-refundable because they're usage-based (figures from chatwoot.com/pricing, June 2026; re-check before budgeting). It's a sensible, increasingly standard way to price AI, but worth modeling against your real conversation volume — heavy automation can outrun the included allowance.

Deployment: self-host or Chatwoot Cloud

This is the decision that defines the Chatwoot experience, and it splits cleanly two ways.

Self-hosted (Community Edition). The open-source core is free to license and you run it on your own infrastructure. The stack is Ruby on Rails + PostgreSQL + Redis, typically deployed via Docker. This is heavier than the PHP-on-shared-hosting open-source tools (osTicket, FreeScout) — budget a real server, not a $5 shared-hosting plan. In exchange you get full data ownership, no per-seat licensing ceiling, and complete control over customization.

Chatwoot Cloud. Chatwoot hosts, secures, scales, and patches everything for a per-agent subscription. You trade the data-ownership and zero-licensing benefits for not having to run a Rails app in production. For most teams without a spare ops engineer, this is the pragmatic option.

The honest framing — which we explore in depth in our open-source ticketing roundup — is that self-hosting is free to license, not free to run. Someone installs it, secures it, upgrades it, and backs it up. Below a handful of agents, a managed plan often costs less once you price your own time; above it, self-hosting starts to save real money.

The licensing nuance: MIT core, not MIT everything

This is the single most misunderstood thing about Chatwoot, so it's worth getting precise. The repository's main LICENSE file states the project is released under the MIT License — one of the most permissive open-source licenses there is. That applies to the community core.

But it does not apply to everything in the repo. All content under the enterprise/ directory ships under a separate, proprietary, source-available license: you can see the source, but using those enterprise features in production requires a paid Chatwoot subscription and an active agreement with Chatwoot Inc. (verified against enterprise/LICENSE, June 2026). Features that live behind this split include things like customizable dashboards, SLA management, agent capacity/scheduling, IP blocklisting, and audit logs.

The practical takeaway: "Chatwoot is open source (MIT)" is true for the core — and that core is genuinely capable — but it is not a clean, single-license open-source app where every feature is MIT. If a strictly OSI-style license across the whole product is a hard requirement for you, read both license files before you build on it.

Pricing: free self-host vs Chatwoot Cloud tiers

Self-hosting the Community Edition costs $0 in licensing (your only spend is infrastructure and your time). Chatwoot Cloud is priced per agent per month, billed annually (from chatwoot.com/pricing, June 2026):

Per agent/month, billed annually; verified on chatwoot.com/pricing, June 2026. Prices and Captain credit allowances change — confirm before budgeting.

Chatwoot flags Business ($39) as the most popular and the first "complete" tier — it's where Teams, automation rules, the Voice channel, and SLAs all arrive together. The free Hacker plan is a genuinely usable starting point for a solo founder or a tiny team (capped at 2 agents and 500 conversations/month). Note that Captain AI credits start on the paid tiers — the free plan doesn't include them.

Who Chatwoot is for

Chatwoot fits best when control and low cost matter more than zero-maintenance convenience:

• Developers and technical teams comfortable running a Dockerized Rails app, who want to customize the platform and own their data outright.
• SMBs and startups that want modern omnichannel support and live chat without per-seat SaaS fees scaling against them — the free Hacker tier and free self-host are real on-ramps.
• Privacy- and compliance-conscious teams that need customer conversation data on their own servers.
• Product-led, customer-facing teams that live in live chat and social channels rather than formal IT ticket queues.

It's a weaker fit if you need classic ITSM-style ticketing (incident/problem/change workflows, asset/CMDB management — that's GLPI or a dedicated ITSM tool), or if you have no ops capacity at all and want a tool that someone else fully runs with enterprise polish out of the box.

Strengths and limits

Strengths. The biggest open-source community in this category, which means frequent releases, deep docs, and a large pool of integrations and shared knowledge. A permissive MIT core. The strongest live-chat and social-channel story among open-source support tools. Real data ownership and no per-seat ceiling when self-hosted. A built-in AI agent (Captain) so you're not bolting one on. And a free tier plus free self-host that lower the barrier to trying it.

Limits. It's conversation-first, not built for rigid IT-style ticketing. The community/enterprise license split means some capabilities (SLA management, advanced dashboards, audit logs) sit behind the paid edition. Self-hosting carries a real operational and total-cost burden — Rails + Postgres + Redis is not shared-hosting-friendly, and patching/backups/uptime become your job. And on G2, reviewers repeatedly note the interface isn't the most beginner-friendly for brand-new agents, even as they praise the channels and AI. For a peer comparison, lightweight hosted live-chat tools like Crisp occupy the same "modern messenger" space without the self-host overhead — see our guide to the best live chat software.

An honest aside: where Macha fits (and doesn't)

Since you'll see Macha mentioned elsewhere on this site, here's the straight version: Macha is not an open-source platform, and it does not integrate with Chatwoot. Macha is a proprietary AI agent layer that sits on top of two commercial help desks — Zendesk and Freshdesk — to resolve routine tickets automatically inside your existing workflow. Chatwoot, by contrast, is the platform itself, with its own native Captain AI built in.

So these aren't competitors; they're different categories. If your plan is to own an open-source engagement platform on your own servers, Chatwoot (and the others in our roundup) is your shortlist, not Macha. If you're instead on — or considering — Zendesk or Freshdesk and the gap you're feeling is AI automation, that's the problem Macha is built for: see how the AI agent layer works on your help desk, or 7-day free trial, no credit card required. Either way, pick the tool that matches how you actually want to run support.

Frequently asked questions

What is Chatwoot? Chatwoot is an open-source customer engagement platform — an omnichannel shared inbox with a live-chat widget, help center, automations, CSAT, and a built-in AI agent (Captain). It positions itself as a self-hostable alternative to Intercom, Zendesk, and Salesforce Service Cloud, and can be run free on your own servers or on Chatwoot's paid cloud.

Is Chatwoot really open source and free? The community core is genuinely open source under the MIT license, and self-hosting it is free to license. But two caveats: features under the repo's enterprise/ directory ship under a separate proprietary license that requires a paid subscription for production use, and "free to license" isn't "free to run" — self-hosting the Rails + Postgres + Redis stack costs you infrastructure and maintenance time.

How much does Chatwoot cost? Self-hosting the Community Edition is $0 in licensing. Chatwoot Cloud is priced per agent/month (billed annually): Hacker $0 (up to 2 agents), Startups $19, Business $39 (most popular), and Enterprise $99. Paid tiers include monthly Captain AI credits (300/500/800), with top-ups at $20 per 1,000 credits. Figures verified June 2026 — re-check before budgeting.

What is Captain AI in Chatwoot? Captain is Chatwoot's built-in AI layer with four parts: an Assistant that answers customer questions and hands off to humans, a Co-Pilot that drafts and translates agent replies, Smart FAQs that flag knowledge-base gaps, and Memories that retain per-customer context. It's metered in credits included with paid plans.

What do I need to self-host Chatwoot? Chatwoot runs on Ruby on Rails with PostgreSQL and Redis, usually deployed via Docker. That means a real server rather than cheap shared hosting, plus someone to handle setup, security patches, upgrades, and backups. It's a heavier lift than PHP-based open-source help desks like osTicket or FreeScout.

Is Chatwoot good for IT ticketing? Chatwoot is conversation-first — excellent for live chat and omnichannel customer support, less suited to formal ITSM workflows (incident/problem/change management, asset/CMDB tracking). For IT service management, a tool like GLPI or a dedicated ITSM platform is a better fit.

The bottom line

Chatwoot is the most popular open-source customer engagement platform for good reason: a capable, MIT-licensed core, a modern omnichannel inbox with strong live chat, a built-in AI agent in Captain, and the freedom to self-host and own your data — backed by the largest community in the category. The honest caveats are that "open source" applies to the core and not the separately-licensed enterprise features, that self-hosting is free to license but not free to run, and that it's conversation-first rather than a classic IT ticketing tool. If you want control and low cost and have (or can rent) the ops capacity, Chatwoot is one of the strongest open-source picks of 2026. If you'd rather not run servers, its Cloud tiers — or a fully managed commercial tool — are the pragmatic middle ground.

Positioning, capabilities, licensing, and pricing verified against chatwoot.com and the chatwoot/chatwoot GitHub repository, June 2026. GitHub stars, ratings, and Captain credit prices move continually and are vendor/community-set — re-check the source pages before you decide.