IncidentRelay
incidentrelay.io
- Free plan
- Linux
- Web
- API
- Self-hosted
What IncidentRelay is
IncidentRelay is open-source, self-hosted software for on-call management and incident response. It routes alerts using their source, labels, severity and team ownership, then applies team rules and escalation policies. Teams can set schedules, shifts, rotations, overrides and escalation chains. Responders can acknowledge, resolve, silence or escalate alerts, and temporarily shelve alert groups. Event rules can enrich, group, route, suppress and automate events; execution history shows rule matches and results. Incoming sources include Alertmanager, AWS SNS and CloudWatch, Grafana, Datadog, Zabbix, Sentry, LibreNMS, RMON, PagerDuty Events API v2, heartbeats and generic webhooks. Notifications can go to Slack, Mattermost, Telegram, email, Discord, Microsoft Teams, webhooks, voice calls and browser/PWA push. The automation interface includes Swagger UI, OpenAPI JSON, route-intake tokens and personal API tokens. Roles include viewer, editor, user_admin, responder and manager. Deployment options include Docker Compose, Kubernetes with Helm, RPM packages and manual systemd installation. The free plan is self-hosted.
Who it suits
It suits SRE and DevOps teams seeking self-hosted incident management and on-call workflows. Teams that need rotation scheduling, escalation policies and calendar exports may also find its tools relevant.
Good to know, and what to watch
- Routes alerts by source, labels, severity and ownership
- Supports schedules, rotations, overrides and escalation chains
- Offers multiple notification channels, including voice calls
- Exports schedules through CalDAV and tokenized ICS feeds
- Free, open-source and self-hosted
- Requires self-hosting
- Production uses separate web/API and scheduler processes
Plans
Every plan and priceIncidentRelay
Open source
Getting started
- Choose Docker Compose, Kubernetes with Helm, an RPM package, or manual systemd installation
- Deploy the web/API and scheduler processes for production
- Configure incoming alert integrations and route-intake tokens
- Create teams, roles, on-call schedules, rotations, and escalation policies
- Set notification channels and event-orchestration rules
- Connect automation through Swagger UI, OpenAPI JSON, or personal API tokens
Limits to check
The listed plan is free, open-source, and self-hosted. Using it requires running your own deployment, with production web/API and scheduler processes.
The verdict
IncidentRelay combines alert routing, response actions, scheduling and event automation in a self-hosted package. Its free plan may suit teams comfortable managing deployment themselves.
Questions people ask
How much does IncidentRelay cost?
The IncidentRelay plan is free and is open-source and self-hosted.
Which alert sources can it receive?
Sources include Alertmanager, AWS SNS and CloudWatch, Grafana, Datadog, Azure Monitor, Zabbix, Sentry, LibreNMS, RMON, PagerDuty Events API v2, heartbeats, and generic webhooks.
Which notification channels are available?
Notifications can use Slack, Mattermost, Telegram, email, Discord, Microsoft Teams, webhooks, voice calls, and browser or PWA push.
How can IncidentRelay be installed?
Deployment options are Docker Compose, Kubernetes with Helm, RPM packages, and manual systemd installation.
Can schedules be synchronized with calendars?
On-call schedules can be exported through read-only CalDAV calendars and tokenized ICS feeds.
What roles does it provide?
Documented roles include viewer, editor, user_admin, responder, and manager.
What the maker publishes
- Access controls
- The documentation describes group and team roles, including viewer, editor, user_admin, responder and manager. source
- 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. source
- Alert routing
- It routes incoming alerts by source, labels, severity and team ownership, then applies escalation policies and team rules. source
- Automation API
- IncidentRelay provides Swagger UI and OpenAPI JSON, with route intake tokens for incoming integrations and personal API tokens for user-scoped automation. source
- Calendar exports
- On-call schedules can be exported through read-only CalDAV calendars and tokenized ICS feeds. source
- Deployment options
- The documentation describes Docker Compose, Kubernetes with Helm, RPM packages and manual systemd installation. source
- Event processing
- Event orchestration can enrich, group, route, suppress and automate events, with execution history to inspect rule matches and results. source
- Incident actions
- Responders can acknowledge, resolve, silence or escalate alerts, and the documentation describes temporarily shelving alert groups. source
- Integrations
- Documented alert sources include Alertmanager, AWS SNS and CloudWatch, Grafana, Azure Monitor, Zabbix, Sentry, LibreNMS and generic webhooks. source
- Intended users
- The maker presents IncidentRelay for SRE and DevOps teams seeking self-hosted incident management and on-call workflows. source
- Migration
- The maker says its Grafana OnCall and PagerDuty migration tools use public APIs, avoid product databases and default to dry-run mode. source
- Notification channels
- Documented notification options include Mattermost, Telegram, Slack, email, webhooks, Discord, Microsoft Teams and voice calls. source
- Notifications
- Available delivery methods include Slack, Mattermost, Telegram, email, Discord, Microsoft Teams, outbound webhooks, voice calls and browser/PWA push. source
- Orchestration
- Event orchestration can enrich, group, route, suppress and automate events using versioned rules. source
- 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. source
- Scheduling
- Teams can create on-call schedules, shifts, rotations, overrides and escalation chains. source
- Scheduling
- Teams can configure on-call schedules, rotation layers and temporary overrides. source
- 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. source
- Self-hosting
- Installation paths include Docker Compose, an RPM package and manual systemd; production installations run separate web/API and scheduler processes. source
Checked against the maker's pages on 4 Oct 2026.