Compare / Healthchecks vs Uptime Kuma
Healthchecks vs Uptime Kuma
Pick Healthchecks if you want the published Cronitor stack (cron heartbeats). Pick Uptime Kuma if you want MIT HTTP/TCP uptime.
Facts checked 25 Oct 2026. License, language, and GitHub activity come from the catalog or the project's own repo. "Not in the catalog row" means the public catalog dump does not store that number.
Healthchecks in the catalog Uptime Kuma in the catalog Start on Railway
How they compare
| Healthchecks | Uptime Kuma | |
|---|---|---|
| License | BSD-3-Clause (catalog) source | MIT (catalog) source |
| Language | Python (catalog) | JavaScript (catalog) |
| GitHub activity | 10,451 stars in the catalog; last push 22 Oct 2026 source | 92,564 stars in the catalog source |
| Self-host | Published as /stacks/healthchecks-cron. Django plus Postgres. | Same monitoring family. HTTP/TCP checks and a status page. |
| Best for | The published Cronitor replacement. | HTTP uptime if a cron ping is not the job. |
Self-hosting and resource needs
Healthchecks is the published Cronitor lander — /stacks/healthchecks-cron. Uptime Kuma is already on /stacks/checkcle-monitoring and /compare/checkcle-vs-uptime-kuma. Checkcle stays the published StatusCake / Pingdom path. Neither has a one-click c17 Railway template.
FAQ
- Is this StatusCake?
- HTTP uptime stays on /replace/statuscake (Checkcle). Uptime Kuma is the sibling, not the published StatusCake path.
- Where is Checkcle?
- /compare/checkcle-vs-uptime-kuma and /replace/pingdom.
- Are these free?
- Healthchecks is BSD-3-Clause. Uptime Kuma is MIT. You pay hosting.
- How do I deploy Healthchecks?
- Open /stacks/healthchecks-cron. Persist Postgres. Point one cron job at the ping URL.
Related pages
Stack of the Week
Get one stack a week that replaces a SaaS bill.