Relayroom
A lightweight internal status page for small engineering teams to broadcast what's up, what's degraded and what's being worked on — without adopting an incident-management platform.
The problem
Small teams kept reaching for enterprise incident tools that assumed a dedicated on-call rotation, an SRE team and a budget line. What they actually needed was a page that told the rest of the company what was going on.
The approach
Reduced the surface area to three states — operational, degraded, down — and one update stream per service. No escalation policies, no paging integrations, no SLA tracking. Those are real needs for a different kind of team.
System diagram
Focus or hover a node for what it does.
By the numbers
Decisions I kept
- No escalation policies or on-call rotations — out of scope by design
- One update stream per service, no threads
- Plain-text history instead of a timeline visualization that needed explaining
Things I didn't build
- Paging integrations — the teams using this didn't have a formal on-call rotation
- SLA and uptime percentage tracking — that's a different product's job
- Multi-tenant support — this stayed a self-hosted, single-team tool
What changed
Adopted by a handful of small teams as an internal status page; the smaller surface area meant new teammates understood it without a walkthrough.