Statusnook

Statusnook puts a public status page and the monitoring behind it in a single binary. One install script gets an instance running with managed TLS, so a team can publish incident updates and start checking endpoints the same afternoon instead of wiring a monitoring service to a separate hosted page.

Configuration works two ways. The web interface covers everything by default, and the settings page can switch an instance to text-based configuration, where a YAML document defines general settings, mail groups, notification channels, monitors and services. That file is applied from the settings page or synchronized automatically on pushes to a chosen GitHub branch, and a rename directive exists because dropping or renaming a key is destructive.

Deployment paths are laid out for several environments.

• Standalone: one shell command with managed TLS, requiring ports 80 and 443.
• Reverse proxy: the same install behind Caddy or NGINX on a port you choose.
• Docker: a published image run directly or through a compose file with a named data volume.
• Cloud templates: one-click deployments for DigitalOcean, Vultr, Railway and Zeabur.
• Binaries: amd64 and arm64 Linux builds attached to each release.

Monitors are HTTP checks with a method, headers, body, frequency, timeout and retry count, and each one points at notification channels and mail groups. Channels can be SMTP providers such as Postmark, Amazon SES or Azure Communication Services, or a Slack webhook, and secrets inside the config file are stored encrypted. Managed subscriptions let visitors sign themselves up for updates.