MonoDuty vs Wachd

MonoDuty is a workspace-based incident management service for teams responsible for production systems. It brings together team-owned services, on-call schedules, escalation policies, Heartbeats, uptime Monitors, and email, SMS, and voice notifications. All published plans include on-call scheduling. Systems that can send HTTP requests can submit incidents through its Universal HTTP Webhook using MonoDuty's documented JSON payload; Pro and Business plans can send lifecycle updates to Slack, Discord, and Microsoft Teams. Monitors check websites and APIs from Helsinki, tracking response times, validating responses, checking HTTPS certificates, and alerting on recovery. A REST API uses scoped, short-lived customer tokens, with documented access for incidents, services, and Monitors. Security controls include TLS 1.2/1.3, workspace roles, rate limits, CSRF protection, and optional time-based one-time-password MFA. MonoDuty says it does not currently publish security certifications. Its production service runs on a single European virtual server, without promised geographic failover, load-balanced application replicas, or provider redundancy. The free plan includes seven-day incident retention; Pro and Business list 30- and 90-day retention. A 14-day trial is listed.

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.