What it makes possible.
Product and support teams that want to host customer chat and manage conversations using their own infrastructure.
Host a support inbox and embed its chat widget in a website, connecting only the support integrations the team needs.
Inside the project.
- A customizable website widget with React and HTML integration via the separate upstream widget package.
- Assign, prioritize and close conversations, and invite teammates.
- Support email workflows and Twilio-backed SMS conversations when configured.
- Reply to customer conversations from Slack or Mattermost.
- The fork documents current Erlang, Elixir, Node and PostgreSQL targets; source manifests use Phoenix 1.8 and React 19.
- Run from source or build this fork’s Docker image; database migrations run during container startup.
Getting started.
- Documented runtime targets: Erlang/OTP 27.3, Elixir 1.18.4, Node 22 and PostgreSQL 16.
- Production requires DATABASE_URL, SECRET_KEY_BASE and BACKEND_URL.
- Email, Twilio, Slack, S3 and other integrations need their own configuration when used.
- Clone the fork, install Mix and frontend dependencies, and run mix ecto.setup.
- Start the Phoenix backend and Vite frontend for local development.
- Alternatively set a real SECRET_KEY_BASE and run docker compose up --build to build the fork locally.
Before you use it.
- The embedded chat widget, chat builder and session-replay package remain separate upstream projects; the README describes them as unmaintained upstream.
- Papercups75 is a self-hosted fork; the linked upstream demo belongs to the original Papercups project.
- Self-hosting requires operating a PostgreSQL database and configuring the chosen integrations.
Project sources.
Based on public project documentation and source, checked 7 September 2026. Refer to the repository for changes since then.