About
Four people who were on call too long.
Relay is built by engineers who carried the pager at payments companies, a bank and a hospital network, and kept count of the nights.
Why Relay
The 3am screen was never designed.
Every on-call tool was designed at 2pm for a manager. The person who matters is the one who was just woken up, and nobody designed their screen. Relay started as that screen: the alert, the runbook, the chat and the status page together. Everything else grew from it.
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
The team
Six time zones, one pager.
Ana Ribeiro
Co-founder, CEO
Ran platform at two payments companies. Was on call for nine years and kept count.
Jonas Weiss
Co-founder, CTO
Built the alerting at a bank and the status page at a hospital network. Writes most of Relay.
Mei Tanaka
Design
Designs the 3am screen, which is the only screen that matters.
Samuel Okafor
Support and documentation
Answers every message himself, and writes the runbooks you start from.
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.