Powered by IncidentFlare
That status page is the free plan
You clicked through from a page someone built here, so you already know what it looks like. The part worth knowing is what it cost them: nothing, no card, and about twenty minutes.
The page itself, on their domain
status.theirapp.com, light or dark, with the components their customers would name. The domain is a CNAME and a TXT record, and it is free here — Statuspage charges $29 a month for the same thing.
The 90-day uptime chart
Built from real checks, one bar per day. Nobody types it in, and it is the part prospects scroll to.
Whatever opened that incident
An HTTP check that failed twice, a Sentry or Grafana webhook, or a deploy pipeline posting through the API. All three land on the same incident.
The paging you did not see
While the page said “investigating”, an escalation policy was working through Slack, then email, until a human acknowledged. Elsewhere that starts at $29 per responder per month.
Why we give the paging away
Every other tool in this category charges for the moment that matters. The status page is cheap to host and the escalation is a database table and a ticker; per-responder pricing on a three-person team mostly convinces the third person not to be on-call. We charge for the things that genuinely cost money to run — SMS and phone calls, faster checks, extra pages — and never for the loop itself.
What you would set up
- 1. Components your customers can name — API, Web app, Billing.
- 2. A monitor on your health endpoint; two failures open the incident.
- 3. Slack now, your email in ten minutes, a co-founder in twenty-five.
- 4. Your domain, a badge in the README, and subscribers who confirmed by email.
Comparing options? What Statuspage, PagerDuty, Better Stack and UptimeRobot give you for free.