Vercel Schedules enters public beta on all plans

Schedules can be declared statically in vercel.json, where they can target a private Vercel Function, an HTTP path, or a Vercel Queue topic. Schedules created at runtime target a Queue topic. Any schedule can be enabled, disabled, or run on demand without a redeploy.

Adding a schedule/v1beta trigger to a function makes that function private, with no public URL, so only the Vercel schedule infrastructure can invoke it. The function handles each dispatch with handleSchedule from the @vercel/schedules package, which receives metadata such as the schedule name and scheduled time.

Schedules is the successor to Cron Jobs. Existing Cron Jobs continue to work, and a migration guide covers moving them over. Vercel says Schedules also powers dynamic schedules in Eve and experimental scheduled tasks in Nitro projects. Pricing starts at $5 per 1M runs and $10 per 1M creations on Pro and Enterprise, while Hobby includes 500 creations and 5,000 runs per month.

Agents that need periodic work, such as cleanup jobs or digests, can now be scheduled without an external cron service or a public endpoint. Runtime-created schedules can also be toggled or triggered manually without redeploying.

If you run Cron Jobs today, plan a move to Schedules using the migration guide, and check the per-run and per-creation pricing against how often your agents create schedules.