BenchRank
#1 in Monitoring & ObservabilityUpdated 2026-08

openstatus

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

BenchRank score

87.4 — BenchRank score out of 100

Screenshots of openstatus

Homepage · openstatus

Homepage of openstatus

Overview

openstatus is a status page and uptime monitoring service. It checks HTTP endpoints, including REST and GraphQL, from 28 regions across three cloud providers, and publishes a status page with incident reports, maintenance windows and email, RSS/Atom and SSH subscriptions. Monitors can be run through the dashboard, a CLI, an API, an MCP server or a Terraform provider.

Best for
Teams that need a public status page and uptime checks while working towards SOC 2.
Pricing
Free to start, then Starter $30/month, Pro $100/month and Scale $500/month, with a yearly option advertised as two months free and Enterprise by quote.
Runs on
WebSelf-hosted

Strengths and trade-offs

Strengths

  • Checks run from 28 regions across three cloud providers
  • Monitors as code via YAML, Terraform, API, CLI or MCP server
  • Open source, free to start, no credit card required
  • Custom domains, password protection and subscriber channels

Trade-offs

  • Custom theme and private locations need Pro at $100/mo or above
  • White label is a $300/mo add-on unless you are on Scale
  • SSO/SAML costs $250/mo extra on every published plan
  • Starter checks only every 60s and keeps 3 months of data

How openstatus markets itself

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

Homepage capture

“Ship your status page before your SOC 2 auditor asks for it”

  • Angle: Fear / risk avoidance
  • Hero: Product screenshot

Pricing

Published plans and prices from openstatus’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.

  • API quality

    Public API surface: machine-readable spec, official SDKs, documented auth, errors, rate limits and versioning.

  • 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.

  • Pricing transparency

    Whether real prices are published, self-serve signup exists, and usage costs are knowable without a sales call.

  • 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 openstatus’s score

Where this comes from

The openstatus 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 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

  • Ranked 4

    82.7 — BenchRank score out of 100

    Pydantic Logfire

    Logfire · OpenTelemetry-based observability for AI and general applications

    Best for: Engineering teams tracing LLM agents alongside the rest of their application stack in one tool.

See all 48 alternatives to openstatus

Is this your product?

Claim OpenStatus 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 openstatus