We stopped waking up the whole team.
Before Relay every alert went to a channel and whoever was awake took it. Now one person is paged, with the runbook. Our on-call survey went from dread to fine.
Relay, incident response
Fix incidents before customers notice.
Relay pages the right engineer, opens the runbook and updates your status page, in the first ninety seconds. Built for teams without an on-call department.
Built for
Payments teams · Platform teams · Two-person startups · Agencies on call
Open source maintainers · Hospitals' IT · Game studios · Fintech
Why Relay
Three promises, measured on every incident.
Built forthe 3am page.
The alert, the runbook, the chat and the status page on one screen, so the person who was just woken up does not have to find anything.
See how it worksAlerts that find a person
One page to the engineer who owns the service, escalating every five minutes until someone answers.
Relay reads your service map and pages the owner, not a rota. If they do not acknowledge in five minutes it moves up the chain, then to everyone. Pages arrive by push, call and text; the call reads the alert aloud.
Runbooks that open themselves
The fix for this alert, on the screen that shows the alert, with last time's notes.
Every alert carries its runbook: the steps, the dashboards, the people to call, and what the last three engineers did when it fired. Runbooks are Markdown in your repository, so they are reviewed like code.
A status page customers trust
Updated from the incident, in your words, before the first support ticket.
Your status page is written from inside the incident, in a template your team agreed on in advance. Subscribers get the first update within ninety seconds and the all-clear with the cause, not a shrug.
Postmortems in a day, not a month
The timeline writes itself from the chat, the pages and the deploys.
Relay keeps the timeline as the incident happens: every page, every message, every deploy and rollback, with the clock. The postmortem starts with the facts filled in, so the meeting is about what to change.
Changelog
Something ships every two weeks.
0.9.0, 2026-10-02
Status page subscribers by email and RSS
Customers can subscribe to a status page and get the first update within ninety seconds of an incident opening. RSS for the people who prefer it.
0.8.2, 2026-09-18
Phone calls read the alert aloud
A page by call now reads the alert's title and the service name, so you know what it is before you find your glasses.
0.8.0, 2026-09-04
Deploys and rollbacks on the timeline
GitHub and GitLab deploys appear on the incident timeline with the commit, so the postmortem shows what changed and when.
0.7.1, 2026-08-21
Runbooks show last time's notes
When an alert fires, its runbook opens with what the last three engineers did and how long it took.
Beta teams
What they say after a quarter.
Priya Natarajan, CTO, Tally, Beta customer since May 2026 The status page is finally honest.
We used to update it after the fact. Now it is written from inside the incident and customers see it before they notice anything. Support tickets during incidents fell by half.
Marcus Oyelaran, head of platform, Ferry, Beta customer since June 2026 Postmortems take an hour.
The timeline is already there, with the clock. We argue about what to change instead of what happened.
Lena Hartmann, engineering manager, Grove, Beta customer since July 2026
Relay in numbers
- 90s
Alert to a human, median
- 38%
Fewer repeat incidents, first quarter
- 1200+
Teams on the waitlist
- 12
Integrations, with a webhook for the rest
Pricing
Free for five. Fair after that.
One price per person on call, nothing per alert. Beta teams pay nothing until general availability.