Back to catalog
Statusnook
MITStatusnook is an open-source, self-hosted alternative to Statuspage with built-in HTTP uptime monitoring and Git-driven YAML configuration.
Open-source alternative to — compare it against:
Overview
Statusnook is a self-hosted uptime monitor and status page generator written in Go. Its Git-driven YAML synchronization allows teams to manage endpoint health checks and alert channels directly through version control. By combining an active polling scheduler with a public status portal, it removes the need to bridge external monitoring tools with separate incident dashboards.
Why Statusnook instead of Statuspage
Atlassian Statuspage acts as a decoupled communication portal, requiring external monitors or manual updates to publish incident details. Statusnook embeds automated health checks directly alongside the status board in a single Go process. Backed by SQLite and server-rendered htmx, probe execution runs at frequencies down to ten seconds with sub-millisecond local scheduling overhead, updating page state without the API hops or third-party webhooks that SaaS status pages require.
Resource efficiency and hosting boundaries mark the operational difference. Statuspage charges per team seat and per subscriber, inflating costs as notification lists grow. Statusnook runs within a lightweight container using under fifty megabytes of memory, routing alerts through SMTP or Slack without per-subscriber billing. In exchange, operators assume hosting responsibilities: running Statusnook on the same cluster as the monitored application risks taking down the status board when an infrastructure outage occurs.
What it does well
- GitOps configuration: manages monitors, mail groups, and services through a
config.yamlfile synchronized on GitHub branch pushes. - Repository secret encryption: protects sensitive webhook URLs and SMTP credentials with a built-in symmetric encryption utility before committing configuration.
- Flexible HTTP checks: executes GET and POST probes at 10, 30, or 60-second intervals with custom headers, URL forms, or JSON request bodies.
- Segmented alerting: routes internal failure alerts to engineering mail groups and Slack channels while sending subscriber notifications over SMTP.
- Minimal operational footprint: packages the scheduler, admin interface, and public portal into a single Go binary backed by embedded SQLite.
- Automatic TLS provisioning: provisions and renews Let's Encrypt certificates automatically when running as a standalone systemd service on Linux.