OpenStatus trades a status-page subscription for self-hosting work

The workload

OpenStatus is an open-source status-page and uptime-monitoring project that a founder can run on their own infrastructure instead of paying a hosted vendor. Choosing it swaps a subscription fee for a self-hosting workload: standing up the application, keeping it patched, and being the one who gets paged if the monitoring system itself goes down, a second layer of operational responsibility a hosted vendor would otherwise absorb.

What the documents show

Verified: the project's own GitHub README describes OpenStatus as an “open-source uptime monitoring and status page platform built for infra as code,” configured through YAML or Terraform, checking endpoints from 28 regions across three cloud providers, and distributed under the AGPL-3.0 licence, a copyleft licence that requires anyone who runs a modified version as a network service to make their source changes available. Verified: the README's stated self-hosting path is a Docker Compose deployment, requiring Node.js 20 or later, pnpm, and a Turso database CLI, with the dashboard and public status pages running on separate local ports. Verified: OpenStatus's own marketing site lists a free hosted tier alongside paid hosted plans starting at $30 a month, so the project is not exclusively self-hosted; a founder can also simply pay for the hosted version and skip the self-hosting workload above. Neither document states uptime or reliability figures for either path.

The operating cost

Verified as a stated requirement, not a fee: self-hosting means the compute needed to run the described Docker image plus a database, and the AGPL-3.0 obligation to publish source changes if the self-hosted instance is offered as a service to others. The alternative, paying $30 a month and up for the hosted tiers the marketing site lists, replaces that infrastructure and licence obligation with a straightforward subscription cost; the README does not state which choice costs less overall, since that depends on infrastructure the operator already has.

The stop condition

Neither document names a point at which self-hosting stops being worth it. Editorially: the trade-off is legible enough to state as a threshold, self-hosting stops making sense once the time spent patching, monitoring and troubleshooting the status-page instance itself exceeds what the cheapest paid hosted tier would have cost, a comparison the operator has to make since neither source supplies it.

• Does the operator already run the infrastructure this requires, or would it be new surface area?
• Who gets paged if the self-hosted status page itself goes down, and is that the same person the page exists to reassure?
• Does offering the self-hosted instance to anyone else trigger the AGPL-3.0 source-disclosure obligation?

OpenStatus documents a genuine choice, not a free option: the subscription fee a hosted vendor charges is replaced by infrastructure and licence obligations the project's own README states plainly, and the cheaper path depends on what the operator already has running.