Skip to content

In-app notifications

The bell your users open.
Not the cluster you run.

A real-time inbox in your product with one tag. Templates, topics, scheduled sends, action buttons and analytics — all from one dashboard, and nothing for you to operate.

Read the docs

No card. Up to 1,000 active subscribers on the trial.

your page
<script src="https://notifybell.altixcode.com/embed/notify-bell.js" defer></script>

<notify-bell app-id="app_…" token="…"
  api-url="https://notifybell.altixcode.com"></notify-bell>

From one call to a bell that rings.

  1. 01

    Your backend publishes

    One call — to a person, a topic, or everyone. With a template and its variables, or the words themselves; now, or at a time you pick.

  2. 02

    Every open bell rings

    Server-Sent Events push it to every tab that has the bell open. Anyone offline finds it waiting, in order.

  3. 03

    People read and act

    Buttons that approve or open something, tabs for unread and archived, a settings panel where required categories stay on.

  4. 04

    You see what worked

    Seen, read and clicked, per day and per category, in the dashboard and as CSV. Retract anything that went out wrong.

your backend202 · 200
await fetch('https://notifybell.altixcode.com/api/v1/apps/APP_ID/broadcasts', {  method: 'POST',  headers: { Authorization: `Bearer ${API_KEY}` },  body: JSON.stringify({    topic: 'project:apollo',    template: 'release',    variables: { version: '2.4' },  }),})
3
NotificationsMark all read

Apollo 2.4 is out

Release notes for everyone on project:apollo

See what changed

Ada mentioned you

in “Q4 launch plan”

Your export is ready

invoices-2026-10.csv

Sent

3

Seen

3

Clicked

1

Illustration drawn from the real bell and dashboard; the numbers are this scene’s own.

Everything the bell needs. Nothing it does not.

Each of these is in the product today, in the API and in the dashboard.

  • 01

    Real-time inbox

    A bell, a badge and an inbox in a shadow-DOM custom element. Delivered live over Server-Sent Events, under 8 KB gzipped.

  • 02

    Templates

    Copy with {{ variables }} kept in the dashboard and published by key. Changing the words needs no deploy.

  • 03

    Topics

    Put subscribers on project:42 or team:design and reach all of them with one call.

  • 04

    Scheduled sends

    Pick a time up to 90 days out. Cancel it before it goes, or retract it after.

  • 05

    Action buttons

    Up to two buttons per notification. The host page can route them in-app instead of opening a tab.

  • 06

    Update and retract

    Rewrite a notification that already went out, or take it back from every inbox, live.

  • 07

    Preferences that hold

    Per-category opt-outs enforced at publish time, opt-in categories, and required ones nobody can switch off.

  • 08

    Your look, no deploy

    Accent, badge, corners, light or dark, toasts — set in the dashboard, picked up by every bell.

  • 09

    Engagement analytics

    Seen, read and clicked rates by day and category, the most-sent titles, and CSV export.

  • 10

    Signed webhooks

    Created, read, clicked, archived, retracted and erased events, HMAC-signed, retried for 12 hours.

  • 11

    Six languages

    The dashboard, the docs and the bell’s own words in English, German, French, Spanish, Italian and Russian.

  • 12

    Built to be trusted

    Short-lived subscriber tokens, row-level security in Postgres, two-factor sign-in and an audit log.

What you will not be running.

Most notification platforms sell email, SMS, push and chat together, and ask you to run their stack to get any one of them. NotifyBell is the in-app inbox only — one container and Postgres behind it.

If you need email and SMS routing too, you want a different product, and we would rather say so here than after you have integrated.

  • Kafka or a message brokernot here
  • MongoDBnot here
  • A workflow enginenot here
  • Email, SMS and push routingnot here
  • A separate realtime servicenot here

Decisions we made so you do not have to.

Nothing is missed while offline

The inbox is read from PostgreSQL, not replayed from a channel. Someone whose laptop was shut still sees what arrived, in order, when they open it.

An opt-out is never delivered

Preferences are enforced when publishing, not filtered in the browser. A notification somebody muted does not exist, rather than existing and being hidden.

Your key never reaches a browser

Your backend mints a short-lived token naming one user. The embed can read that person’s inbox and nothing else — it cannot publish, and it cannot see anyone else.

Priced by the people who actually saw something.

Monthly active subscribers, not rows in a table. A user who churned two years ago is not on your invoice.

Pro

A product with a real user base.

$39/ month

50,000 active subscribers

Scale

A platform, or several products at once.

$99/ month

250,000 active subscribers

Full comparison on the pricing page.