Healthchecks on a plan, not a meter. 50 jobs are $29 a month on Essentials with 3 seats, where Cronitor bills $2 per monitor and $5 per user. Uptime checks and your status page share the plan.
20 healthchecks free. No credit card required.
We’re on watch
Cronitor has no base fee, so a handful of jobs costs a few dollars. The bill grows by $2 with every monitor and $5 with every person, and passes $1,005 a month at 500 jobs.
Swipe to compare
| Monthly priceUSD, monthly billing, one user | HyperpingHealthchecks count as monitors | CronitorBilled per monitor and per user |
|---|---|---|
| Free plan | 20 jobsShared with uptime monitors | 5 jobsHacker, 1 user, email and Slack |
| 50 jobs | $29Essentials, $24 billed yearly | $10550 × $2, plus $5 per user |
| 50 jobs, team of 5 | $433 seats included, then $7 each | $125$5 for each of the 5 users |
| 500 jobs | $299Business, $249 billed yearly | $1,005500 × $2, plus $5 per user |
| Also in the price | Uptime monitors, status pages, on-call for monitorsWithin the same monitor count | Uptime checks, status pageBilled per monitor too |
Cronitor 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 | CronitorBusiness · $2/monitor, $5/user |
|---|---|---|
| Where Cronitor is stronger | ||
| Alerts when a run takes too long | Duration loggedFrom a /start ping, no alert on it | IncludedDuration assertions per job |
| Exit codes and job output | Not includedNot stored | IncludedExit code, stdout and stderr with CronitorCLI |
| Failure pings | Included/fail alerts at once | IncludedA fail event alerts at once |
| Run history | 15 daysLast 20 pings and a 24-hour chart | 12 monthsOn Business |
| Microsoft Teams and webhooks | Not includedNot for healthchecks, only for uptime monitors | IncludedTeams, Discord, Telegram and webhooks |
| Jobs found from your crontab | Not includedOne healthcheck per job, by hand, API or Terraform | IncludedCronitorCLI imports the crontab |
| Where Hyperping makes the difference | ||
| Pricing model | PlansHealthchecks count toward the plan’s monitors | Per monitor + per userNo base fee, billed monthly |
| 500 jobs | $299/moBusiness, 1,000 monitors and 20 seats | $1,005/moOr Enterprise, from $6,000 a year |
| People included | 3 seatsOn Essentials, 10 on Pro, 20 on Business | None$5 per user, from the first one |
| Private status page | IncludedOn Pro, password or email access codes | +$50/moPer private page, +$25 to brand one |
| 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 | Included |
| 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 Business |
| Uptime monitors in the same plan | IncludedEvery 30 seconds on paid plans, from 17 regions | IncludedBilled per monitor too |
| Status pages | IncludedOn every plan, public or private on Pro | Included1 included, private or branded as add-ons |
| MCP server for AI agents | IncludedLists each healthcheck’s next deadline | Included |
Watching a few jobs? 20 healthchecks are free.
Get started freeCronitor is a job analytics tool. It records each run’s exit code and output with CronitorCLI, alerts the moment a job reports a failure, and warns when a run takes longer than it should. Hyperping logs a run’s duration from a /start ping but never alerts on it.
It also keeps 12 months of history on Business, against 15 days of pings on Hyperping, and sends to Microsoft Teams and webhooks, which Hyperping’s healthchecks don’t. If you debug jobs from their monitor, stay.
Cronitor bills $2 per monitor and $5 per user, with no base fee: cheap for ten jobs, $1,005 a month for 500. Hyperping sells plans. Essentials is $29 a month for 50 monitors and 3 seats, Business $299 for 1,000 monitors and 20 seats, and healthchecks and uptime checks share the count.
The same plan runs your status page, public or private on Pro with no add-on, and on-call with escalation for your websites and APIs from Essentials. 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.
Cronitor goes deeper into each run. Hyperping goes wider: your jobs, websites, APIs and status page on one plan, and a bill that doesn’t move with every job you add.
If you watch more than a few dozen jobs and want uptime monitoring next to them, Hyperping costs a fraction of Cronitor. If you need exit codes and duration alerts, Cronitor is the better tool. For a wider shortlist, see the best Cronitor alternatives.
List your jobs from Cronitor’s API, recreate each one as a healthcheck, then change one line per job.
# Every job, with its schedule and grace period
curl -u "$CRONITOR_API_KEY:" \
"https://cronitor.io/api/monitors?type=job"
# Or all of them as YAML
curl -u "$CRONITOR_API_KEY:" \
"https://cronitor.io/api/monitors?format=yaml"Cronitor’s Monitor API lists every job with its schedule, time zone and grace period, and exports them all as YAML.
Cronitor’s 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 * * * cronitor exec d3x0c1 /usr/local/bin/backup.sh
# 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 cron monitoring on a plan rather than per monitor, with uptime checks and a status page in the same account. Healthchecks are on every plan, 20 free, and count toward the plan’s monitors. Healthchecks.io is the cheaper pick for cron jobs alone. The best Cronitor alternatives compares six of them.
The Hacker plan is free for 5 monitors and 1 user. Business costs $2 per monitor and $5 per user each month, with no base fee, so 50 jobs and one user are $105 a month and 500 jobs $1,005. A private status page adds $50 a month. Enterprise starts at $6,000 a year.
At list prices, from the sixth job: Cronitor’s free plan stops at 5 monitors and Hyperping’s at 20. 50 jobs are $29 a month on Hyperping Essentials with 3 seats, against $105 on Cronitor for one user, and 500 jobs are $299 on Business against $1,005. On both free plans, alerts skip SMS and PagerDuty.
Cronitor’s pricing lists hosted plans only. Hyperping is hosted too. If you need to run cron monitoring on your own servers, Healthchecks.io is open source under the BSD license: see Hyperping vs. Healthchecks.io.
No. Ping /start when a job begins and Hyperping logs how long the run took, but it alerts only when a ping doesn’t arrive by the deadline. Cronitor can alert on duration. See the healthchecks docs.
List your jobs from Cronitor’s Monitor API, which also exports them as YAML, and recreate each one as a healthcheck with the same cron expression, time zone and grace period, 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.