BenchRank
#37 in Monitoring & ObservabilityUpdated 2026-08

Wachd

by Wachd · Self-hosted on-call with AI root cause analysis on Kubernetes

BenchRank score

36.2 — BenchRank score out of 100

Screenshots of Wachd

Homepage · Wachd

Homepage of Wachd

Overview

Wachd is a self-hosted on-call tool that receives alerts from Grafana, Datadog and Prometheus by webhook. For each alert it collects recent commits, 30 minutes of error logs and metric history, strips PII, then uses an in-cluster or cloud model to produce a plain-English root cause. It also covers rotas, escalation and per-user SMS, voice, email and Slack notifications.

Best for
DevOps and SRE teams who need on-call and incident data to stay inside their own cluster
Pricing
Free self-hosted Apache 2.0 tier, SMB at $99/month, and a custom-priced Enterprise tier listed as coming soon.
Runs on
Self-hosted

Strengths and trade-offs

Strengths

  • Runs in your own cluster; air-gapped with in-cluster models
  • Apache 2.0 free tier covers unlimited teams and users
  • Read-only: cannot deploy, restart or change infrastructure
  • Pulls commits, logs and metrics into one root-cause summary

Trade-offs

  • Self-hosting needs a Kubernetes cluster; no hosted option is offered
  • SSO, audit logs and compliance reports sit in an unreleased tier
  • Cloud AI models (Claude, OpenAI, Gemini) require the $99/mo tier
  • Enterprise pricing is not published — sales contact only

How Wachd markets itself

A structured read of the promise, proof and page design on Wachd’s captured homepage.

Homepage capture

“Your on-call engineer gets answers, not just alerts”

  • Angle: Outcome / benefit-led
  • Hero: Terminal / CLI

Pricing

Published plans and prices from Wachd’s own pricing page.

How this score is made up

Each dimension is scored out of 100 and combined into the headline score using fixed weights.

  • MCP support

    Whether an agent can drive the product through the Model Context Protocol, and how much setup that takes.

  • Documentation

    Publicly reachable docs — coverage, freshness, code samples and machine readability.

  • Agent friendliness

    How readable the site is to an automated client: llms.txt, structured data, server-rendered content, crawler access.

  • Changelog

    A public, dated record of what shipped and when — the clearest signal that a product is still alive.

  • Marketing site structure

    Whether the site answers a buyer's questions: clear positioning, the pages that matter, and accessibility.

  • Page speed

    How fast the site loads for real visitors: Chrome UX Report 75th-percentile LCP, INP and CLS, with a Lighthouse mobile run standing in where a site has too little traffic for field data.

  • Operational trust

    Status page and incident history, security disclosure, compliance and data-processing documentation.

Measured, but not part of the score

Useful to know, but not a mark for or against the product — so these do not affect the ranking.

  • Openness

    Source availability, self-hosting, data export and open standards. Scored and shown, but not part of the composite — paid SaaS is not worse for being paid SaaS.

  • Maintenance

    Release cadence and repository activity. Scored and shown, but not part of the composite — it is only measurable for open repositories.

This doesn’t look right — report a problem with Wachd’s score

Where this comes from

The Wachd pages BenchRank reads when it scores the product — its documentation, release notes, status and security pages, and its repository where there is one.

Alternatives in Monitoring & Observability

  • Ranked 1

    87.4 — BenchRank score out of 100

    openstatus

    OpenStatus · Open source status pages with uptime monitoring from 28 regions

    Best for: Teams that need a public status page and uptime checks while working towards SOC 2.

  • Ranked 2

    86.7 — BenchRank score out of 100

    OneUptime

    OneUptime · Open-source observability and incident management on one platform

    Best for: Teams wanting monitoring, on-call, status pages and observability on one open-source platform

  • Ranked 3

    83.1 — BenchRank score out of 100

    Sentry

    Sentry · Error tracking and application performance monitoring for developers

    Best for: Development teams wanting error monitoring, tracing and session replay tied to one trace

See all 48 alternatives to Wachd

Is this your product?

Claim Wachd to manage its profile. Claiming lets you suggest edits to the descriptive fields — it never changes scores or rankings.

Claim this business

Report a problem with this page

Report an issue with Wachd