- Home
- On-Call Scheduling Software
- IncidentRelay
IncidentRelay
What it is
IncidentRelay is open-source, self-hosted software for on-call management and incident response, aimed at SRE and DevOps teams. It routes alerts by source, labels, severity, and team ownership, then applies escalation policies and team rules. Teams can manage schedules, shifts, rotations, overrides, and escalation chains; responders can acknowledge, resolve, silence, or escalate alerts. Versioned event orchestration rules can enrich, group, route, suppress, and automate events, with execution history for reviewing matches and results. Integrations include alert sources such as Alertmanager, AWS SNS and CloudWatch, Grafana, Datadog, Azure Monitor, Sentry, and webhooks. Notifications can go through Slack, Mattermost, Telegram, email, Microsoft Teams, voice calls, and browser/PWA push. The software also provides Swagger UI and OpenAPI JSON, tokens for incoming routes and user-scoped automation, and roles including viewer, editor, responder, and manager. Deployment options include Docker Compose, Kubernetes with Helm, RPM packages, and manual systemd installation. Schedules can be exported through read-only CalDAV calendars and tokenized ICS feeds. Its listed plan is free and self-hosted.
For and against
For
- Open-source and self-hosted.
- Supports schedules, rotations, overrides, and escalation chains.
- Event rules include execution history.
- Offers several deployment options.
- Schedules can be exported as CalDAV or ICS.
Against
- Production installations run separate web/API and scheduler processes.
- Self-hosting requires choosing and maintaining a deployment path.
The verdict
IncidentRelay combines alert routing, responder actions, scheduling, and event automation in a self-hosted package. Teams should account for deployment and production process requirements when considering it.
Who it suits
IncidentRelay is for SRE and DevOps teams that want self-hosted on-call and incident workflows. Its routing, escalation, integrations, and schedule exports suit teams coordinating alert response.
Plans and prices
IncidentRelay
Open-source · Self-hosted
Read 4 Oct 2026 · incidentrelay.io
On the record
- Access controls
- The documentation describes group and team roles, including viewer, editor, user_admin, responder and manager.incidentrelay.io · read 4 Oct 2026
- Alert integrations
- Available 1.x incoming integrations include Alertmanager, AWS SNS and CloudWatch, Grafana, Datadog, Zabbix, Sentry, LibreNMS, RMON, generic webhooks, PagerDuty Events API v2 and heartbeats.incidentrelay.io · read 4 Oct 2026
- Alert routing
- It routes incoming alerts by source, labels, severity and team ownership, then applies escalation policies and team rules.incidentrelay.io · read 4 Oct 2026
- Automation API
- IncidentRelay provides Swagger UI and OpenAPI JSON, with route intake tokens for incoming integrations and personal API tokens for user-scoped automation.incidentrelay.io · read 4 Oct 2026
- Calendar exports
- On-call schedules can be exported through read-only CalDAV calendars and tokenized ICS feeds.incidentrelay.io · read 4 Oct 2026
- Deployment options
- The documentation describes Docker Compose, Kubernetes with Helm, RPM packages and manual systemd installation.incidentrelay.io · read 4 Oct 2026
- Event processing
- Event orchestration can enrich, group, route, suppress and automate events, with execution history to inspect rule matches and results.incidentrelay.io · read 4 Oct 2026
- Incident actions
- Responders can acknowledge, resolve, silence or escalate alerts, and the documentation describes temporarily shelving alert groups.incidentrelay.io · read 4 Oct 2026
- Integrations
- Documented alert sources include Alertmanager, AWS SNS and CloudWatch, Grafana, Azure Monitor, Zabbix, Sentry, LibreNMS and generic webhooks.incidentrelay.io · read 4 Oct 2026
- Intended users
- The maker presents IncidentRelay for SRE and DevOps teams seeking self-hosted incident management and on-call workflows.incidentrelay.io · read 4 Oct 2026
- Migration
- The maker says its Grafana OnCall and PagerDuty migration tools use public APIs, avoid product databases and default to dry-run mode.incidentrelay.io · read 4 Oct 2026
- Notification channels
- Documented notification options include Mattermost, Telegram, Slack, email, webhooks, Discord, Microsoft Teams and voice calls.incidentrelay.io · read 4 Oct 2026
- Notifications
- Available delivery methods include Slack, Mattermost, Telegram, email, Discord, Microsoft Teams, outbound webhooks, voice calls and browser/PWA push.incidentrelay.io · read 4 Oct 2026
- Orchestration
- Event orchestration can enrich, group, route, suppress and automate events using versioned rules.incidentrelay.io · read 4 Oct 2026
- Purpose
- IncidentRelay is open-source, self-hosted on-call management and incident response software for routing alerts, notifying responders, managing rotations and reducing alert noise.incidentrelay.io · read 4 Oct 2026
- Scheduling
- Teams can configure on-call schedules, rotation layers and temporary overrides.incidentrelay.io · read 4 Oct 2026
- Security
- Its webhook delivery guidance says HTTPS is required by default, private and special network addresses are denied unless allowlisted, and secret headers are encrypted and not returned by APIs.incidentrelay.io · read 4 Oct 2026
- Self-hosting
- Installation paths include Docker Compose, an RPM package and manual systemd; production installations run separate web/API and scheduler processes.incidentrelay.io · read 4 Oct 2026
