PagerTree vs Wachd

PagerTree helps teams share on-call responsibility and respond to incidents. Its scheduler supports rotations, overrides, reminders, calendar sync, and public, private, or password-protected schedules. Escalation policies allow unlimited layers, configurable timeouts, repeated alerts up to three times, and reassignment. Notifications can arrive by push, email, SMS, voice, WhatsApp, or Slack. PagerTree can aggregate and deduplicate similar alerts, with aggregation periods configurable from 15 minutes to 30 days. Integration options include email, webhook, and custom webhook. Single sign-on uses SAML 2.0 and supports identity providers such as Azure, Okta, and Google. PagerTree says data is encrypted at rest with AES-256, communications use SSL/HTTPS, and encrypted database backups run hourly. Basic costs nothing for up to five users and two teams, with three months of data retention. Pro is $15 a month per user; Elite is $19 a month per user. SMS and voice coverage varies by country.

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.