Prompt
What should I use for a self-hosted status page?
Latest observation
Oct 27, 2026
OpenAI APIWeb search: off
If you want a self-hosted status page, the best choice depends on whether you want something simple and ready-made or more customizable.
Good options
1. Cachet
- Best for: a polished, public-facing status page
- Pros: popular, clean UI, incident and component tracking, easy to understand
- Cons: project activity has historically been uneven, so check current maintenance status before committing
2. Statping / Statping-ng
- Best for: monitoring + status page in one tool
- Pros: uptime checks, incidents, metrics, nice dashboard
- Cons: smaller ecosystem than more established tools
3. Healthchecks.io (self-hosted)
- Best for: cron / job monitoring
- Pros: great for dead-man’s-switch style monitoring
- Cons: not really a full public status page platform
4. Uptime Kuma
- Best for: easiest self-hosted option
- Pros: very easy to deploy, supports monitors, notifications, and a public status page
- Cons: more “monitoring tool with a status page” than a dedicated status-page product
5. Better Stack / Atlassian Statuspage / Status.io
- These are not self-hosted, but worth mentioning if you decide hosted is okay.
My recommendation
- If you want the easiest self-hosted setup: Uptime Kuma
- If you want a more traditional status page with incidents/components: Cachet
- If you want monitoring + status page in one package: Statping-ng
Quick decision guide
- Small team / personal projects → Uptime Kuma
- Public SaaS status page → Cachet
- Need monitoring plus page → Statping-ng
If you want, I can also give you:
- a comparison table,
- a Docker Compose example for the best option, or
- a recommendation based on your stack and hosting setup.