The suite has four layers — the marketing site, the app you log into, the public status surface, and reference. Here's the whole map.
The pitch: cron monitoring, scheduling & uptime in one tool. Hero, how-it-works, the four check-in methods, feature grid, comparison vs AWS / healthchecks.io / Uptime Kuma, and pricing.
The command center. Fleet rollup, every monitor in one list (filter by team & tag), live WebSocket runs, incident banner, activity feed, and an SLO burn-down.
One monitor up close: a GitHub-style year heatmap of runs, latency p50/p95, client-pushed custom metrics with anomaly detection, SLO budget, run history, and alert policy.
One monitor, many reporters. Friendly aliases, a quorum rule (“≥5 healthy”), per-reporter counts & latencies, breakdowns by host/region/version, and a breach timeline.
How clients push values and see them charted — line/bar/area, heatmaps, gauges, histograms, anomaly bands — plus metadata facets and the five ways to send data.
A live, self-animating demo: a sample app's workers, crons, backups and queues wire into every cron.watch feature over HTTP, WebSocket, DNS and UDP — shown as an animated workflow, with each widget linking to the feature behind it.
Why every daemon should phone home — the case for dead-man's-switch monitoring for startups and enterprises, plus a copy-paste systemd pattern to make every daemon, cron, and worker check in.