Healthchecks.io costs less for cron jobs alone. Hyperping is worth it when the same plan also checks your websites and APIs, runs your status page and pages on-call when a site goes down. 20 healthchecks are free.
20 healthchecks free. No credit card required.
We’re on watch
For cron jobs alone, Healthchecks.io is the cheaper tool: $20 a month for 100 jobs, $80 for 1,000. On Hyperping, the same plan also covers uptime monitors, a status page and on-call for them, in the same monitor count.
Swipe to compare
| Monthly priceUSD, monthly billing, one user | HyperpingHealthchecks count as monitors | Healthchecks.ioCron monitoring, open source |
|---|---|---|
| Free plan | 20 jobsShared with uptime monitors | 20 jobsHobbyist |
| 50 jobs | $29Essentials, $24 billed yearly | $20Business, up to 100 jobs, $16 billed yearly |
| 500 jobs | $299Business, $249 billed yearly | $80Business Plus, up to 1,000 jobs, $64 billed yearly |
| Also in the price | Uptime monitors, status pages, on-call for monitorsWithin the same monitor count | Cron monitoring onlyOpen source, free to self-host |
Healthchecks.io prices read on its pricing page on , in USD at monthly billing. Hyperping’s are on pricing: healthchecks come with every plan and count toward its monitors.
Swipe to compare
| Cron job monitoringUSD list prices |  Healthchecks on every plan | Healthchecks.ioBusiness · $20/mo for 100 jobs |
|---|---|---|
| Where Healthchecks.io is stronger | ||
| Price per job | $29/mo50 monitors on Essentials | $20/mo100 jobs on Business |
| Open source and self-hosting | Not includedHosted only | IncludedBSD license, run it on your own servers |
| Exit codes and job output | Not includedNot stored | IncludedExit status and the first 100 kB of the ping body |
| Failure pings | Included/fail alerts at once | Included/fail or a non-zero exit status alerts at once |
| Microsoft Teams and webhooks | Not includedNot for healthchecks, only for uptime monitors | IncludedAbout 25 integrations, Signal and ntfy too |
| Phone call alerts for missed jobs | Not includedRoute healthchecks to PagerDuty or Opsgenie | Included20 calls a month on Business |
| Free for open source | Free plan20 monitors and a status page | IncludedBusiness plan for open source and nonprofits |
| Where Hyperping makes the difference | ||
| Uptime monitors in the same plan | IncludedEvery 30 seconds on paid plans, from 17 regions | Not includedCron and heartbeat checks only |
| Status pages | IncludedOn every plan, public or private on Pro | BadgesStatus badges, no status page |
| Cron jobs on your status page | IncludedShow a job’s state to your users | Not included |
| On-call and escalation for uptime monitors | IncludedFrom Essentials. Healthchecks alert every channel at once | Not includedHanded to PagerDuty or Opsgenie |
| What both do | ||
| Cron expressions with a time zone | IncludedOr every N minutes, hours or days | IncludedOr systemd OnCalendar |
| Start pings and run duration | IncludedPing /start, then the URL | Included |
| Email, SMS, Slack, PagerDuty and Opsgenie alerts | IncludedAll at once. SMS, PagerDuty and Opsgenie from Essentials | IncludedSMS, PagerDuty and Opsgenie on paid plans |
| Grace period | Included1 minute or more, 10 by default | Included |
| API | IncludedHealthchecks API, hyperping_healthcheck resource and MCP | IncludedManagement API v3 |
Watching a few jobs? 20 healthchecks are free.
Get started freeIf cron jobs are all you monitor, Healthchecks.io costs less: $20 a month for 100 jobs, $80 for 1,000, and nothing at all if you run its open source code yourself. Open source projects and nonprofits get its Business plan free.
It also does more with each ping. A job can report its exit status, attach the first 100 kB of its output, and alert by phone call, WhatsApp, Microsoft Teams or webhook, which Hyperping’s healthchecks don’t.
Healthchecks.io watches jobs. The site those jobs serve, the API behind it and the page that tells your users what is down need other tools and other bills. On Hyperping they share one plan: Essentials is $29 a month for 50 monitors, healthchecks and uptime checks together, a status page on your domain and 3 seats.
Uptime monitors page whoever is on call and escalate when nobody answers, from Essentials, and a job’s healthcheck can sit on your status page next to them. See cron job monitoring for how healthchecks work.
A missed run alerts email and SMS to the project’s members, Slack, Discord, Telegram, PagerDuty and Opsgenie, all at once, and the next ping sends the recovery. Healthchecks have no escalation policy, on-call schedule, Teams, webhook or phone call: those belong to uptime monitors. To page whoever is on call for a job, route it to PagerDuty or Opsgenie.
Hyperping stores neither exit codes nor job output. A /start ping logs how long a run took, the dashboard keeps the last 20 pings and a 24-hour chart, and pings are kept for 15 days. Everything is in the healthchecks docs.
Healthchecks.io is the better cron monitor for the price, and the only one here you can host yourself. Hyperping is the better fit when cron jobs are one part of what you watch.
If you already pay for an uptime monitor and a status page next to Healthchecks.io, Hyperping replaces all three with one plan. For a wider shortlist, see the Healthchecks.io alternatives.
List your checks from the Healthchecks.io API, recreate each one as a healthcheck, then change one line per job.
# Every check of the project, with schedule, tz and grace
curl -H "X-Api-Key: $HC_API_KEY" \
"https://healthchecks.io/api/v3/checks/"The Management API lists every check of a project with its cron expression or period, time zone and grace time, from one read-only API key.
Healthchecks.io API docsresource "hyperping_healthcheck" "nightly_backup" {
name = "Nightly database backup"
cron = "0 2 * * *"
timezone = "Europe/Paris"
grace_period_value = 30
grace_period_type = "minutes"
}
output "backup_ping_url" {
value = hyperping_healthcheck.nightly_backup.ping_url
sensitive = true
}Declare one hyperping_healthcheck per job, with its cron expression, time zone and grace period, and output its ping URL. The healthchecks API and the dashboard do the same.
Terraform provider# Before
0 2 * * * /usr/local/bin/backup.sh && curl -fsS -m 10 --retry 5 https://hc-ping.com/0f6a1c2e-…
# After: the backup pings Hyperping when it succeeds
0 2 * * * /usr/local/bin/backup.sh && curl -fsS --retry 3 https://hc.hyperping.io/tok_8f3kq2Lm9xV4Point each job at its healthcheck’s ping URL and run both for a few days. Ping /start when the job begins to log how long each run takes. When the alerts match, remove the old check-in.
Read the healthchecks docsHyperping, if you want your cron jobs next to uptime monitors and a status page. Healthchecks work the same way, one ping URL per job with a cron expression, a time zone and a grace period, and 20 are free. Uptime Kuma is the self-hosted pick. The Healthchecks.io alternatives compares them.
Hobbyist is free for 20 jobs. Business is $20 a month for 100 jobs, $16 billed yearly, with 50 SMS or WhatsApp messages and 20 phone calls. Business Plus is $80 a month for 1,000 jobs, $64 billed yearly. Open source projects and nonprofits get Business free.
Yes, for 20 jobs on the hosted Hobbyist plan, and without limit if you self-host its open source code. Hyperping’s free plan also has 20 monitors, healthchecks and uptime checks together, and a status page.
No. It offers status badges you can embed, in SVG, JSON or Shields.io format. Hyperping has a status page on every plan, on your own domain from Essentials, and can show a healthcheck on it. See status pages.
Healthchecks.io waits for your jobs to ping it. Uptime Kuma checks your sites from the server you install it on, and also takes push heartbeats. Both are open source. Hyperping does both as a hosted service, checking sites from 17 regions so a problem on one server doesn’t hide an outage.
List your checks from the Healthchecks.io Management API with a project’s API key: each one comes with its schedule, time zone and grace period. Recreate them as healthchecks by hand, with the healthchecks API or with Terraform, then point each job at its new ping URL and keep both for a few runs.