Skip to content
SPECIFICTION
Get listed

IncidentRelay

incidentrelay.io

Free plan WebLinuxAPISelf-hosted
Visit incidentrelay.io
Spec score 8.4 #8 of 25 in On-Call Scheduling Software

What it is

IncidentRelay is open-source software for self-hosted on-call management and incident response. It routes incoming alerts by source, labels, severity, and team ownership, then applies team rules and escalation policies. Teams can manage schedules, shifts, rotations, overrides, and escalation chains; responders can acknowledge, resolve, silence, or escalate alerts and temporarily shelve alert groups. Versioned event rules can enrich, group, route, suppress, and automate events, with execution history showing matches and results. Documented inputs include Alertmanager, AWS SNS and CloudWatch, Grafana, Datadog, Azure Monitor, Zabbix, Sentry, LibreNMS, PagerDuty Events API v2, RMON, heartbeats, and webhooks. Notifications include chat services, email, voice calls, outbound webhooks, and browser/PWA push. The automation interface provides Swagger UI, OpenAPI JSON, route-intake tokens, and personal API tokens. On-call calendars can be exported through CalDAV and ICS. Deployment options include Docker Compose, Kubernetes with Helm, RPM packages, and manual systemd installation. The IncidentRelay plan costs nothing; it is open-source and self-hosted.

Spec sheet

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.Read 4 Oct 2026 · incidentrelay.io
Intended users
The maker presents IncidentRelay for SRE and DevOps teams seeking self-hosted incident management and on-call workflows.Read 4 Oct 2026 · incidentrelay.io
Integrations
Documented alert sources include Alertmanager, AWS SNS and CloudWatch, Grafana, Azure Monitor, Zabbix, Sentry, LibreNMS and generic webhooks.Read 4 Oct 2026 · incidentrelay.io
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.Read 4 Oct 2026 · incidentrelay.io
Access controls
The documentation describes group and team roles, including viewer, editor, user_admin, responder and manager.Read 4 Oct 2026 · incidentrelay.io
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.Read 4 Oct 2026 · incidentrelay.io
Alert routing
It routes incoming alerts by source, labels, severity and team ownership, then applies escalation policies and team rules.Read 4 Oct 2026 · incidentrelay.io
Automation API
IncidentRelay provides Swagger UI and OpenAPI JSON, with route intake tokens for incoming integrations and personal API tokens for user-scoped automation.Read 4 Oct 2026 · incidentrelay.io
Calendar exports
On-call schedules can be exported through read-only CalDAV calendars and tokenized ICS feeds.Read 4 Oct 2026 · incidentrelay.io
Deployment options
The documentation describes Docker Compose, Kubernetes with Helm, RPM packages and manual systemd installation.Read 4 Oct 2026 · incidentrelay.io
Event processing
Event orchestration can enrich, group, route, suppress and automate events, with execution history to inspect rule matches and results.Read 4 Oct 2026 · incidentrelay.io
Incident actions
Responders can acknowledge, resolve, silence or escalate alerts, and the documentation describes temporarily shelving alert groups.Read 4 Oct 2026 · incidentrelay.io
Migration
The maker says its Grafana OnCall and PagerDuty migration tools use public APIs, avoid product databases and default to dry-run mode.Read 4 Oct 2026 · incidentrelay.io
Notification channels
Documented notification options include Mattermost, Telegram, Slack, email, webhooks, Discord, Microsoft Teams and voice calls.Read 4 Oct 2026 · incidentrelay.io
Notifications
Available delivery methods include Slack, Mattermost, Telegram, email, Discord, Microsoft Teams, outbound webhooks, voice calls and browser/PWA push.Read 4 Oct 2026 · incidentrelay.io
Orchestration
Event orchestration can enrich, group, route, suppress and automate events using versioned rules.Read 4 Oct 2026 · incidentrelay.io
Scheduling
Teams can configure on-call schedules, rotation layers and temporary overrides.Read 4 Oct 2026 · incidentrelay.io
Self-hosting
Installation paths include Docker Compose, an RPM package and manual systemd; production installations run separate web/API and scheduler processes.Read 4 Oct 2026 · incidentrelay.io

Plans and prices

IncidentRelay Free Open-source · Self-hosted Read 4 Oct 2026 · incidentrelay.io

Every IncidentRelay plan and price →

Strong points and limits

Strong points

  • Routes alerts using source, labels, severity, and ownership.
  • Supports schedules, rotations, overrides, and escalation chains.
  • Offers versioned event rules with execution history.
  • Exports schedules through CalDAV and ICS feeds.
  • Available free as open-source, self-hosted software.

Limits

  • Self-hosting requires deployment and process setup.
  • Other listed delivery options may require external services.

Who it suits

IncidentRelay suits SRE and DevOps teams looking for self-hosted incident management and on-call workflows. Its schedules, integrations, and notification options also serve teams coordinating responders across different alert sources.

Verdict

IncidentRelay combines alert routing, on-call scheduling, response actions, and event automation in a self-hosted package. Its free plan is clearly listed, along with several deployment paths and extensive integration and notification options.

Where Specifiction places it

Alternatives to IncidentRelayAll alternatives →