Statusnook

Statusnook publishes a public status page with a service health summary and an incident and maintenance timeline, plus opt-in visitor updates over email and Slack.[1]

Monitors are customizable with HTTP method, request headers, request body, check frequency, timeout, and retry attempts, and each monitor assigns its own notification channels and mail groups.[1][2]

Alerting runs on two tracks: private monitor alerts to the team and public status broadcasts to page visitors, using Slack notifications and SMTP email through providers such as Azure, Postmark, and SES.[1][2]

Configuration works through the web UI, exclusively text-based YAML, or automatic sync on pushes to a chosen GitHub branch, with secrets encryptable from the settings page.[1][2]

Teams that want status communication and endpoint monitoring on their own server, including a low-cost VPS or dedicated machine, without paying for a hosted status page subscription.[1]

Operators comfortable with a single-command install, automatic HTTPS with renewal, in-app upgrades, and official Docker images or one-click templates for DigitalOcean, Vultr, Railway, and Zeabur.[1][2]

No single sign-on support is documented on the official site, README, or configuration docs, so teams that require SSO should verify before adopting.[1][2][3]

There is no vendor-operated hosted edition; one-click templates deploy the self-hosted build into the user's own cloud account, so operating responsibility stays with the adopter.[1][2]

No enterprise support plan or SLA is documented, and no public REST or API surface for operating Statusnook was found in the README or configuration docs.[1][2][3]

Repository health signals such as star history, commit recency, and release cadence were observed only as page text during research and still await the platform's worker verification.[1]