Skip to content

Entry 01First sightingOpen source

Support chat that plugs into any product. Your servers, your database.

Open source and self-hosted: live chat, tickets and a help center, with no per-seat pricing.

Entry 02Habitat under threatObserved in most help desks

Paying by the seat, and renting your own conversations

Most support tools charge for every person on the team, so adding a colleague to the inbox is a budget decision.

They also keep every conversation and article on their servers. Leaving means exporting what they let you export.

price: by the head
fig. 2

Entry 03InstallOne snippet

Building the nest

Run one command, pnpm helpwren install, deploy, and open the setup wizard. Then paste one snippet into your site: Settings → Installation writes it with your address in it, and shows a live check the moment the widget is on your site. Guest chat works at once.

<script src="https://support.example.com/widget.js"></script>
<script>
  Helpwren.init({ source: "web" });
</script>
plug: one snippetsocket: your site
fig. 3

Entry 04Growth stagesLevels 0 to 3

Start with a snippet. Grow when you want to.

Each level works on its own. Nobody needs a later one to get value from an earlier one.

  1. Level 0 · Snippet

    Install with one command and paste the snippet. Guest chat, a help center and the team's inbox.

  2. Level 1 · Identify

    One identify call and the team sees who they are talking to. Add a signed token and history follows people across devices.

  3. Level 2 · Mobile

    Add the support screen to a React Native or Expo app. Chat and help inside your app.

  4. Level 3 · Notify

    Turn on push through Expo, Firebase or a webhook, and email. People hear back.

fig. 4

Entry 05Observed in the wildCaptured from the running app

What your visitors see

A launcher in the corner opens the chat. Before writing, visitors see the articles your team put forward, and can open them right there. They can send a message or submit a ticket.

Logged-out visitors chat as guests. People you identify are recognised, and the team sees the page they wrote from.

The Helpwren widget open on a page: a greeting, buttons to send a message or submit a ticket, and suggested articles.

suggested before they ask

fig. 5
The team's inbox: views, a list of conversations and an open ticket with an internal note.
fig. 5a: the team's inbox, where the message lands
An article in the public help center, with its collection's other articles beside it.
fig. 5b: your help center, on your own address

Entry 06Field guidePlate I: behaviours

What it does

  • fig. 1: in conversation

    Live chat

    Visitors and logged-in users, with attachments, typing and online status.

    Live chat: read the docs
  • fig. 2: carrying a ticket

    Tickets

    Numbers, status, priority and an assignee, with internal notes only the team sees.

    Tickets: read the docs
  • fig. 3: well read

    Help center

    Collections, articles and search, built to rank and embeddable in your site.

    Help center: read the docs
  • fig. 4: in the pocket

    Mobile screen

    A support screen for React Native and Expo apps, with an unread badge.

    Mobile screen: read the docs
  • fig. 5: calling back

    Notifications

    Push through Expo, Firebase or a webhook. Email, and replies by email back into the chat.

    Notifications: read the docs
  • fig. 6: keeping watch

    Knows who's asking

    Identify users or verify them with a token. The team sees the page and live visitors.

    Knows who's asking: read the docs

Entry 07AnatomyFour layers, top to bottom

How it is built

Each layer uses only the one below it.

  1. 1Widget script. A launcher on your site, in a shadow root so neither side's CSS reaches the other.
  2. 2Chat page. The chat itself, served by your install and shown in a frame. Your site never runs its code.
  3. 3Client library. Sessions, conversations, messages and articles. The widget, inbox and help center are built on it.
  4. 4Your Supabase. Postgres, Realtime, Storage and Auth, with access rules on every row.

later: the library and API go public, so you can build your own interface on them

1234
fig. 7

Entry 08Home rangeSelf-hosted

It lives where you live

Helpwren runs on your own servers and your own Supabase project. The conversations, the contacts and the articles stay in your database.

  • Your address

    One install per product, at an address you choose.

  • Your database

    Everything is stored in your own Supabase project.

  • No seat pricing

    Add the whole team. There is nothing to count.

  • MIT licence

    Read it, change it, run it. The code is yours too.

nest: your own database
fig. 8

Last entryJoin the surveyOpen to everyone

Add your own sightings

Helpwren is built in the open. Install it, read how it works, or help make it better.

more sightings in the repo