Papercups

What Papercups actually is

Papercups is an open-source live customer chat tool positioned as an alternative to Intercom, Zendesk, and Drift. The pitch is straightforward: run customer conversations through software you can inspect, modify, and self-host instead of renting another opaque support widget. In this comparison, Papercups primarily stands in for Intercom, especially for teams that want live chat without immediately committing every customer-support workflow to a large commercial platform. It is not trying to be a generic “business communication platform” in the abstract. It is live chat, with the open-source label doing a meaningful amount of the differentiation.

Live GitHub stats

Papercups has 6,101 stars and 577 forks on GitHub. Those are substantial numbers for an open-source customer-chat project and suggest that the repository has had real visibility beyond a weekend demo. They are signals of interest, though, not proof that the software is currently thriving or that the project will fit your production requirements.

The project is licensed under MIT, which is one of the least restrictive choices an open-source project can make. That gives teams room to run, modify, and integrate Papercups without the licensing obligations associated with copyleft licenses. The primary language is Elixir, so expect the codebase and deployment story to make more sense to teams already comfortable in that ecosystem than to teams whose operational muscle is entirely centered on JavaScript or Python.

The repository’s last push was 2024-02-15. GitHub currently shows 179 open issues. That combination deserves a clear reading: Papercups has a meaningful public footprint, but the latest recorded push is not recent enough to treat active maintenance as a given. The issue count is not automatically a condemnation; open-source projects accumulate stale issues all the time. It does mean you should inspect recent issue activity, test the version you plan to deploy, and decide whether your team can own the consequences if upstream support is slow.

What it's good at

Papercups has a focused proposition, which is useful in a category full of products that keep adding “engagement,” “automation,” and “AI” until the original chat problem is buried under a settings menu. Its GitHub description is simply “Open-source live customer chat”, and the tagline calls it an “Open source live chat alternative to Intercom, Zendesk, Drift.” That clarity is a feature in itself. If your requirement is customer chat and your objection is handing the entire workflow to a proprietary SaaS vendor, Papercups is aimed in the right direction.

The open-source model also makes Papercups more interesting than a basic price comparison. Intercom’s cheapest listed tier starts at $29 per seat per month, with pricing based on full seats and additional usage or add-ons potentially increasing the bill. Papercups gives you another axis to evaluate: whether you would rather pay a vendor for convenience or spend engineering and operations time controlling the system yourself. Self-hosting is not free, but it can be the more defensible choice when data control, customization, or vendor independence matter more than having every feature polished and bundled.

The MIT license is another practical advantage for teams that expect to adapt the product or embed it into a broader internal stack. That does not magically turn Papercups into a drop-in Intercom replacement. It does mean the project is legally straightforward to evaluate, and the repository is available for the kind of inspection that SaaS products generally do not permit. For a small team with a narrow live-chat requirement, that can be more valuable than a sprawling commercial feature set nobody asked for.

What to watch for

The main concern is maintenance, not licensing. MIT is permissive, but the 2024-02-15 last push and 179 open issues mean you should not assume that Papercups is receiving steady upstream development. A deploy difficulty rating of 3 out of 5 is the right kind of warning: this is not necessarily an infrastructure research project, but it is also not the same as signing up for Intercom and pasting in a snippet. Elixir familiarity, operational ownership, upgrades, backups, and troubleshooting all become your problem when you self-host. The official-cloud option may reduce that burden, but it does not erase the need to verify current availability, support expectations, and feature parity before moving customer conversations over.

You should also resist evaluating it on stars alone. 6,101 stars is a useful signal that people have cared about the project, while 577 forks indicate that others have copied or adapted it. Neither number tells you whether the current release is reliable for your traffic, whether unresolved issues affect your deployment, or whether the project’s commercial side is still being actively operated. Read the repository as a product with an uncertain maintenance profile, not as a museum piece with a reassuring star counter.

How to deploy

Papercups supports both self-hosting and an official-cloud option. For self-hosting, Docker or Docker Compose is the practical path commonly associated with deploying an Elixir application alongside its supporting services, but you should follow the project’s current instructions rather than relying on a compose file found in an old blog post. For the deployment walkthrough and the details that matter around configuration, use the Papercups deployment guide. The official-cloud route is the simpler operational choice if you want to test the product without taking on the full maintenance burden first.

Related tools

Papercups belongs in the broader set of open-source alternatives to Intercom. For other projects that target the same replacement category, browse the Intercom alternatives page. Compare maintenance activity, deployment requirements, licensing, and actual product scope rather than treating “open-source Intercom alternative” as a guarantee that two tools are interchangeable.