A public page showing green/red boxes per service, with an incident log underneath, is a small CRUD app with a nice layout. The hard problem (actually detecting the outage) belongs to your monitoring tool, not this page.
VIBE SCORE 95/100
The parts this build actually needs, each rated on its own — the average is the Vibe Score above.
| Landing page | 99 |
| CRUD database | 95 |
| Email notifications | 91 |
Don't feel like building it? These are already made, open-source, and free.
Build it. A public page showing green/red boxes per service, with an incident log underneath, is a small CRUD app with a nice layout. The hard problem (actually detecting the outage) belongs to your monitoring tool, not this page.
Statuspage costs $29/mo (about $348/yr) as of 2026-08. That's what a working rebuild would save you.
Automatically flipping a component's status based on your actual monitoring (rather than manual updates) needs an integration with whatever you use for uptime checks Historical uptime graphs per component compound over time and need a bit of data retention thought Their status-page-as-a-service reliability (staying up even when your main product is down) matters more than it sounds — don't host it on the same infrastructure you're reporting on
Yes — Cachet, Uptime Kuma are open-source options worth trying before you build your own. Details are in the standard parts section on this page.