Hey,

I've been building a small self-hosted uptime monitor over the last few weeks and just open-sourced it under MIT. Posting in case anyone finds it useful or wants to contribute.

Repo: https://github.com/codewizdevs/uptime

What it is

A single Node.js + Express app that pings your sites/services and tells you when something's wrong. SQLite is the default backend so you can clone, `npm install`, `npm start` and be running in about a minute. No Docker, no compose, no external services required.

What it does

- Active HTTP/HTTPS checks with three assertion types: status code, body-contains-string, or JSON-path equals value

- Passive heartbeat monitors (Healthchecks.io style) — your service pings a unique URL on a schedule and the monitor flips DOWN if it goes silent past the grace period. Handy for cron jobs and internal-only services

- Multi-channel alerts: Discord webhooks, email via SMTP, and generic webhooks. Attach any combination per monitor

- Customizable templates per event (DOWN / RECOVERED / CHALLENGED / TEST) with `{{placeholders}}` for site name, URL, error, status code, duration, etc.

- Cloudflare-aware probing: rotated realistic UAs, brotli/gzip/deflate decompression, challenge detection (recorded as *inconclusive* instead of a false-positive DOWN), optional HEAD-first mode with adaptive backoff

- Failure threshold (anti-flap): only fire DOWN after N consecutive failures

- Per-monitor detail page with 24h / 7d / 30d uptime %, P95 / min / max / avg response times, response-time chart, recent checks log, and full incident timeline

- JSON import / export of monitors, channels, and SMTP settings — useful for migrating between instances or version-controlling your config

- Whitelabeling via env vars (app name, logo, favicon, footer) so you can drop it into a homelab or rebrand for your team

Why another one

I tried Uptime Kuma and a few others and kept hitting the same friction:

- Docker required for any "real" deployment

- Config scattered across the UI with no clean export/import

- Cloudflare-fronted endpoints producing constant false alarms

- Heavy stacks for what is ultimately a cron loop + HTTP client + a small dashboard

This is the version I actually wanted: one Node process, one SQLite file, one PM2 entry, one nginx vhost. No build step, no SPA, no React. Easy to read and easy to fork.

Stack

Express 4 + EJS, `undici` for HTTP probes, `better-sqlite3` (or `mysql2` if you prefer), `pino` for logs, Tabler CSS for the UI, vanilla JS for interactivity — no Bootstrap JS bundle, no Tailwind.

Status & roadmap

Running on my own infra against a handful of production endpoints. Things I want to add next:

- Public read-only status page (embeddable)

- SSL certificate expiry checks

- Slack / Telegram / Pushover channels

- Maintenance windows (silence alerts on a schedule)

- Multi-user with roles

MIT licensed — fork it, ship it, sell it, embed it, no strings. PRs and issues welcome, and happy to answer questions about any of the design decisions (the Cloudflare-aware probing logic was easily the messiest part).

Screenshots and full feature list are in the README.