HeyOnCall vs IncidentRelay

HeyOnCall combines website and API monitoring with incident management and on-call paging. Checks cover HTTP and HTTPS availability and performance, response assertions, redirects, and request or response inspection. SSL monitoring validates certificates and chains and can warn before expiration; heartbeat and cron monitoring are also included. Teams can set timezone-aware rotations, change or trade shifts, and sync Google Calendar, Outlook, or iCalendar feeds. Unacknowledged incidents can escalate to another user, a rotation, or everyone in a rotation. Its iOS and Android Critical Alerts can bypass Do Not Disturb, silent or vibrate modes, and volume settings, and repeat until acknowledged. Alert sources include Datadog, Prometheus Alertmanager, Uptime Kuma, and other webhook-capable tools; notifications can be sent through Slack, email, Telegram, or webhooks. The API supports custom triggers, incident resolution, and custom payloads. Plans are billed monthly: Free Trial for evaluating is free, Solo is $3 a month, and Pro is $32 a month. The evaluation plan limits users and triggers, while paid plans are limited to 1000 triggers of each listed type.

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.