Alerts arrive briefed
Runbook, owning service, recent deploys, and the last three similar incidents arrive on the page automatically. context: ready before you're awake.
Incidents end 4× faster when nobody's hunting for context
Every alert arrives with its runbook, its owner, and the last time it happened. Relay turns 2am archaeology into a five-minute fix.
02:14:07 SEV-2 p99 latency breach: api-gateway
02:14:08 → runbook attached: gateway-latency.md
02:14:09 → paging @maya (primary, gateway rotation)
02:14:11 → similar: #3971 resolved in 11m; fix linked
02:19:44 ✓ rollback applied · latency recovering
✓ Resolved in 5m 37sOn call at 400+ engineering teams
NorthflankDatawireQuorumFieldsetParallax
How it works
Context finds you, not the other way around
Relay sits between your alerting and your team, and does the archaeology before the page even lands.
Wake the right person
Ownership-aware routing pages the engineer who shipped the change or owns the service, not the whole rotation. Escalation happens only when it's earned.
Postmortems write themselves
Every action, decision, and timestamp is captured as you work. When it's over, the timeline is the draft. You edit instead of excavating.
Case study: Datawire
−43%
mean time to resolution, 90 days after switching to Relay
"The first SEV-1 after we switched, the runbook and the last-time-this-happened thread were already in the channel. We fixed it before the status page even needed an update."
Elif KayaStaff SRE, Datawire
Try it on your next incident
Start free trialFree 14 days · No credit card · Works with PagerDuty, Opsgenie & Grafana