Reaches the right people, where they already are.
One incident, routed to every channel your team uses: chat, on-call, webhooks, feeds. No per-message surprises.
An incident the right people never see is the same as no incident. Status tools that only send email, or that lock on-call integrations behind enterprise tiers, leave teams wiring brittle forwarding rules, and the SRE who needs the alert is the last to know something broke.
One status change routes everywhere your team works. Chat tools get a native message. On-call tools get a single alert that follows the incident from create to resolve, not three separate pages. Your own systems get a signed webhook or a feed.
Subscribers choose their channels, the services they care about, and the severity that’s worth interrupting them. On-call integrations route per page or per org. Every channel here is included, with no per-message billing.
Where the team already talks.
An incident lands in the channel people are already watching, formatted natively for each platform.
- Slack
- Posts incident updates to a channel, formatted with Block Kit. Paste a Slack incoming-webhook URL on a page or as an org integration.
- Telegram
- Delivers to a Telegram chat or group the Observer bot has joined. Connect through the bot deep-link and confirm the chat once.
- Discord
- Posts to a Discord channel as a rich embed. Paste a Discord channel webhook URL.
- Microsoft Teams
- Posts an Adaptive Card to a Teams channel. Paste an incoming-webhook URL from the Teams connector.
The pager, correlated.
Create, update, and resolve correlate to a single alert via a stable dedup key, not three separate pages.
- PagerDuty
- Triggers and resolves a PagerDuty incident via the Events API v2. Add a routing key per page or per org.
- Splunk On-Call
- Raises and resolves alerts through the Splunk On-Call REST endpoint. Add your Splunk On-Call routing URL.
- Grafana IRM
- Sends create and resolve into Grafana IRM (OnCall). Paste the Grafana IRM webhook integration URL.
For everything you build yourself.
Signed webhooks for your own pipelines, a pull feed for readers, and a ticket for the work that follows.
- Signed webhook
- POSTs a JSON event to your endpoint, signed so you can verify it. Add a URL; check the signature against your shared secret.
- RSS / Atom feed
- A per-page feed of published incidents and maintenance. Pull, not push. Point any reader at the page's Atom feed. Nothing to configure server-side.
- Jira
- Opens and transitions a Jira issue as the incident lifecycle moves. Connect a Jira project and map create / resolve to issue transitions.
From one event to every inbox.
The dispatch layer is transport-agnostic. It resolves who and where, then hands each channel the event to render in its own format.
- 01
A signal crosses the line
A metric breaches its threshold, or an operator posts an incident by hand. Either way, an event is emitted.
- 02
Observer scopes it
The dispatch layer resolves the affected services and the severity from the event.
- 03
Recipients are looked up
Who should hear about this, and on which channels: subscribers by service and severity, on-call integrations per page or org.
- 04
Each channel delivers natively
Slack as Block Kit, PagerDuty through the Events API, a Teams Adaptive Card. The same event, rendered for its destination.
- 05
Updates correlate to one alert
Follow-ups and the resolve land on the same on-call alert through a stable dedup key, so the pager tells one story.
- 06
Subscribers stay in control
Channels, services, and severity are managed from a preferences page. People tune their own signal.
What it looks like on the day.
Two moments where routing to the right channel is the difference between a handled incident and a surprise.
API p99 breaches its SLO the incident auto-drafts, on-call publishes, and within seconds PagerDuty triggers, #incidents posts in Slack, and status-page subscribers get email.
A maintenance window is scheduled subscribers are notified in advance on the channels they chose, and the status pill reads Maintenance, not Outage.
The channels here are free to use.
Webhook- and API-based delivery has no per-message cost, so it’s included in every plan.
Every channel on this page is included, with no per-message fees, because each one rides a webhook or an API you already pay nothing to call. SMS and WhatsApp carry a real per-message cost; they’re on the roadmap and will be priced separately when they land.