IncidentRelay vs Spike.sh
IncidentRelay
incidentrelay.ioSpike.sh
spike.shSide by side
| Figure | IncidentRelay | Spike.sh |
|---|---|---|
| Price from | Free | $7/mo |
| Free plan | Yes | — |
| Free trial | — | Yes |
| Open source | — | — |
| Web | Yes | Yes |
| Linux | Yes | — |
| iOS | — | Yes |
| Android | — | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | — |
| Plans published | 1 | 3 |
| Spec score · On-Call Scheduling Software | 8.4 (#8) | 8.2 (#10) |
| Integrations | Documented alert sources include Alertmanager, AWS SNS and CloudWatch, Grafana, Azure Monitor, Zabbix, Sentry, LibreNMS and generic webhooks. | Spike says it connects to 80+ monitoring tools, cloud platforms, and error trackers, including Datadog, Prometheus, Grafana, Sentry, Slack, and Microsoft Teams. |
| 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. | Spike is an incident management and alerting platform that calls the team when things go wrong and helps triage, fix, and close incidents. |
| 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. | Spike says data is encrypted at rest with AES-256, traffic uses TLS and HSTS, production access is limited, and backups are encrypted. |
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.
Spike.sh
Spike.sh is an incident-management and alerting service for calling responders when systems fail, then helping teams triage, fix, and close incidents. It groups and de-duplicates alerts, detects duplicate incidents and recoveries, and uses AI to draft titles and suggest severity and priority. On-call schedules and escalation policies route alerts through phone, SMS, Slack, or the mobile app; MCP connections support AI clients and agents. Status pages can use custom domains or private access and include live widgets, incident history, planned maintenance, and subscriber updates by email, Slack, RSS, or Atom. Spike says it connects to more than 80 monitoring tools, cloud platforms, and error trackers. Standard costs $7.00 per user per month and includes 100 total phone and SMS alerts, one one-person schedule, one central number, and five incoming calls monthly. Business is $14.00 per user per month with unlimited phone and SMS alerts, multiple teams, unlimited schedules, and unlimited live call routing. Enterprise pricing is by contact. There is no free plan; a 14-day trial is available.