A Statuspage alternative you buy once. Hosted status pages are rented by the month, priced by the page, and hold your uptime history hostage. Here is the honest case for owning one instead — including who shouldn't.

Public pages run from $29 to $1,499 per month by tier (subscribers, team members, SMS); private pages start higher, and audience-specific pages are priced per page. It is a polished, battle-tested product — and after three years you've paid for it thirty times without owning anything.

The modern SaaS cohort is cheaper — think $15–$300/mo depending on pages, seats and branding removal — and genuinely good. The structure is the same: the bill scales with your client count, and your uptime history lives in their cloud, priced again every month.

One payment, $149, one company: unlimited status pages (multi-tenant, branded per tenant, on your domains), unlimited monitors and seats, plus the part hosted status pages don't include at any tier — the monitoring and incident timeline that feed the page, in the same codebase, on your Postgres.

Their global probe network and 24/7 ops team. Vigil checks from where you run it, and your team keeps the server alive — the sane setup is a $5 VPS outside the infrastructure it monitors, so the status page never shares fate with what it watches. If you can't own a VPS, stay on SaaS; that's the truthful answer.

No recurring bill, no per-page math, no seat counting. Your uptime history in your Postgres — exportable, queryable, yours when you leave. Full source with private modification rights: rebrand the sign-in screen, add a check type, wire your own alerting. And status pages that are ISR-cached at the edge, so outage traffic never touches your database.

Watch the 60-second film — the real app, seeded data, no cuts: monitors fail, an incident opens itself, the status page updates, recovery closes it. If that loop covers your case, the rest is a docker compose up away.