Single-binary monitoring

Curl the binary. Run it. Start monitoring.

updu ships the UI, API, scheduler, auth, and SQLite together. Grab the release that matches your box, make it executable, and open http://localhost:3000.

Jump to binary quick start View on GitHub
Binary quick start One pasted shell command gets the server running.
No Docker
Linux AMD64 default 
curl -fsSLO https://github.com/nwpeckham88/updu/releases/download/v0.5.1/updu-linux-amd64 \
  && chmod +x updu-linux-amd64 \
  && ./updu-linux-amd64

Default shown: Linux AMD64. The quick start below lets you switch architecture and opt into the OIDC build when you need it.

Stable v0.5.1 Single binary Embedded SvelteKit SPA SQLite Pi Zero to cloud VM
Coverage
15 monitor types
Alerting
5 notification channels
Response
Incidents and maintenance windows
Sharing
Public status pages
Deploy
One binary with embedded UI
What ships inside One deployable
15 monitor types HTTP, TCP, DNS, SSL, SSH, databases, WebSocket, SMTP, UDP, and push/heartbeat checks.
Operator loop included Incidents, maintenance windows, alerts, and status pages stay inside the same deployable.
No runtime sprawl Embedded frontend, Go API, SSE updates, and SQLite all ship together.
Observe /healthz, Prometheus metrics, and the live dashboard are already in the binary.
Declare GitOps YAML config stays available when you want reproducible monitor definitions.
Scale Runs on tiny hardware, but still exposes the operational hooks you expect in production.

What It Does

Small surface area, broad enough coverage.

The landing page does not need to be the full manual. The useful point is simpler: one binary covers the usual surfaces, the response loop, and the operator-facing outputs.

01

Watch the stack users feel

Keep the external surfaces visible first, then drill into the infra behind them.

  • HTTP
  • JSON API
  • WebSocket
  • TCP
  • Ping
  • DNS
  • SSL
02

Watch the dependencies underneath

Database, cache, mail, and remote access checks stay in the same tool instead of being spread around.

  • SSH
  • UDP
  • SMTP
  • Redis
  • PostgreSQL
  • MySQL
  • MongoDB
03

Handle the operator loop too

The runtime surface stays narrow even though the operator workflow is broader than basic checks.

  • Push / Heartbeat
  • Incidents
  • Maintenance
  • Status Pages
  • Webhook / Slack / Discord
  • Email / Ntfy
  • GitOps YAML

Quick Start

Quick start is just the binary.

Pick your architecture, paste the command, and open http://localhost:3000. Everything else can stay in the docs instead of stretching the landing page.

Current stable release v0.5.1

Linux AMD64 is shown by default. Switch architecture on the right, or enable the OIDC build if you need single sign-on support.

View release notes
After launch

Open http://localhost:3000 and register your admin account.

If you need a different deployment path later, use the docs instead of the quick-start block here.

Binary quick start

Enable this only if you want the release that includes OpenID Connect / single sign-on support.

The command stays pinned to the current stable release line.

Binary 
curl -fsSLO https://github.com/nwpeckham88/updu/releases/download/v0.5.1/updu-linux-amd64 \
  && chmod +x updu-linux-amd64 \
  && ./updu-linux-amd64

Paste it, let the binary start, then open http://localhost:3000.