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 |
| Cadence floor | 1 minute | 1 minute (Pro) |
| Per-schedule timezone | Yes | Yes (any IANA) |
| Automatic retries | No | Yes, with exponential backoff |
| Per-request timeout | 3 seconds | Longer window (per request) |
| Heartbeat / dead-man monitoring | Yes (before the June 30, 2026 shutdown) | Yes, native (period + grace, /fail; Email, Slack, Discord, Telegram; webhooks) |
| Schedule integrations (failure / success alerts) | Email, Slack, SMS, webhook, PagerDuty | Email, Slack, Discord, Telegram; webhooks |
| Free tier | None | 2 combined schedules + uptime + heartbeats |
| Historical paid entry | $10/mo (Hobby) | from $2.99/mo (scales as you grow, 1-minute cadence) |
How they work
The two approaches in one paragraph each.
Cronhub
Cronhub bundled two products under one bill. The Scheduler took a URL, a cron expression, and a timezone, and fired the URL on cadence with a 3-second timeout and no automatic retries. The Monitoring product received heartbeat pings from jobs you ran elsewhere and paged you when a ping failed to arrive in the configured window. Historical Hobby pricing started at $10/mo with no free tier.
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.
- Free forever tier: 2 combined schedules, uptime monitors, and heartbeats. Starter heartbeats run hourly or slower. Cronhub had no free tier; its historical Hobby plan started at $10/mo.
- Automatic retries with exponential backoff. Cronhub Scheduler had no automatic retry; one bad fire and you only knew through the alert.
- Longer timeout window per request. Cronhub Scheduler capped requests at 3 seconds, which trips on cold-start backends and longer reconciliations.
- Crontap Pro starts at $2.99/mo and scales as you grow at 1-minute cadence, below Cronhub's former $10/mo Hobby entry.
- Connected email, Slack, Discord, and Telegram notification channels, plus generic webhook Integrations across Schedules, Uptime, and Heartbeats.
- Native heartbeats for silent jobs, so Cronhub Monitoring migrations no longer require a second vendor.
The math
Cadence and pricing, worked out.
- On the former Cronhub Hobby plan ($10/mo, no free tier) with 1 schedule at hourly cadence, the equivalent setup on Crontap is $0/mo on the free forever tier.
- 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.
- Paste the cron expression verbatim. Cronhub uses the standard 5-field expression and Crontap accepts it unchanged.
- Pick the same IANA timezone the Cronhub schedule used. Crontap is per-schedule, no DST math required.
- 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?
- Yes. Cronhub uses the standard 5-field cron expression and Crontap accepts the same syntax unchanged. Paste the expression as-is, pick the same IANA timezone, and the next-fire preview should match your old Cronhub schedule.
- 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?
- Crontap sends schedule, uptime, and heartbeat alerts to connected email, Slack, Discord, and Telegram channels. 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?
- Cronhub had no free tier; its historical Hobby plan started at $10/mo. Crontap includes 2 combined schedules, uptime monitors, and heartbeats on Starter, and Pro starts at $2.99/mo with 1-minute cadence. Many former Cronhub customers fit on Crontap Starter or Pro for less than they paid Cronhub.
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