{
  "slug": "vercel-cron",
  "name": "Vercel Cron",
  "url": "https://vercel.com/docs/cron-jobs",
  "cat": "auto",
  "group": "ship",
  "tagline": "Cron for Vercel functions",
  "price": "Included on all plans. Hobby free: 100 cron jobs per project, once-per-day maximum, plus or minus 59 minutes of drift. Pro (from $20/user/mo): 100 jobs, per-minute schedules and precision. Function usage billed separately.",
  "tier": "mixed",
  "pick": false,
  "what": "Declare schedules in <code>vercel.json</code> and Vercel invokes the matching route on time. No extra service, queue or dashboard: the cron entry just calls a normal function, so it inherits that function's runtime, timeout and billing.",
  "why": "Lowest-friction scheduler if you already deploy to Vercel: three lines of JSON plus a route handler. Good for nightly digests, cache warming, cleanup jobs and kicking off a real queue.",
  "warn": "Hobby is capped at <b>once per day</b> with up to 59 minutes of drift, and more frequent expressions fail at deploy time. Crons only fire; they do not queue, fan out or retry, so real work still needs a job runner.",
  "category": {
    "key": "auto",
    "name": "Automation & background jobs",
    "desc": "Visual no-code and code-first job runners — different problems, listed together.",
    "group": "ship",
    "groupName": "Ship it & keep it alive"
  },
  "freshness": null,
  "health": {
    "ok": true,
    "status_code": 200,
    "final_url": null,
    "checked_at": "2026-08-19T00:58:08.071+00:00"
  },
  "corrected_at": null,
  "upstream_changed_at": null
}