Will this deploy on Vercel Hobby?
Vercel’s cron rules are stricter than standard cron in ways that fail the deployment rather than the job. Paste your config and find out before you push.
Your vercel.json, or a single expression
Checked in your browser. Nothing you paste is sent anywhere — there is no request behind this, which is the only honest way to ask someone for a file out of their repository.
0 9 * * 1-5/api/digestAt 09:00 AM, Monday through Friday
Runs at most once every 1 day · all Vercel crons are evaluated in UTC
Warning: Hobby fires within the hour, not on the minute
Scheduling precision on Hobby is anywhere within the hour (±59 minutes). A job written for 01:00 can run at 01:59, so do not rely on it for anything time-sensitive.
*/15 * * * */api/syncEvery 15 minutes
Runs at most once every 15 minutes · all Vercel crons are evaluated in UTC
Error: Hobby allows one run per day, this runs more often
Its closest two runs are 15 minutes apart. Vercel rejects this at deploy time with "Hobby accounts are limited to daily cron jobs" — the deployment fails rather than the job silently running late.
Limits checked against Vercel’s published pricing for cron jobs on 15 July 2026. Vercel can change these, so check the source if a deploy disagrees with this page.
What Vercel actually allows
| Plan | Cron jobs | Minimum interval | Precision |
|---|---|---|---|
| Hobby | 100 | Once per day | Within the hour (±59 min) |
| Pro | 100 | Once per minute | Per minute |
| Enterprise | 100 | Once per minute | Per minute |
The job count is the same on every plan — the tier difference is frequency, not how many you can define. Figures checked on 15 July 2026 against Vercel’s documentation.
Three rules that are not standard cron
These are the ones that catch people, because the expression is valid everywhere else — including on crontab.guru — and fails only when Vercel builds it.
- No names.
MON,SUN,JANandDECare not supported. Use numbers — 0–6 for day of week, 1–12 for month. - Not both day fields. If day of month has a value, day of week must be
*, and the other way round. - Always UTC. There is no timezone setting. A job written for 09:00 fires at 09:00 UTC, which drifts against your local working day twice a year.
If Hobby will not take your schedule
You have three options, and only one of them is us. Upgrade to Vercel Pro if you want everything in one place. Trigger the endpoint from something you already run — a GitHub Actions schedule works, with the same UTC-only caveat and its own timing looseness. Or call it from an external scheduler.
getNodi is the third option: it calls your existing /api/cron route on whatever schedule you actually wanted, in your timezone rather than UTC, retries when it fails, and tells you when it stops working. Your Vercel plan stays as it is, and the route does not change.
One thing to do either way: put a shared secret on that route and check it. A cron endpoint that runs for anyone who finds the URL is a problem regardless of what is calling it.