Sentry includes one cron monitor, then bills $0.78 for each one on top of the plan. On Hyperping, healthchecks count toward the plan’s monitors: 50 for $29 a month, uptime checks and a status page included.
20 healthchecks free. No credit card required.
We’re on watch
Sentry’s plans include one cron monitor. Each other one is $0.78 a month on pay-as-you-go, on top of the Team plan at $29, so 500 jobs come to $418.22 a month.
Swipe to compare
| Monthly priceUSD, monthly billing, one user | HyperpingHealthchecks count as monitors | Sentry CronsTeam plan, then per monitor |
|---|---|---|
| Free plan | 20 jobsShared with uptime monitors | 1 jobDeveloper, 1 user, email alerts |
| 50 jobs | $29Essentials, $24 billed yearly | $67.22Team $29, plus 49 × $0.78 |
| 500 jobs | $299Business, $249 billed yearly | $418.22Team $29, plus 499 × $0.78 |
| Also in the price | Uptime monitors, status pages, on-call for monitorsWithin the same monitor count | Error monitoring and tracingTeam plan, unlimited users |
Sentry Crons 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 | Sentry CronsTeam · $29/mo, $0.78/monitor |
|---|---|---|
| Where Sentry Crons is stronger | ||
| Errors linked to the run | Not includedHealthchecks see pings, not errors | IncludedErrors raised during a job show on its monitor |
| Alerts when a run takes too long | Duration loggedFrom a /start ping, no alert on it | IncludedMaximum runtime per monitor |
| Failure pings | Included/fail alerts at once | IncludedAn error check-in alerts at once |
| Alert only after several misses | Not includedOne alert per missed run | IncludedFailure and recovery thresholds |
| Microsoft Teams and webhooks | Not includedNot for healthchecks, only for uptime monitors | IncludedTeams, Discord and webhooks on paid plans |
| Users | 3 seatsOn Essentials, then $7 each | UnlimitedOn Team and Business |
| Where Hyperping makes the difference | ||
| Pricing model | PlansHealthchecks count toward the plan’s monitors | Per monitor$0.78 each after the first, on top of the plan |
| Free plan | 20 healthchecksShared with uptime monitors | 1 monitorEmail alerts only |
| SMS alerts | IncludedFrom the plan’s credits, from Essentials | Not included |
| Status pages | IncludedOn every plan, public or private on Pro | 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 | IncludedCrontab or interval schedules |
| Start pings and run duration | IncludedPing /start, then the URL | Includedin_progress, then ok |
| Grace period | Included1 minute or more, 10 by default | IncludedCheck-in margin |
| Slack, PagerDuty and Opsgenie alerts | IncludedPagerDuty and Opsgenie from Essentials | IncludedOn paid plans |
| API | IncludedHealthchecks API, hyperping_healthcheck resource and MCP | IncludedCrons API |
Watching a few jobs? 20 healthchecks are free.
Get started freeIf your team already lives in Sentry, its cron monitors sit where you debug. A run that fails opens an issue, the errors the job raised show on its monitor, and you can alert when a run exceeds its maximum runtime or only after several misses in a row.
A handful of monitors costs little on a plan you already pay for, users are unlimited on Team, and alerts reach Microsoft Teams and webhooks, which Hyperping’s healthchecks don’t.
Sentry counts cron monitors one by one: $0.78 each past the first, so 50 jobs are $67.22 a month with the Team plan and 500 are $418.22. On Hyperping, healthchecks count toward the plan’s monitors: 50 on Essentials for $29, 1,000 on Business for $299.
The same plan checks your websites and APIs from 17 regions, runs a status page your users can read, sends SMS from the plan’s credits, and pages on-call for uptime monitors 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.
Keep Sentry Crons for the jobs you debug in Sentry. Move the rest when the per-monitor line grows, or when you also need a status page, which Sentry doesn’t run.
Past a few dozen jobs, one Hyperping plan costs less than Sentry’s monitors alone, with uptime monitoring and a status page included. Every tool side by side: the best cron job monitoring tools.
List your monitors from Sentry’s API, recreate each one as a healthcheck, then change one line per job.
# Every cron monitor of the organization
curl -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" \
"https://sentry.io/api/0/organizations/acme/monitors/"Sentry’s Crons API lists every monitor of the organization with its schedule, time zone and check-in margin, page by page.
Sentry’s Crons 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 "$SENTRY_CRONS?status=ok"
# 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 that isn’t billed per monitor, next to uptime checks and a status page. Each job pings its own URL, on a cron expression with a time zone and a grace period, and 20 healthchecks are free. Cronitor and Healthchecks.io are the other dedicated tools: see the best cron job monitoring tools.
Every Sentry plan includes one cron monitor. Each other one is $0.78 a month on pay-as-you-go, which only paid plans have: on Team, at $29 a month or $26 billed yearly, 50 monitors come to $67.22 a month and 500 to $418.22.
For one monitor. The free Developer plan includes one cron monitor, one user and email alerts, with no pay-as-you-go. Hyperping’s free plan includes 20 healthchecks, shared with uptime monitors, and a status page.
Yes. A Hyperping healthcheck needs no SDK: the job calls its ping URL with curl or any HTTP client when it finishes, and /start when it begins if you want its duration. See the healthchecks docs.
List your monitors from Sentry’s Crons API with an auth token: each one comes with its schedule, time zone and check-in margin. Recreate them as healthchecks by hand, with the healthchecks API or with Terraform, then replace each job’s check-in with its ping URL and keep both for a few runs.