IncidentRelay vs OpsKnight
IncidentRelay
incidentrelay.io
OpsKnight
opsknight.comSide by side
| Figure | IncidentRelay | OpsKnight |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Linux | Yes | — |
| iOS | — | Yes |
| Android | — | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · On-Call Scheduling Software | 8.4 (#8) | 8.5 (#6) |
| Spec score · On-Call Management Software | 8.2 (#12) | 8.5 (#8) |
| Integrations | Documented alert sources include Alertmanager, AWS SNS and CloudWatch, Grafana, Azure Monitor, Zabbix, Sentry, LibreNMS and generic webhooks. | The integrations page lists 27 integrations, including Datadog, New Relic, Prometheus Alertmanager, Grafana, AWS CloudWatch, Slack, and Jira Cloud. |
| 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. | OpsKnight is a self-hosted incident command and on-call platform for alerting, paging, escalation, war rooms, status pages, and postmortem timelines. |
| 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. | The security page says stored credentials use AES-256-CBC envelope encryption and inbound webhook signatures are checked with constant-time verification. |
Plans
In their own words
IncidentRelay
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.
OpsKnight
OpsKnight is a self-hosted incident command and on-call platform for alerting, paging, escalations, war rooms, status pages, and incident timelines. Monitoring webhooks can create incidents for responders to acknowledge, assign, resolve, or group by fingerprint to reduce duplicate paging. On-call schedules support rotations, time zones, and swaps. Pages can be sent through SMS, push, Slack, Microsoft Teams, WhatsApp, or automated voice calls; pressing 1 acknowledges a voice page, and unanswered calls move to the next escalation tier. Community includes one status page per install, plus SLA policies, support-hours rules, and MTTA/MTTR analytics. The integrations page lists 27 native integrations, including Datadog, Sentry, Prometheus Alertmanager, Grafana Alerting, AWS CloudWatch, GitHub Actions, Slack, and Jira Cloud. Community is self-hosted, licensed under AGPL-3.0-only, and priced at free. It requires PostgreSQL 14+ and configured secrets; listed deployment options include Docker Compose, Docker Swarm, Helm, and Kustomize. The maker says it has no hosted cloud, external telemetry, or vendor phone-home.