BetterStatusPage: self-hosted monitoring + status page in one container (SQLite, OIDC SSO, YAML config)

At work we needed a status page. We looked around and none of the free tools covered everything we needed, CAS login in particular, which we still use for a few internal services. So the topic died, as these things do. I decided to build a small thing at home as a hobby project: HTTP monitors, CAS login and email alerts. It grew into something much bigger.

That's BetterStatusPage, a free, MIT-licensed monitoring tool with a public or private status page, built for self-hosting. The current version is v0.4.0 and it's under active development.

\- GitHub: https://github.com/BElluu/BetterStatusPage

\- Docs: https://docs.betterstatuspage.dev

\- Overview and a 5-minute live demo with test data (each visitor gets their own instance): https://betterstatuspage.dev

Setup

A single Node.js process on SQLite, so there's no separate database server, Redis or queue to run next to it. Docker Compose or a one-liner install script.

What it does

\- 9 monitor types: HTTPS (keyword, JSON path and header checks, slow-response threshold, Basic/OAuth2/CAS auth, TLS expiry warnings), ping/TCP, DNS, SQL Server, PostgreSQL, MySQL/MariaDB and MongoDB query monitors, Docker containers, passive heartbeat

\- Alerts to email, Slack, Teams, Discord, Telegram, ntfy, Pushover and webhooks, with failure thresholds, quiet hours and digests

\- Monitor dependencies so you get one root-cause alert instead of a pile of them

\- Actions: fire an HTTP request when a monitor stays down or recovers (e.g. trigger a failover job in Jenkins)

\- Status page: drag-and-drop builder (custom CSS optional), incidents (a monitor can open a draft incident by itself), maintenance windows, uptime reports with CSV export, subscriptions via email, RSS/Atom and JSON API

\- Private status pages with OIDC SSO (Entra ID, Keycloak, Okta, Google, Authentik, Auth0)

\- Ops and security: monitors, channels and actions as YAML, API tokens for CI/CD, Prometheus metrics, AES-256-GCM credential vault (or HashiCorp Vault), TOTP 2FA, audit log, built-in backup/restore

The full list is in the docs.

Feedback I'd like

What are you using today, and what would stop you from switching? Any feedback and testing is very welcome, and thanks in advance to everyone who gives it a try!

PS:
The demo runs on my small server, which has limited resources. If you are unable to launch it at a given moment, it means there are currently too many active instances. Please wait 5 minutes and try again :)

https://redd.it/1x7i007
@r_SelfHosted