Comparison
Crontap vs Vercel Cron
Vercel Cron is convenient for production Vercel Functions: every plan allows 100 jobs, Vercel sends UTC GET requests, and Pro or Enterprise can run every minute. Hobby is limited to once daily with hour-level precision. Crontap is the external option for timezone-aware HTTP requests, retries, alerts, uptime, and heartbeats across hosts.
At a glance
Vercel Cron vs Crontap, side by side.
| Dimension | Vercel Cron | Crontap |
|---|---|---|
| Cadence minimum, Hobby | Once per day, with per-hour precision | Hourly+ on Starter |
| Cadence minimum, Pro / Enterprise | 1 minute | 1 minute |
| Cron jobs per project | 100 on Hobby, Pro, and Enterprise | Plan combined-item cap |
| Per-schedule timezone | No (UTC only) | Yes (any IANA) |
| Change cadence | Redeploy vercel.json | Save in dashboard |
| Dashboard scope | Per-project | All projects + non-Vercel targets |
| Free tier | 100 daily cron jobs; Function usage applies | Starter: 2 combined items; schedules hourly+, 1 uptime monitor daily, and 1 heartbeat hourly |
| Human Notifications | Anomaly alerts cover unexpected usage or behavior, not deterministic per-cron failure routing | 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 | No cron-specific machine callback surface | 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 | No native dead-man monitor | Native: period + grace, /fail, missed/recovered/explicit-failure alerts, ping URL, and 90-day history |
| Uptime monitoring | No native uptime monitor in Cron Jobs | Native HTTP uptime: down/recovered alerts, history, 90-day rollups, and integration controls |
| Retries and customization | No automatic retries; delivery is best-effort | 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 |
| AI response processing | No cron response transform-and-forward workflow | AI response transforms: transform, summarize, normalize, extract, or triage, then forward. Pro: daily, 1 per schedule. Ultra: hourly, unlimited; test-run UX |
| Pricing | $20/mo per user | $0 free / from $2.99/mo Pro |
How they work
The two approaches in one paragraph each.
Vercel Cron
Vercel Cron lives in vercel.json or Build Output API output. Vercel sends a GET request to the production deployment URL in UTC. It documents best-effort delivery, including the possibility of missed or duplicate invocations, and does not automatically retry failed cron requests.
Crontap
Crontap is an external scheduler. You paste the URL of any HTTP endpoint, set the cadence (cron expression or plain English) and timezone, optionally add Authorization headers and a JSON payload. Crontap fires the endpoint on cadence; nothing about the schedule is bundled into your repo or your deploy.
Where each side wins
Honest broker, both columns.
Vercel Cron wins on
- One-click setup if your code already lives on Vercel.
- No new dashboard to learn.
- Tightly integrated with Vercel observability.
- 100 cron jobs per project are included on every plan; Function usage still applies.
Crontap wins on
- Methods, custom headers, and JSON bodies instead of GET-only production paths.
- Every 1 minute on Pro. Vercel Hobby is once daily with hour-level precision.
- Per-schedule IANA timezones (UK customers fire at 5am Europe/London, US customers fire at 9am America/New_York, same account).
- Change cadence in the dashboard, no redeploy.
- Human Notifications and machine webhook Integrations are routed separately.
- Default-on retries with paid controls, plus native uptime and heartbeat monitoring.
- One dashboard across multiple Vercel projects, plus non-Vercel targets like Cloud Run, Railway, or your own box.
The math
Cadence and pricing, worked out.
- Need every 5 minutes? Vercel Hobby cannot run more than once daily. Vercel Pro can run every minute and includes 100 cron jobs per project. Crontap Pro starts at $2.99/mo for one-minute scheduling across any HTTP host.
- The comparison is not job-count superiority: Vercel now allows 100 cron jobs on every plan. Crontap's wedge is HTTP configuration, timezone, retries, monitoring, and cross-platform routing.
Moving from Vercel Cron
The migration, in 4 steps.
- Paste your existing config into the free cron migrator to get every schedule pre-filled as a Crontap deep link.
- Pick the API route currently driven by your vercel.json crons entry.
- Add Authorization-header verification on that route so it refuses unauthenticated calls.
- Create a Crontap schedule pointing at https://yourdomain/api/your-route with the header set. Delete the vercel.json cron entry on next deploy.
Decision
Which one fits.
Pick Vercel Cron if
Your target is a production Vercel Function, UTC is fine, GET is enough, and deploy-managed configuration is desirable.
Pick Crontap if
You need per-schedule timezones, richer HTTP requests, automatic retries, deterministic alert routing, or a dashboard across hosts.
Pair both if
Keep your daily Vercel Cron build refresh and add Crontap for schedules that need per-IANA timezones or live across non-Vercel targets.
FAQ
Crontap vs Vercel Cron, in detail.
- Can Crontap call my Vercel function?
- Yes. Paste the deployment URL into Crontap and set an Authorization header on the schedule. Your route verifies the header and runs as normal.
- Will Vercel Cron and Crontap conflict?
- No. They run independently. Many teams pair them: keep Vercel Cron for tightly-coupled-to-deploy schedules and add Crontap for per-IANA timezone schedules or schedules that span multiple Vercel projects.
- How is this different from cron-jobs-for-vercel?
- That is a use-case-first guide for Vercel users wiring up cron. This is a head-to-head decision page comparing Crontap and Vercel Cron directly.
- What about timezone-aware Vercel Cron?
- Vercel Cron is UTC-only as of 2026 docs. Crontap supports any IANA timezone per schedule, set independently for each schedule on the same account.
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