Features · Alerting & Incidents · In-App Notifications
Alerting & Incidents · In-App Notifications

A bell, an archive,
and inline action buttons.

Not every alert needs a Slack message. The in-app bell catches the lower-severity stuff, archives it, and lets you ack / resolve / snooze without leaving the platform. Per-event opt-out.

bell · unread 4
agent updated web-prod-05 · v1.0.74
cert renewed acme.io · 90d
backup finished 333 MiB · 4m54s
anomaly cleared db-prod-01 cpu
archive kept 90 days
— Why this matters

Not everything deserves a Slack message.

01

Low severity still needs somewhere to go.

A certificate renewed, an agent updated, an anomaly that cleared itself. Worth knowing, not worth interrupting for.

02

A re-firing alert should not multiply.

Notifications are deduplicated on their source, so one flapping alert stays one item in the bell.

— What's included

How the bell behaves.

Unread count
Capped at 9+, because the exact number stops mattering after that.
Severity colours
Critical, warning, info and ok, matching the palette used everywhere else.
Click to read and go
Marks read and navigates to the thing it is about.
Mark all read
In the dropdown header, for the morning after.
Full archive
At /notifications, filterable by read state, severity and type.
Polls every 30 seconds
Pausing when the tab is hidden and resuming on focus, so a background tab is not a background job.
Broadcast or personal
Tenant-wide notices are marked read per user, not for everyone at once.
— Works with

Connected capabilities

— FAQ

Questions, answered honestly.

Does the bell consume mobile push? +
Only if you opt in. By default the bell is in-app only; push is for explicit external channels.
Can I bulk-archive? +
Yes — filter the bell, select-all, archive.
Is it shared across the team? +
No — per user. For shared visibility use a Slack channel.

A quieter inbox for the alerts that don't need a page.

In-app notifications on every plan.

Get early access Back to Alerting & Incidents