Comparison
Crontap vs Healthchecks.io
Healthchecks.io is a mature heartbeat specialist with self-hosting and detailed job lifecycle signals. Crontap combines interval-based native heartbeats with HTTP scheduling and uptime. They overlap on absence detection, but only Crontap owns the clock.
At a glance
Healthchecks.io vs Crontap, side by side.
| Dimension | Healthchecks.io | Crontap |
|---|---|---|
| Fires HTTP cron jobs | No | Yes |
| Open source self-host option | Yes | No (hosted SaaS) |
| Cron expression on check | Yes (monitor side) | Yes (scheduler side) |
| Free tier | 20 checks | Starter: 2 combined items; schedules hourly+, 1 uptime monitor daily, and 1 heartbeat hourly |
| Paid entry (as of 2026) | Tiered per check count | from $2.99/mo on Pro |
| Human Notifications | Email plus broad native chat, SMS/WhatsApp, phone, and incident integrations by plan | All plans: email, test sends, product defaults, per-item default/custom/off routing, and delivery history. Pro, Ultra, and legacy Pro add Slack, Discord, and Telegram |
| Machine webhook Integrations | Management API, ping API, webhooks, and self-hosting | Separate machine webhook Integrations with per-event success, failure, missed, and recovered levers where applicable |
| Schedule failure batching | Not compared; Crontap schedule-specific alert setting | Schedule alerts: unsaved default Starter 24h / 3 failures, paid 10m / 3; configurable floor Starter 1 day, paid 1 minute |
| Heartbeat / dead-man monitoring | Period, cron, or systemd OnCalendar with timezone, grace, start, fail, duration, and logs | Native: period + grace, /fail, missed/recovered/explicit-failure alerts, ping URL, and 90-day history |
| Uptime monitoring | No active uptime-monitor product | Native HTTP uptime: down/recovered alerts, history, 90-day rollups, and integration controls |
| Retries and customization | Monitors external jobs; does not rerun them | Default on: 3 retries with 2× exponential backoff and jitter. Pro, Ultra, and legacy Pro: 1–5 retries plus delay and retry outcomes; alert after exhaustion |
How they work
The two approaches in one paragraph each.
Healthchecks.io
Healthchecks.io gives each job a ping URL and supports simple period, cron, or systemd OnCalendar expectations with timezone and grace. Start, success, fail, duration, request-body or email logs, filtering, native notifications, Management API, and self-hosting make it a deep dead-man specialist. It does not schedule or run the job.
Crontap
Crontap calls HTTP endpoints on cron cadence and also receives native heartbeat pings from jobs that run anywhere. Heartbeats support period plus grace, /fail, connected notification channels, generic webhook Integrations, and 90-day history. Misses are detected within one minute after grace; notification delivery follows asynchronously.
Where each side wins
Honest broker, both columns.
Healthchecks.io wins on
- Open-source edition you can self-host.
- Cron-expression expectations as well as simple periods.
- /start plus duration tracking, /fail, and separate log signals.
- 20 free checks and a broad paging integration list.
- Management API and a mature open-source self-hosted deployment.
Crontap wins on
- Scheduler included: Healthchecks listens; Crontap fires.
- From $2.99/mo on Pro, scaling as you grow.
- Per-run HTTP logs.
- Uptime monitoring in the same dashboard as cron.
- No second vendor when interval-based heartbeat monitoring is enough.
The math
Cadence and pricing, worked out.
- Healthchecks.io Hobbyist covers 20 checks for free. Crontap Starter includes 2 combined schedules, uptime monitors, and heartbeats; Pro starts at $2.99/mo.
- Using both buys operational independence and deeper Healthchecks lifecycle signals. Using Crontap alone removes a second vendor when period plus grace and /fail are enough.
Moving from Healthchecks.io
The migration, in 4 steps.
- Keep Healthchecks checks that only monitor external schedulers you are not moving yet.
- Move HTTP firing to Crontap schedules with matching cron and timezone.
- Create matching Crontap heartbeats and send both ping URLs during a parallel window.
- Drop Healthchecks only when Crontap's interval-based heartbeat model and shared failure domain fit your risk tolerance.
Decision
Which one fits.
Pick Healthchecks.io if
You want self-hosting, cron-expression expectations, or start and duration tracking today.
Pick Crontap if
You want scheduler plus heartbeats plus uptime on one bill.
Pair both if
The scheduler and alerter must live in separate systems.
FAQ
Crontap vs Healthchecks.io, in detail.
- Should I replace Healthchecks with Crontap?
- Replace it when period plus grace, /fail, connected notification channels, generic webhook Integrations, and 90-day history cover the job. Keep Healthchecks for self-hosting, cron schedules, /start duration tracking, log signals, or an independent failure domain.
- Where is the pairing guide?
- See Pair Crontap with Healthchecks.io for end-to-end monitoring on the Crontap blog.
Sources
Ready to fix it?
Point Crontap at any URL. Pick any cron. Done.
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
Free forever tier ・ No credit card required
/wp-cron.php?doing_wp_cron=1
Schedule
"every 5 minutes"
Next
in 23s