openstatus

Visit Website

Introduction

openstatus is an open-source status page, incident response and uptime monitoring platform built for infrastructure as code. Monitors, status pages and notification channels are declared in YAML or Terraform, applied from the CLI or CI, and operable from Claude, ChatGPT or Cursor over MCP. It is available as a managed service or self-hosted.

It is built for humans and agents alike: there is an MCP server, a CLI with --json output, a typed API, read-only or read-write key scopes, and every mutation lands in an audit log. Monitoring runs from 28 global regions across three cloud providers in parallel, and private locations run in a single 8.5 MB Docker image, so you can check internal services too.

Status pages support custom domains, password protection, maintenance windows and subscriber notifications by email and RSS. Alerts go to Slack, Discord, PagerDuty, email and more when services are down or slow. Because status pages and monitoring live in one tool, you do not need to wire a separate monitoring service into your status page.

Incident response is a newer focus. From the dashboard you declare an incident, set severity (critical, major or minor), assign a commander and move it from open to mitigated to resolved, with each change on a timeline. In Slack you mention the openstatus agent to declare, update, resolve or add notes, and can bind an incident to a channel. Status reports can be linked to incidents so users see progress, and the same incident tools are available over MCP.

Pricing is flat with unlimited members: there are no per-seat or per-subscriber charges, which suits teams where many people need access.

For testing teams, defining monitors in code means synthetic API checks can be reviewed in pull requests and applied from CI, just like tests. Monitoring is the last line of a testing strategy: it catches what tests, reviews and staging missed. Wire its alerts into the same place your CI failures go, and when an incident reveals a gap, add a test or a synthetic check so the same failure is caught before release next time.

The source code is at openstatusHQ/openstatus on GitHub under the AGPL-3.0 licence, with about 9,300 stars; the most recent commit was on 10 November 2026.

Status pages are also part of incident communication, so rehearse an incident in staging: declare it from Slack, update the status page and confirm subscribers receive notifications before you need it for real.

Defining monitors next to the services they watch also keeps them current when endpoints change.

For smaller teams, the flat pricing with unlimited members is a practical advantage: support, sales and engineering can all access incidents without negotiating extra seats.

Features

1. Infrastructure as code: YAML or Terraform monitors and pages.
2. 28 global regions: Parallel checks across three clouds.
3. Private locations: 8.5 MB Docker image.
4. Status pages: Custom domains, passwords and maintenance windows.
5. Incident response: Severity, commander and timeline.
6. Slack agent: Run incidents in Slack.
7. MCP server: AI clients manage monitors and incidents.
8. JSON CLI and typed API: Automation-friendly.
9. Audit log: Every mutation recorded.
10. Subscriber notifications: Email, RSS and webhooks.

Pros

1. Flat pricing: Unlimited members, no per-seat fees.
2. Free to start: Free plan and 14-day Starter trial.
3. Free to use: Open source under the AGPL-3.0 licence, so the core tool costs nothing to use.
4. Actively maintained: The repository had commits as recent as 10 November 2026.
5. Community: About 9,300 GitHub stars.

Cons

1. AGPL-3.0: Copyleft for modified hosted versions.
2. Newer incident features: Less mature than dedicated incident tools.

Usage and Links (Example)

1. Sign up free or self-host from the openstatusHQ/openstatus repository.
2. Declare monitors and a status page in YAML or Terraform.
3. Apply the configuration from the CLI in CI.
4. Connect Slack and the MCP server for incidents.

Resources:

• openstatus website
• GitHub repository

Pricing

openstatus is free to start; the Starter plan has a 14-day free trial with no card, and paid plans start at $30 a month with unlimited members. Self-hosting the AGPL-3.0 edition is free.

Recommended for?

1. Startups wanting a public status page and uptime checks in one place.
2. Platform teams managing monitors as code.

Conclusion

openstatus is a modern, code-first status and uptime platform with fair, flat pricing.

Keep its configuration in the same repository as your tests.

On CheckOps, openstatus is filed under the Production monitoring & observability, Release & CI gates and API & contract testing stages. Related tools listed here include Uptime Kuma, Checkly, Better Stack, UptimeRobot, Pingdom and Grafana. Which one fits best depends mostly on your stack, your team’s size and skills, and whether you prefer to run tools yourself or pay for a managed service. This page reflects the official website, documentation and repository as they stood on 11 November 2026.