Uptime monitor for websites, ports, DNS, certificates and cron jobs, with Telegram alerts and public status pages
- Deploy
- One-click
- License
- MIT
- GitHub stars
- 29 stars
- Last commit
Self-hosted alternatives to Cronitor
Cronitor is a hosted monitoring service for cron jobs, heartbeats, websites and APIs, with status pages and alert integrations. One listed app does its main job and runs in your own Cloudflare account.
Each answer comes from the app’s README and source code, compared with the features Cronitor describes on its own site.
Cronitor features, app by app
| Feature | Uptime Guard |
|---|---|
| Heartbeat monitoring that alerts when a scheduled job never checks in | Yes |
| Run, complete and fail telemetry with duration | No |
| Schedule assertions for expected run times | Partly |
| Slow job alerts from duration thresholds | No |
| Captured stdout and stderr for each run | No |
| Uptime checks for websites and APIs from 12+ locations | Partly |
| Public and private status pages | Partly |
| Alerts to Slack, PagerDuty, email, SMS, Teams, Telegram and webhooks | Partly |
Uptime monitor for websites, ports, DNS, certificates and cron jobs, with Telegram alerts and public status pages
- What a Cronitor user would miss
- It has no run telemetry, slow job alerts and output capture, and covers cron expression schedules, multi-location checks, a full status page and email/SMS/Slack alerts only in part.
- What it adds
- It also has owner login that needs a password plus an authenticator code and data that stays in your Cloudflare account.
- Yes Heartbeat monitoring that alerts when a scheduled job never checks in. Each heartbeat monitor has its own /ping/<token> URL that any HTTP method can call.
- No Run, complete and fail telemetry with duration. A ping only marks the job alive; no start or fail signal and no run time.
- Partly Schedule assertions for expected run times. A repeat interval you choose plus a grace window; no cron expressions.
- No Slow job alerts from duration thresholds. No run time or slow job alerts.
- No Captured stdout and stderr for each run. No output capture; a ping carries no body.
- Partly Uptime checks for websites and APIs from 12+ locations. HTTP, TCP, DNS and certificate checks every minute at best; no multi-location checks.
- Partly Public and private status pages. Read-only public status page per project; no incident posts.
- Partly Alerts to Slack, PagerDuty, email, SMS, Teams, Telegram and webhooks. Telegram and Web Push only; no email, SMS, Slack or webhook.
Sources:github.com/calmray-solutions/uptime-guard#readmegithub.com/calmray-solutions/uptime-guard/blob/main/worker/src/checks.ts