IncidentRelay vs Wachd
IncidentRelay
incidentrelay.ioWachd
wachd.ioSide by side
| Figure | IncidentRelay | Wachd |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Linux | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · On-Call Scheduling Software | 8.4 (#8) | 7.3 (#20) |
| Spec score · On-Call Management Software | 8.2 (#12) | 7.4 (#25) |
| Access controls | The documentation describes group and team roles, including viewer, editor, user_admin, responder and manager. | It lists Entra ID, Okta, and Google Workspace group mappings, with local accounts available as break-glass access. |
| Integrations | Documented alert sources include Alertmanager, AWS SNS and CloudWatch, Grafana, Azure Monitor, Zabbix, Sentry, LibreNMS and generic webhooks. | The site lists Grafana, Datadog, Prometheus, Loki, PagerDuty webhooks, GitHub, GitLab, Slack, Microsoft Teams, Twilio, and several AI inference backends. |
| Intended users | The maker presents IncidentRelay for SRE and DevOps teams seeking self-hosted incident management and on-call workflows. | Wachd says it is built for DevOps and SRE teams. |
| Notifications | Available delivery methods include Slack, Mattermost, Telegram, email, Discord, Microsoft Teams, outbound webhooks, voice calls and browser/PWA push. | Notifications can use SMS, voice calls, email, and Slack, with escalation for unacknowledged alerts and cancellation when resolved. |
| 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. | Wachd receives monitoring alerts, gathers related context, and sends an AI-generated root cause diagnosis to the on-call engineer. |
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.
Wachd
Wachd is a free, open-source incident alert and diagnosis service for DevOps and SRE teams. It receives monitoring alerts, gathers nearby operational context, and sends an AI-generated root-cause diagnosis to the on-call engineer. Context can include the last 10 GitHub commits, 30 minutes of Loki or Datadog error logs, and metric history around the alert. Supported AI backends include in-cluster Ollama, vLLM, OpenAI-compatible models, Claude, OpenAI, and Gemini. On-call schedules support primary, secondary, and custom rotations, time restrictions, and self-service overrides. Notifications can use SMS, voice, email, or Slack, with escalation for unacknowledged alerts and cancellation after resolution. Wachd runs in the customer's Kubernetes cluster, can keep incident data inside its VPC, and supports air-gapped in-cluster deployments. It says emails, IP addresses, API keys, and account IDs are stripped before AI processing. The Apache 2.0 plan costs nothing and has no licence fees.