RelayOpsOperations overview
Active incidents, service health and the next action.
Self-hosted incident operations
One incident. One shared picture.
Keep services, incoming signals and response decisions together. A durable timeline gives the next responder the context to continue.
Open local RelayOps- Service
- Signal
- Incident
- Timeline
SERVICE → SIGNAL → INCIDENT → TIMELINE
Built for the response
Incident workbench
Server-side filters, shareable URLs and saved views.
Response board
Permission-checked transitions with keyboard and menu alternatives.
Incident room
Durable updates, participants, signals and conflict-aware commands.
Service catalog
Service ownership, runbooks and reversible archiving.
Reliability insights
MTTA, MTTR, explicit samples and links back to the incidents.
PostgreSQL is the record. Realtime keeps the team current.
A single instance runs without Redis. Existing Kaneo data remains in an explicit read-only archive; incidents are a separate domain.
React · Hono · PostgreSQL · WebSocket