IncidentRelay vs LinkedIn Oncall

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.

LinkedIn Oncall has no write-up on Specifiction yet; its figures are above.