Self-hosted uptime monitoring — one binary, no Docker

Run the whole of PulZone from a single static binary. No Docker, no Node, no database server, no Redis. Uncapped, because the limit is your hardware.

The install

curl -L https://pulzone.com/dl/linux-amd64 -o pulzone
chmod +x pulzone
./pulzone

That is the entire procedure. The binary embeds its own assets and uses SQLite by default; point it at Postgres when you outgrow that.

What you do not need

No Docker daemon. No docker-compose.yml to keep merged with upstream. No Node toolchain. No Redis. No reverse-proxy requirement — though put one in front if you want.

What "uncapped" means

Self-hosted has no monitor, seat or interval limits, because there is nobody to bill. The constraint is the box you put it on.

Coming from Uptime Kuma?

Same freedom, without the container maintenance. See PulZone vs Uptime Kuma.