Self-hosted status page tools

The self-hosted status page tool with the least to run is not the most popular one. Upptime checks run on GitHub Actions, incidents are GitHub Issues, and the public page is static on GitHub Pages, so there is no server and no database anywhere. Everything else here asks you to run something, and how much is the real choice.

Licences, star counts and repository activity were checked against each project's own GitHub repository on 22 August 2026, and hosted prices against each vendor's own pricing page the same day.

Status pages are a different category to a feature request board, but the self-hosting maths underneath is the same one this site works through in self-hosting a feature request board.

What do you actually have to run?

Sorted by infrastructure, lightest first, because that is what a small team is actually choosing between.

Cachet is worth a second look before you trust its repository badge: GitHub reports the licence as NOASSERTION, which reads as "unclear", but the project's own LICENSE file is plainly BSD-3-Clause. GitHub's detector missed it; the file did not change. Read the LICENSE file itself rather than the badge. Openstatus is AGPL-3.0 and also sells its own hosted version, so it sits in open-core territory: check directly what the free self-hosted build includes rather than assuming.

Why does Upptime deserve to lead this list?

Because it removes the question rather than answering it well. A scheduled GitHub Actions workflow runs the checks, incidents live as GitHub Issues, and GitHub Pages serves the built page, so there is no process to keep alive. Upptime's own README states the case plainly: it is "completely free if you're already using GitHub since there's no external server or subscription needed." That is the same argument this site makes about a support centre, made independently, in a different category, and the honest move is to credit Upptime for it rather than claim it as original to Docket, which has no stake here.

Its limits matter too. Incidents are GitHub Issues, not a purpose-built timeline with severity levels or subscriber-facing updates, and running on GitHub Actions and Pages means your status page's own uptime is now GitHub's, a real irony for a tool whose whole job is reporting on uptime. Both are the price of nothing to run yourself.

Why is Uptime Kuma the popular full-featured option?

At 90,467 stars, checked 22 August 2026, Uptime Kuma is by a wide margin the most starred project here. MIT licensed, it runs from Docker or Node 20.4 or later with SQLite by default, and it was pushed as recently as 22 August 2026, so it is actively maintained as well as popular. It gives you an admin interface, notification integrations and a monitor dashboard in one running application: a process to operate, in exchange for a full UI rather than a repository of YAML.

What about Gatus and Cachet?

Gatus is the config-file option. Apache-2.0, 11,882 stars at the time of checking, pushed as recently as 18 August 2026, running from a YAML file with checks held in memory unless you add SQLite or Postgres. That makes it the lightest option still running as a process, useful for a team happier editing YAML than clicking through a UI.

Cachet is the heaviest to stand up: PHP, a web server and Composer, 15,224 stars at the time of checking. It predates most of the others here, but a PHP stack is more moving parts than Gatus, Uptime Kuma or Upptime ask for.

Is Statping-ng still alive?

Not really, and this is the cautionary tale in this list. It is not archived, so a listicle checking only that will happily call it live. But its last push was 4 June 2025, and it carries 194 open issues. GPL-3.0, 1,988 stars at the time of checking, Docker to run. Neither figure says anything about whether anyone is behind it now. Read the last commit date before deploying anything here, not the badge and not the star count.

What do the hosted options cost?

For teams who would rather pay than run any of the above.

Atlassian Statuspage's ladder is the clearest published shape here: four fixed tiers from free up to $1,499 a month, each unlocking more subscribers and components. Better Stack does something more unusual: rather than tiers that bundle features together, a status page is priced per feature. A second status page is $15 a month on its own, white labelling $250 per page per month, SSO another $250 per page per month, each an independent line rather than a step up a ladder. That matters when comparing headline numbers, because a similar entry price can hide very different totals once you add what you actually want. Better Stack's base plan price and Instatus's paid tiers could not be confirmed; both render client-side rather than in the raw HTML.

Which one should you actually run?

Already using GitHub for the product this status page reports on? Upptime costs nothing extra to operate, once you accept that incidents are Issues and your uptime now includes GitHub's. Want a full admin interface and do not mind Docker or Node running somewhere? Uptime Kuma is the popular, actively maintained default. Prefer editing a config file over clicking through a UI? Gatus is the lighter option. Skip Statping-ng regardless of what a search result says about it being unarchived; 194 open issues and no push in over a year is not a tool to build on. Want nobody on your side operating anything? Atlassian Statuspage or Openstatus are the two vendors here whose pricing you can actually read before signing up.

Whether a page has to be backed by a running process at all is worked through for a different category in static site or server, and the failure profile of each shape, static against self-run against hosted, is broken down in uptime, static against hosted.

Frequently asked questions