Current direction
The project is focused on making self-hosted incident response easier to run without hiding important operational details. The near-term direction is improving alert context, routing clarity, responder workflows and integration coverage.
Product areas
| Area | Direction |
|---|---|
| Alert routing | More predictable matcher behavior, better explainability and clearer route/service ownership. |
| Incident workflow | Responder requests, stakeholder visibility, comments, priorities and notification center improvements. |
| Scheduling | Better rotation visibility, calendar integrations, overrides and timezone handling. |
| Integrations | More monitoring sources and richer notification channel behavior. |
| Operations | Deployment docs, schema checks, logging, troubleshooting and safer upgrades. |
How to follow progress
The changelog is the best public summary of shipped features between tags. The GitHub repository shows the actual implementation work, open discussions and code history.
Release expectations
IncidentRelay evolves through regular tagged releases. Teams deploying it should test their exact alert sources, notification paths, escalation timing and backup plan before relying on it for critical production coverage.