IncidentRelay vs Squid Alerts
IncidentRelay
incidentrelay.ioSquid Alerts
squidalerts.comSide by side
| Figure | IncidentRelay | Squid Alerts |
|---|---|---|
| Price from | Free | $89/mo |
| Free plan | Yes | — |
| Free trial | — | Yes |
| Open source | — | — |
| Web | Yes | Yes |
| Linux | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | — |
| Plans published | 1 | 2 |
| Spec score · On-Call Scheduling Software | 8.4 (#8) | 7.6 (#16) |
| Alert routing | It routes incoming alerts by source, labels, severity and team ownership, then applies escalation policies and team rules. | Routing rules can forward alerts to another team, convert them to incidents, or ignore them. |
| Integrations | Documented alert sources include Alertmanager, AWS SNS and CloudWatch, Grafana, Azure Monitor, Zabbix, Sentry, LibreNMS and generic webhooks. | The maker names ServiceNow, JIRA, SolarWinds, Microsoft Teams, Slack, Splunk, and Jenkins as integration examples. |
| 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. | Squid Alerts provides on-call calendars, incident escalation, and rule-based alert routing for IT organizations. |
| 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 data security policy says data in transit is encrypted with SSL and HTTPS/TLS and data at rest with AES-256 or higher. |
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.
Squid Alerts
Squid Alerts has no write-up on Specifiction yet; its figures are above.