Status pages without the busywork
A status page only earns trust if it is accurate during an incident, which is exactly when you have no time to update it. So let the monitoring do it.
The hardest time to update a status page is the one time it matters: in the middle of an incident, when you are already busy fixing the real problem. So pages drift out of date, customers refresh a green screen while the API is down, and trust takes the hit.
The fix is not more discipline. It is removing the manual step.
State changes are the source of truth
In Cronaut, the one event that matters is a monitor changing state. There is no separate “post an incident” button to forget:
- Going from UP to DOWN opens an incident on its own.
- Going from DOWN to UP resolves it on its own.
- Every change streams to the public page live over SSE.
Your status page is just a view of what your monitors already know. It cannot fall out of sync, because nothing updates it by hand.
Public by design, separate by design
The status page runs as its own read-heavy service, which means it is:
- Cacheable behind a CDN, so it survives the traffic spike a real outage brings.
- Server-rendered HTML, so it stays fast and search-friendly.
- Isolated from your authed dashboard, so it is a separate security surface.
What you still control
Automation handles the mechanical part, and you keep the story. You can post a human update to an open incident, such as “we have found the cause and are deploying a fix.” You can schedule maintenance windows, and choose which monitors show up on which page. The busywork is gone, but the communication is still yours.