Chatwoot vs Papercups

The one question that decides this

Are you replacing Intercom because you need a broader support desk, or because you mainly need open-source customer chat? Chatwoot is explicitly positioned as an “Open-source live-chat, email support, omni-channel desk” and lists both Intercom and Zendesk among the products it replaces. Papercups is narrower by its own description: “Open source live chat alternative to Intercom, Zendesk, Drift.” That is the real dividing line here. Chatwoot aims at a wider support operation; Papercups aims more directly at the live-chat-shaped part of Intercom.

What each one is actually trying to be

Chatwoot: a broader open-source support desk

Chatwoot’s own tagline is “Open-source live-chat, email support, omni-channel desk.” That is a fairly unembarrassed attempt to occupy the space left by several established support products, not just the chat widget attached to one. Its GitHub description is even more explicit: “Open-source live-chat, email support, omni-channel desk. An alternative to Intercom, Zendesk, Salesforce Service Cloud etc. 🔥💬”

The important word is “desk.” Chatwoot is presenting itself as a place for customer support work across live chat, email, and multiple channels, rather than as a single-purpose messaging layer. The supplied replaces data backs that up: it names both Intercom and Zendesk. That gives Chatwoot the broader brief in this comparison, at least on paper.

There is also a difference in how much ambition the positioning reveals. “Omni-channel desk” is product-suite language; it implies a support team with more than one queue or communication channel. That does not prove every workflow is equally good, and GitHub descriptions are not product audits. It does mean Chatwoot is the more natural candidate when “replace Intercom” really means “replace the customer-support system around Intercom.”

Papercups: a focused open-source chat alternative

Papercups describes itself as “Open source live chat alternative to Intercom, Zendesk, Drift.” Its GitHub description is shorter still: “Open-source live customer chat.” The pitch is easy to understand and notably less expansive than Chatwoot’s. Papercups is making live customer chat the center of gravity.

That narrower framing can be a feature rather than a weakness. If the thing you want to get out of Intercom is primarily its chat presence, Papercups has a clean conceptual target. The project lists only Intercom in its replaces data, while its tagline also names Zendesk and Drift, so the available data consistently points toward chat-first positioning rather than a full support-desk replacement.

The tradeoff is scope. Papercups does not describe itself as an email-support or omni-channel desk product in the supplied material. That does not tell us what the application can or cannot do in practice, but it does tell us what the project is choosing to foreground. For teams that want a broad support platform, that distinction matters before anyone starts arguing about dashboards or deployment commands.

Head-to-head: the metrics

Chatwoot has 37,436 GitHub stars, 9,101 forks, 1,530 open issues, a last push date of 2026-10-02, and a reported license of NOASSERTION. Papercups has 6,114 stars, 580 forks, 179 open issues, a last push date of 2024-02-15, and an MIT license. On the visible GitHub signals supplied here, Chatwoot has the larger footprint and the more recent last-push date; Papercups has the clearer reported license label.

Those numbers are not a scorecard. Stars and forks indicate attention and reuse signals, but they do not establish product quality, support responsiveness, or whether a project fits your team. Open issues are similarly ambiguous: 1,530 can mean a busy project with lots of users reporting problems, while 179 can mean a smaller project with fewer reports, a quieter issue tracker, or less activity. The counts tell us about the shape of the public repository, not whether your specific support workflow will be pleasant.

The license field deserves a more serious pause than the star gap. Papercups is reported as MIT, which is a recognizable permissive open-source license. Chatwoot is reported as NOASSERTION, so the provided data does not let us confidently state a license for it. That is not a verdict on Chatwoot’s legal status, but it is a reason to verify the repository’s current licensing terms before building a business process around it. “Open source” in a project description is not a substitute for checking the actual license.

Freshness is the other uncomfortable signal. Papercups’ last push date is 2024-02-15, while Chatwoot’s is 2026-10-02 in the supplied GitHub data. That is a substantial difference in visible repository activity. It does not prove Papercups is unusable or abandoned, and it does not prove Chatwoot’s latest activity is relevant to your needs. It does mean Chatwoot currently presents the safer bet for a team that values ongoing repository motion, while Papercups asks you to investigate maintenance and roadmap risk more carefully.

Self-hosting

Chatwoot lists both self-host and official-cloud as hosting options, with a deploy difficulty of 3 out of 5. That is a middle-of-the-road deployment rating in the supplied data: not presented as effortless, but not treated as an especially punishing infrastructure project either. The official cloud option also means teams can evaluate Chatwoot without making self-hosting the first decision. For organizations that want control now and a hosted fallback later, that combination fits the broader support-platform pitch.

Papercups also lists both self-host and official-cloud, and it likewise has a deploy difficulty of 3 out of 5. So deployment does not produce a meaningful winner between them based on the supplied data. Both offer the same hosting shape and the same stated difficulty. The difference is what you are deploying: Chatwoot’s stated target is a live-chat, email-support, omni-channel desk, while Papercups keeps its stated target at open-source live customer chat.

Community signals

The Hacker News history shows both projects received an initial burst of attention. Chatwoot’s top listed story is “Launch HN: Chatwoot (YC W21) – Open-Source Alternative to Intercom, Zendesk,” with 396 points and 110 comments, posted on 2021-03-18. Papercups’ top listed story is “Launch HN: Papercups (YC S20) – Open-Core Intercom Alternative,” with 285 points and 85 comments, posted on 2020-08-12. Those are useful signals that both projects got real launch-era visibility, but they are old launch stories rather than current user sentiment.

The recent Hacker News field is quieter: Chatwoot has 1 mention in the last 90 days, while Papercups has 0. That is not enough activity to support a “the community says” conclusion. It is simply a reminder that launch attention and current discussion are different things.

The supplied Reddit records are even less useful for comparing these products. The Chatwoot record is a post titled “Libredesk an open-source Zendesk / Intercom / Chatwoot alternative” in r/selfhosted, with 94 upvotes and 18 comments; it is about another project, even though Chatwoot appears in the title. The Papercups record is a post titled “This Coffee Shop charges Service Fee for a takeout! 😳” in r/CoffeePH, with 80 upvotes and 77 comments, which is unrelated to Papercups. Neither record supports a product quote or a meaningful community verdict, so pretending otherwise would be exactly the sort of slop this comparison should avoid.

What we'd do

Chatwoot wins for teams that mean “replace Intercom” as shorthand for adopting a broader support desk with live chat, email support, and multiple channels, especially when repository activity and a larger public footprint matter. Papercups wins for teams that want a more focused open-source live-chat alternative and prefer the clarity of an MIT license, provided they are comfortable investigating the older last-push signal before committing. For most customer-support teams, we would start with Chatwoot; for a narrowly scoped chat deployment, Papercups remains the more direct fit.