01
Smart alert routing
Route incoming alerts by source, labels, severity and team ownership. Keep alert rules clear, predictable and useful for incident management.
Self-hosted incident response for SRE and DevOps teams
Wake the right engineer. Keep incident data in your infrastructure.
IncidentRelay turns monitoring events into owned incidents with routing, on-call schedules, escalation policies and explainable orchestration — without handing the operational loop to a hosted platform.
{
"alertname": "DiskFull",
"severity": "critical",
"team": "platform",
"status": "firing",
"actions": [
"acknowledge",
"resolve",
"silence"
]
}
Critical
Escalate immediately
ACK
Stop noisy reminders
Routes
Match by labels
Teams
Group scoped access
Why IncidentRelay
Everything needed for on-call scheduling, alert escalation and incident response.
02
On-call schedules and rotations
Build team schedules, on-call shifts, overrides and escalation chains so alerts always reach the current responsible engineer and keep 24/7 coverage visible.
03
Actionable notifications
Send rich messages with acknowledge, resolve and escalation actions to Mattermost, Telegram, email, voice providers and other notification channels.
04
Silences and alert fatigue control
Silence known maintenance alerts, reduce duplicate notifications and keep incident history visible without losing important context.
05
Multi-team access model
Separate teams and groups, limit visibility and keep users focused on the alerts they are responsible for.
06
OpenAPI and automation
Integrate incident response automation and internal tools using documented API endpoints predictable JSON payloads and the Terraform provider for infrastructure-as-code workflows.
Product screenshots
See IncidentRelay in action.
Explore alert response, on-call scheduling, rotations, routing and decision traces in the real IncidentRelay interface.
Workflow
From alert to on-call ownership in seconds.
1
Receive
Accept alerts from AWS CloudWatch, Grafana, Alertmanager, Zabbix, RMON or generic webhooks.
2
Match
Apply route matchers, severity filters, escalation policies and team rules.
3
Notify
Send clean messages to the current on-call person or channel.
4
Act
Acknowledge, resolve, silence or escalate alerts without losing incident context.
Migration tools
Move from Grafana OnCall or PagerDuty with a dry-run first.
The migration tools use public APIs, never connect to product databases and run in dry-run mode by default. Review the generated report before applying changes.
Integrations
Connect the tools you already use.
IncidentRelay is designed for infrastructure teams that already have monitoring, chat and internal workflows. It works as a self-hosted routing layer between alert sources, on-call schedules, escalation policies and responders.
Use cases
Built for teams searching for self-hosted incident management.
IncidentRelay fits teams that need on-call management software, shift scheduling, alert routing, escalation policies and incident response automation without handing core operations workflows to a closed SaaS platform.
On-call management
Schedules, shifts, rotations, overrides and responder ownership.
Alert routing
Route AWS, Grafana, Alertmanager, Zabbix, RMON and webhook alerts by labels, source and severity.
Escalation policies
Notify the right people, remind responders and escalate unacknowledged alerts.
Incident response
Acknowledge, resolve, silence and track incidents from one workflow.
PagerDuty alternative
For teams looking for an open-source, self-hosted on-call workflow.
Grafana OnCall alternative
For teams that want alert routing, schedules and escalation in their own stack.
Explore IncidentRelay
Practical guides for choosing and running an on-call platform.
On-call scheduling software
Build schedules, shifts, layers, calendars and temporary overrides.
On-call rotation software
Keep ownership predictable and escalation paths clear.
Self-hosted on-call management
Keep alert data, schedules and incident workflows in your infrastructure.
Open-source PagerDuty alternative
Compare workflows, deployment control and operational trade-offs.
Grafana OnCall alternative
Evaluate a standalone self-hosted alert routing and scheduling platform.
Product tour
Follow an alert through routes, services, schedules, channels and incident actions.
Use cases
Explore workflows for SRE, DevOps, small teams and self-hosted alert routing.
Integration guides
Connect AWS, Grafana, Alertmanager, Zabbix, Sentry, LibreNMS, RMON, webhooks and chat channels.
Configuration examples
Copy route matchers, alert payloads, silences and severity filters.
Compare IncidentRelay
Review self-hosting, open-source and incident workflow trade-offs.
Roadmap
See the active development direction for routing, scheduling, integrations and operations.
Architecture
Understand how alerts move through integrations, routes, services, schedules and channels.
FAQ
Common questions about IncidentRelay.
What is IncidentRelay?
IncidentRelay is open-source on-call management and incident response software for routing alerts, notifying responders, managing rotations and reducing alert noise.
Is it a PagerDuty alternative?
IncidentRelay can be used by teams looking for a self-hosted, open-source approach to on-call scheduling, alert routing, escalation policies and incident response workflows.
Is it similar to Grafana OnCall?
IncidentRelay focuses on similar operational workflows: rotations, alert routing, escalation, acknowledgements, resolve actions, silences and monitoring integrations.
Which alert sources are supported?
IncidentRelay supports AWS SNS and CloudWatch, Grafana Alerting, Prometheus Alertmanager, Zabbix, Sentry, LibreNMS, RMON and generic webhook alerts, with OpenAPI support for custom automation and internal tools.
Get started
Run IncidentRelay your way.
Deploy with Docker, systemd or your own infrastructure. Start with the documentation rendered directly from the GitHub repository.