Comparison
Crontap vs Cronhub
Cronhub announced its shutdown. Paid subscriptions are cancelled on May 31, 2026. Schedules, monitors, and ping history are deleted on June 30, 2026. Crontap is the closest 1:1 replacement for both halves of Cronhub: the Scheduler and the Monitoring.
At a glance
Cronhub vs Crontap, side by side.
| Dimension | Cronhub | Crontap |
|---|---|---|
| Status | Shutting down June 30, 2026 | Active, GA |
| Cadence floor | 1 minute | 1 minute (Pro) |
| Per-schedule timezone | Yes | Yes (any IANA) |
| Automatic retries on 5xx | No | Yes (with backoff, alert after retry budget) |
| Per-request timeout | 3 seconds | Longer window (per request) |
| Built-in monitoring (uptime + heartbeats) | Yes (Scheduler + Monitoring products) | Uptime built in; pair with Healthchecks.io for dead-man heartbeats |
| Integrations panel (failure / success alerts) | Email, Slack, SMS, webhook, PagerDuty | Email, Slack, Discord, Telegram, webhook |
| Free tier | None | 1 schedule at hourly cadence |
| Paid entry | $5/mo (Hobby), up to $49/mo | $3.25/mo annual (unlimited schedules at 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. Pricing started at $5/mo with no free tier.
Crontap
Crontap is scheduling-first with Uptime monitors built into the same dashboard. You paste a URL, set the cadence (cron expression or plain English) and timezone, optionally add Authorization headers and a JSON body, and Crontap fires the endpoint on cadence with automatic retries on 5xx and a longer timeout window. For dead-man absence detection on schedules you do not own, the canonical pair is Crontap plus Healthchecks.io.
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 routes SMS through webhook).
- 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
- A future. Crontap is GA and shipping; Cronhub stops accepting paid subscriptions on May 31, 2026.
- Free schedule included. 1 schedule at hourly cadence with no credit card. Cronhub had no free tier and started at $5/mo.
- Automatic retries on 5xx with 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.
- Flat predictable Pro pricing at $3.25/mo billed annually for unlimited schedules at minute cadence. Cronhub topped out around $49/mo.
- Integrations panel that covers the same alert shapes (email, Slack, Discord, Telegram, webhook) plus an Uptime monitor surface in the same account.
The math
Cadence and pricing, worked out.
- On Cronhub Hobby ($5/mo, no free tier) with 1 schedule at hourly cadence, the equivalent setup on Crontap is $0/mo on the free forever tier (free schedule included).
- On Cronhub Standard or Pro (up to $49/mo) with unlimited schedules at minute cadence, the equivalent setup on Crontap is $3.25/mo billed annually.
- If you only used Cronhub Monitoring (heartbeats), pair Crontap free with Healthchecks.io free (20 checks). Most small setups land at $0/mo.
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, decide between a Crontap Uptime monitor (for is-this-URL-up cases) or a Healthchecks.io check (for dead-man absence on schedules you do not own). Update the ping URL in the job that pings.
- Run both in parallel for one full window, then delete the Cronhub equivalent only after you see green in the new tool.
- 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 need Cronhub for the next 7 weeks while you migrate, and you have already exported your schedule and monitor configurations so the June 30 data deletion does not surprise you.
Pick Crontap if
You want a 1:1 replacement for the Cronhub Scheduler with automatic 5xx retries, a longer timeout window, per-schedule IANA timezones, an integrations panel, and a free tier Cronhub never had. Pair with Healthchecks.io if you also need dead-man absence detection.
Pair both if
You are mid-migration and want to run schedules in both for one full window before flipping the cut. Both fire the same idempotent URL; the new tool catches up on history while the old one keeps the lights on until the cutoff.
FAQ
Crontap vs Cronhub, in detail.
- When exactly does Cronhub stop working?
- Per the shutdown banner on cronhub.io: paid subscriptions are cancelled on May 31, 2026, and the whole service (schedules, monitors, ping history) is deleted on June 30, 2026. Export anything you want to keep before June 29.
- 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?
- Crontap covers Scheduler 1:1 and covers monitoring through two surfaces: built-in Uptime monitors for is-this-URL-up cases, and the canonical Crontap + Healthchecks.io pair for dead-man absence detection on jobs you run elsewhere. The Crontap blog post (linked below) has the click-by-click walkthrough for both halves.
- Will Crontap match Cronhub's PagerDuty integration?
- Crontap's built-in alert channels are email, Slack, Discord, Telegram, and webhook. PagerDuty is reachable via webhook (their generic webhook integration on a service, or Custom Event Transformer). If first-class PagerDuty matters more than scheduling features, Cronitor is the closer match.
- What does Crontap cost compared to my Cronhub plan?
- Cronhub started at $5/mo with no free tier and topped out around $49/mo. Crontap includes a free schedule at hourly cadence (no credit card) and Pro is $3.25/mo billed annually for unlimited schedules at minute cadence. Most Cronhub Hobby and Standard customers fit on Crontap free 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