Comparison
Crontap vs Cronhub
Cronhub closed on June 30, 2026, when its schedules, monitors, and ping history were deleted. Crontap now covers both former Cronhub surfaces: HTTP scheduling and native heartbeat monitoring.
At a glance
Cronhub vs Crontap, side by side.
| Dimension | Cronhub | Crontap |
|---|---|---|
| Status | Closed June 30, 2026 | Active, GA |
| Scheduling availability | Unavailable since June 30, 2026 | 1 minute (Pro) |
| Free tier | Closed; historical plan details omitted | Starter: 2 combined items; schedules hourly+, 1 uptime monitor daily, and 1 heartbeat hourly |
| Human Notifications | Historically email, Slack, SMS, PagerDuty, and webhooks; service is closed | 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 | Historically webhooks; service is closed | 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 | Previously available; stopped June 30, 2026 | Native: period + grace, /fail, missed/recovered/explicit-failure alerts, ping URL, and 90-day history |
| Uptime monitoring | No active product; service is closed | Native HTTP uptime: down/recovered alerts, history, 90-day rollups, and integration controls |
| Retries and customization | No active product; historical retry details not asserted | 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.
Cronhub
Cronhub formerly bundled HTTP scheduling and heartbeat monitoring. It stopped paid subscriptions in May 2026 and shut down schedules, monitors, and stored history on June 30, 2026. Exact historical limits and pricing are intentionally not used as migration promises.
Crontap
Crontap combines HTTP scheduling, Uptime monitors, and native Heartbeats. Heartbeats expect a success ping within period plus grace, accept /fail, retain 90 days of history, and alert through connected notification channels. Generic webhooks remain separate Integrations. Detection happens within one minute after grace; notification delivery follows asynchronously.
Where each side wins
Honest broker, both columns.
Cronhub wins on
- First-class PagerDuty integration in the alert panel.
- SMS as a built-in alert channel. Crontap does not provide SMS.
- Single dashboard for both Scheduler and Monitoring products (until June 30, 2026).
- Familiar UI for teams who have been on Cronhub for years.
Crontap wins on
- An active service. Crontap is GA and shipping; Cronhub closed on June 30, 2026.
- Starter includes 2 combined items, with one daily uptime monitor and one hourly heartbeat within that cap.
- Default-on retries use 2× exponential backoff with jitter and alert only after attempts are exhausted.
- Crontap Pro starts at $2.99/mo with one-minute schedules, uptime, and heartbeats.
- Starter includes email Notifications; Pro, Ultra, and legacy Pro add Slack, Discord, and Telegram. Generic webhook Integrations stay separate.
- Native heartbeats for silent jobs, so Cronhub Monitoring migrations no longer require a second vendor.
The math
Cadence and pricing, worked out.
- Historical Cronhub prices are omitted because the service is closed and the archived public material is not a reliable current quote.
- Former Cronhub customers who need minute cadence can start at $2.99/mo on Crontap Pro, which scales as usage grows.
- If you only used Cronhub Monitoring, create a Crontap heartbeat and swap the old ping URL. Starter supports one heartbeat at hourly cadence or slower.
Moving from Cronhub
The migration, in 8 steps.
- Sign up at crontap.com (no credit card on the free tier).
- For each Cronhub schedule, click New schedule in Crontap and paste the URL, HTTP method, headers, and body unchanged.
- Recreate the cadence from your saved Cronhub configuration and verify Crontap's next-fire preview.
- Set the intended IANA timezone from your own saved configuration rather than assuming a historical Cronhub default.
- Press Perform test. A 200 in the run log means you are done; a 401 means a header did not match; a 5xx means the route itself failed.
- For each Cronhub heartbeat monitor, create a Crontap Heartbeat with the same interval and grace, then replace the old ping URL in the job.
- Confirm the first successful run or heartbeat in Crontap, then remove the closed Cronhub endpoint from your code and saved configuration.
- Read the full click-by-click walkthrough in the Crontap blog (linked below) for header copying, body migration, and the absence-detection patterns.
Decision
Which one fits.
Pick Cronhub if
You cannot pick Cronhub for a new deployment because the service is closed. This column is retained for historical migration reference.
Pick Crontap if
You want one active product for Cronhub-style HTTP scheduling, uptime, and native heartbeat monitoring.
Pair both if
You want Crontap to schedule the job while a separate heartbeat receiver remains an independent failure domain.
FAQ
Crontap vs Cronhub, in detail.
- When did Cronhub stop working?
- Paid subscriptions were cancelled on May 31, 2026. The whole service, including schedules, monitors, and ping history, closed and was deleted on June 30, 2026.
- Can I keep my Cronhub cron expressions verbatim in Crontap?
- Crontap accepts standard five-field cron expressions. Recreate the cadence and intended IANA timezone from your saved Cronhub configuration, then verify the next-fire preview before enabling it.
- Cronhub had two products (Scheduler and Monitoring). Does Crontap cover both?
- Yes. Crontap Schedules fire HTTP jobs, Uptime probes public URLs, and Heartbeats detect missing or /fail pings from jobs that run anywhere.
- Will Crontap match Cronhub's PagerDuty integration?
- Starter sends email with a one-day notification floor. Pro, Ultra, and legacy Pro add Slack, Discord, and Telegram. Generic webhooks remain machine Integrations. Crontap does not provide native PagerDuty or on-call escalation, so Cronitor is the closer match when those features matter.
- What does Crontap cost compared to my Cronhub plan?
- Compare against your final Cronhub invoice rather than an unsupported historical list price. Crontap Starter includes 2 combined items with hourly schedules, one daily uptime monitor, and one hourly heartbeat. Pro starts at $2.99/mo with one-minute cadence.
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