OpenStatus

28 parallel global check regions Probes run across 28 regions on Fly.io, Koyeb, and Railway at the same time, so each check produces a genuine global snapshot instead of one server's viewpoint.[1][2]

Assertion-based API monitoring Monitors accept any method with custom headers and a body, then assert on status code, headers, body content, and latency, with separate degraded and timeout thresholds.[1]

Per-phase latency breakdown Every check records DNS, connect, TLS, time to first byte, and transfer separately, which separates a slow origin from a slow handshake.[1]

Branded status pages Pages support custom domains, component groups, external dependencies, maintenance windows, password protection, and subscriber updates by email, RSS, Atom, JSON, and Slack Connect. Pages are localized into seven languages, with custom themes and white labelling on higher plans or as paid extras.[1]

Slack-native incident response Mentioning the OpenStatus agent in a thread drafts a status report for human approval, and incidents carry severity, a commander, and a full timeline.[1][2]

Monitoring as code A Terraform provider, CLI, YAML declarations, and an MCP server let teams review monitor changes in pull requests or drive incidents from AI assistants. Existing dashboard monitors can be bootstrapped into HCL with a generate command.[1][2][3]

Wide alert routing Notifications reach Slack, Discord, PagerDuty, Opsgenie, email, SMS, and webhooks, plus Telegram, Google Chat, Microsoft Teams, WhatsApp, Grafana OnCall, and ntfy.[1]

Self-hostable AGPL-3.0 core The repository is licensed AGPL-3.0, and private check locations run as a single 8.5MB Docker image, so teams can keep probing inside their own network.[1][2][3]

SaaS teams that need a status page tied to real monitoring: components fill uptime from attached monitors, and approved reports reach subscribers without manual copying between tools.[1][2]

Teams that coordinate incidents in Slack: declaring, updating, and resolving incidents inside a thread, with confirmation before anything goes public, matches an on-call chat workflow.[1][2]

Operators who manage infrastructure in code: Terraform declarations, CLI application from CI, and an MCP server fit teams that already review infrastructure changes as pull requests.[1][2]

Homelab users wanting a free single-server monitor: Uptime Kuma runs on one VPS at no software cost, while OpenStatus charges from $30 per month for serious managed use.[1][2]

Organizations that cannot accept AGPL-3.0 for self-hosting: the copyleft license governs the self-hosted core, so teams with incompatible licensing policies should seek legal review first.[1]

Teams needing built-in log management or escalation ladders: the vendor's own comparison states OpenStatus has no log management and no incident escalation ladders, unlike some broader suites.[1]