At a glance — how these 4 alternatives compare
Our read on each project's adoption, maintenance activity and commercial-use risk, derived from GitHub signals and SPDX license terms rather than star count alone. Sorted by stars. How we score.
| Project | Adoption | Maintenance | Commercial use |
|---|---|---|---|
| ★ 32,996 · Ruby | Flagship | Active | Unknown risk No clear SPDX id — treat as all-rights-reserved until verified |
| ★ 6,067 · Elixir | Mainstream | Stale | Low risk Embed in a proprietary product with no copyleft obligation |
| ★ 5,694 · Ruby | Mainstream | Active | High risk Even a hosted/modified deployment can trigger source release |
| ★ 4,005 · TypeScript | Established | Active | Unknown risk No clear SPDX id — treat as all-rights-reserved until verified |
The alternatives
chatwoot
Open-source live-chat, email support, omni-channel desk. An alternative to Intercom, Zendesk, Salesforce Service Cloud etc. 🔥💬
chatwoot/chatwoot Updated 2026-06-20 papercups
Open-source live customer chat
papercups-io/papercups Updated 2024-02-15 zammad
Zammad is a web based open source helpdesk/customer support system.
zammad/zammad Updated 2026-06-19 erxes
Experience Operating System (XOS) that unifies marketing, sales, operations, and support — run your core business seamlessly while replacing HubSpot, Zendesk, Linear, Wix and more.
erxes/erxes Updated 2026-06-21 Editor's take
Yusuke Morinaga · last revisited
Intercom is a support tool wearing a marketing tool's clothes — and the OSS world only rebuilt the support half.
Intercom is sold as one product but it does two jobs: reactive support (a shared inbox, live chat, a help center) and proactive lifecycle messaging (product tours, behaviour-triggered in-app messages, onboarding nudges). The open-source projects below have, almost without exception, rebuilt the support half and left the marketing half alone. So before you pick one, be honest about which half of your Intercom bill you were actually using — because if it was the product tours, none of these will satisfy you.
Chatwoot — the only mature, no-asterisk recommendation here
Chatwoot (29.6k stars, Ruby, pushed 2026-05-21) is the clear leader and the
one I would deploy. Live chat widget, email support, social channels, a
proper agent inbox — it covers the reactive-support core of Intercom
genuinely well, and it is actively developed (a commit the day I checked).
The one thing to verify yourself is the license: the GitHub card shows
NOASSERTION because Chatwoot relicensed and carves out enterprise features,
so the community edition’s terms are not the simple permissive story the
others might suggest. Read the current LICENSE before building a commercial
product on top of it; for running it as your own support desk, it is fine.
Zammad — pick this if “support” really meant “ticketing”
Zammad (5.6k stars, Ruby, AGPL-3.0) is a different shape: it is a help-desk / ticketing system first, with email, phone, and chat folded into a ticket model, rather than a chat-first tool with tickets bolted on. If your Intercom usage was mostly the inbox and SLAs and less about the live-chat bubble, Zammad will feel more native. AGPL-3.0, which for self-hosting your own support desk does not trigger any obligations.
Two entries I would not lead with, and why
Papercups (6k stars, Elixir, MIT) shows a healthy star count, but its last commit on the card is 2024-02-15 — over two years stale at the time of this review. That is the single most important fact about it: a customer- facing chat tool that has not shipped in two years is a maintenance risk you are signing up to own or fork. MIT-licensed and pleasant, but I would not put it in front of customers today without accepting that you may be the maintainer now. erxes (4k stars, TypeScript, NOASSERTION) is the opposite problem — it is more than Intercom, an entire “experience operating system” spanning marketing, sales, and support. If you want a sprawling all-in-one platform that is fine, but as a focused Intercom replacement it is a heavier, broader thing than most teams leaving Intercom actually want.
The honest gap nobody fills
The part of Intercom you cannot get back from any of these is the proactive layer: product tours, behaviourally-triggered in-app messages, and especially Fin, the AI agent that resolves tickets from your help center. Chatwoot has added bot and automation pieces, but “rebuild my onboarding tour flow” is not something any project here does out of the box. If that workflow was central, either keep a dedicated product-adoption tool alongside your OSS support desk, or accept that you are giving up the onboarding automation when you leave.
Comparison notes
Chatwoot is the most mature OSS alternative with live chat, email support, Twitter/Facebook channels, and an agent inbox — self-hostable with a Rails backend. Zammad covers the helpdesk ticketing use case for support-focused teams. The main gaps: Intercom's product tour and in-app messaging for user onboarding (not just support) have no OSS equivalent. Intercom's AI chatbot (Fin) that resolves tickets from your help center has no mature OSS equivalent. Chatwoot covers support messaging well but lacks Intercom's marketing and lifecycle communication features.
Migration tips
- Export Intercom conversations via the Data Export tool — download conversation transcripts as JSON
- Export contact data (users, companies) via Intercom's CSV export or API for import into Chatwoot or your CRM
- Migrate your Intercom help articles to your OSS help center or wiki before pointing users to the new URLs
- Update your website's chat widget code from Intercom's snippet to Chatwoot's widget embed
- Notify active conversations of the support channel change — in-flight conversations should be resolved before migration
Which alternative should you pick?
We don't believe in a single "best" answer here — the right project depends on your license constraints, team size, and tolerance for early-stage tooling. The 4 projects above each have a distinct profile. Use this decision tree:
- You want the most active community and the lowest risk of abandonment → chatwoot. 32,996★ — the largest user base in this list, which usually means more StackOverflow answers, more plugins, and more deployment runbooks online.
- You ship commercial software and need to ship modified code without releasing source → papercups. MIT licensed — modify and embed without copyleft obligations.
- You want a strong-copyleft project that resists vendor capture → zammad. AGPL-3.0 licensed — downstream forks must stay open, which is what some teams explicitly want.
- You need a project that has shipped a release in the last few weeks → erxes. Last commit 2026-06-21 — the freshest activity in this list.
License & commercial-use notes
For an open-source replacement the license often matters more than any single feature — it decides whether you can modify the project, embed it in a product, or offer it as a hosted service. Here is how the 4 projects on this page break down:
- Permissive (papercups) — MIT / Apache / BSD / ISC — modify and embed inside a commercial product with no copyleft obligation. The safest bucket for shipping in a proprietary codebase.
- Network copyleft (zammad) — AGPL / SSPL — the copyleft trigger extends to offering the software over a network, so a hosted deployment of a modified version can oblige you to publish your changes. Read the exact terms before building a paid hosted product on these.
- Unverified license (chatwoot, erxes) — GitHub returned no clear SPDX id. Treat as all-rights-reserved until you read the project's LICENSE file directly — do not assume commercial use is permitted.
License fields come from the GitHub API's SPDX classification and can lag a relicense. The repository linked on each card is authoritative — confirm its LICENSE file before any license-sensitive deployment.
Maintenance health of these 4 projects
Of the 4 projects listed, 3 shipped at least one commit in the last 12 months. See how we rank for the full criteria and our self-hosting cost reality check, which apply across every comparison on this site.
Frequently asked questions
How do these 4 alternatives compare on maintenance health?
3 of 4 have shipped a commit in the last 12 months. At least one project here has 5,000+ GitHub stars, which usually correlates with sustained maintainership. Always check the last-pushed date in the cards above and read the latest 5 closed issues — those two signals together catch 80% of abandoned-project cases.
How this page was compiled
- Repository facts (stars, license, language, last commit) come straight from the GitHub public API and are linked on each card as the primary source.
- Editorial analysis is drafted from Intercom's use case and the alternatives' repository metadata, then reviewed by hand.
- Maintenance signal: 3 of 4 projects shipped a commit in the last 12 months as of the latest rebuild (most recent activity: ).
- Last editorial review: by Yusuke Morinaga.
- Spotted an error? Email [email protected] with the page URL (subject prefix
[correction]) — we ship corrections within 14 days.