On 2026-11-05 Vercel launched Schedules in public beta on all plans: static jobs in vercel.json plus dynamic one-shot/cron schedules via SDK/CLI/API targeting private Functions, HTTP paths, or Queues. Eve and AI SDK samples let agents schedule follow-up work. Existing Cron Jobs remain supported.

Key Takeaways

  • ✓Official: Vercel 2026-11-05 changelog + blog Introducing Vercel Schedules; amplified on @vercel
  • ✓Capabilities: static (vercel.json) and dynamic (SDK/CLI/API) one-shot/cron; Function, HTTP, or Queue targets
  • ✓Agents: Eve ships dynamic scheduling; AI SDK sample uses Schedules.create + Queue wake-up
  • ✓Billing (vendor): ~$5 per 1M runs and $10 per 1M creations on Pro/Enterprise; Hobby 500 creates / 5,000 runs per month
  • ✓Existing Cron Jobs keep working; schedule/v1beta functions have no public URL
Vercel Schedules Public Beta: Static and Dynamic Jobs Agents Can Create at Runtime via Queues
🖼️Official Media
Click to view high-res
⚡

Key Decision Metrics at a Glance

TL;DR Verdict
🏆 Benchmark RankRank
No model benchmark in this story · see current rankings
Full Leaderboard→
💰 Cost & PlansCompare
Billing (vendor): ~$5 per 1M runs and $10 per 1M creations on Pro/Enterprise; Hobby 500 creates / 5,000 runs per month
Compare Plans↗
🛠️ Ecosystem & IDERules
Claude Code (Anthropic)
Setup IDE Rules↗
🧭

Turn your technical choice into a development budget

Compare 40 dev plans & simulate token costs vs $20/mo subscriptions

⚔️ Compare Model→💰 Compare plans & limits↗
🔗

Project Links & Resources

Direct Access
Direct access to official project resources and documentation
📝
Introducing Vercel Schedules
vercel.com/blog/introducing-vercel-schedules
↗
📖
Vercel Schedules public beta (changelog)
vercel.com/changelog/vercel-schedules-is-now-in-public-beta
↗
📖
Scheduling Work for Agents
vercel.com/docs/schedules/agents
↗
🔬

In-Depth Technical Analysis

Core Background & Industry Pain Points

Classic cron needs a redeploy to change timing, while agents invent one-off asks like "summarize HN tomorrow." Apps end up with a job table plus polling and weak preview testing.

Architecture Highlights & Internals

Vercel Schedules is in public beta on all plans. Static schedules in vercel.json can hit a private Function, HTTP path, or Queue topic. Dynamic schedules via JS SDK, CLI, or API target a Queue topic for one-shot or cron work. Functions with schedule/v1beta have no public URL. Preview/custom environments and Run Schedule are supported. Eve ships dynamic tools; AI SDK, Pi, and libfx can wrap Schedules.create.

Authoritative Benchmarks & Measured Scores

No latency/reliability benchmarks published. Vendor billing: about $5 per 1M runs and $10 per 1M creations on Pro/Enterprise; Hobby includes 500 creations and 5,000 runs per month. Existing Cron Jobs keep working with a migration guide.

Developer Hands-on Guide

Install @vercel/schedules. Expose Schedules.create with the prompt and timezone in the payload; wake the agent from a Queue consumer. Use per-user namespaces, name schedules after the tool call, and dedupe with executionId. See Scheduling Work for Agents.

Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.

⚔️ Launch VS Compare→💳 View Plans↗
Up NextVercel CI enters beta: runs only the Turborepo tasks a change affects, 2-6x faster CI built for coding agents
Read Now→