Vercel Cron Jobs logo

Vercel Cron Jobs

Schedulers 7.8/10 Jun 16, 2026

Cron-triggered HTTP GET requests to Vercel Functions in a production deployment.

Card required
No

Vercel Cron Jobs scores 7.8/10 for free value in Schedulers. The main constraint: Available on all Vercel plans; Hobby scheduling limits and function limits apply.

Category Schedulers Kind Frontend platform cron Caveats Timezone is UTC and jobs trigger production deployment paths. Not a general container runtime. Renewal monthly Card required No Eligibility anyone

Free value score

7.8 / 10
Show the math
Overall 7.8/10
value = 7.8/100
weighted_components_v1
Run value 9/10
value = 10 $/mo
fixed_log_v1
Reliability 5.5/10
value = 5.5/100
policy_score_v1
Workflow fit 8.3/10
value = 8.3/100
policy_score_v1

Key metrics

3.0K/mo Run quota Uses stated run/message/execution quota when present; otherwise a conservative floor.
1.0/hr Granularity/reliability Derived from minimum interval with conservative reliability adjustment.
5 Workflow/runtime cron, history, http, logs, timeout
100 jobs Cron jobs
24 hr Min interval
3K/mo Executions
1 hour log Run history
5 min Job timeout 300s

What you get

Configured in vercel.json

Triggers Vercel Functions

Good when the app is already on Vercel

Gotchas

  • 100 cron jobs per project

    Hobby plan allows up to 100 cron jobs per project, which resets as projects are managed.

  • Once-per-day execution limit

    On the Hobby plan, each cron job can run at most once per day; any cron expression that resolves to more frequent than daily will fail at deployment.

  • ±59 min scheduling imprecision

    Hobby plan offers only hourly scheduling precision — a job set for 01:00 UTC may fire anywhere between 01:00 and 01:59 UTC.

  • No sub-daily or per-minute schedules

    Sub-daily intervals (hourly, every 30 min, etc.) are unavailable on Hobby; Pro/Enterprise is required for per-minute precision and higher frequency.

  • UTC timezone only

    Cron schedules always execute in UTC; there is no per-job timezone configuration available on any plan.

  • HTTP GET trigger only

    Cron jobs trigger Vercel Functions via HTTP GET to a production deployment URL; arbitrary shell commands or containers are not supported.

  • Production deployment only

    Cron jobs only invoke the production deployment path, not preview or development environments.

  • Vercel Functions runtime limits apply

    Each cron invocation is subject to Vercel Function execution time, memory, and payload limits (Hobby: up to 300s / 5 min max duration).

  • Vercel-hosted apps only

    Cron jobs are tightly coupled to Vercel deployments and cannot be used to trigger external non-Vercel endpoints as a standalone scheduler.

Sources

vercel cron functions nextjs http

Alternatives

Same category · similar quota
Val Town CronVal Town Cron · freemium · Hosted script cron
8.3

Hosted TypeScript/JavaScript functions with built-in cron triggers for quick automations.

3.0M/mo4.0/hr6
Checked 28d ago
Upstash | QStashUpstash · freemium · HTTP scheduler / delivery queue
7.0

Managed HTTP messaging, schedules, queues, retries, callbacks, and failure handling for serverless automation.

30.0K/mo30.0/hr13
Checked 27d ago
Cloudflare Workers Cron TriggersCloudflare Workers Cron Triggers · freemium · Edge cron function
6.5

Run a Worker on cron expressions for lightweight scheduled API and automation tasks.

3.0M/mo60.0/hr6
Checked 28d ago