Vercel
The frontend cloud. Creators of Next.js.
5.0•1.1K reviews•36K followers
The frontend cloud. Creators of Next.js.
5.0•1.1K reviews•36K followers
Vercel provides the developer tools and cloud infrastructure to build, scale, and secure a faster, more personalized web.
This is the 32nd launch from Vercel. View more
Vercel Schedules
Launched this week
Vercel Schedules, now in public beta, lets apps and AI agents create, change and cancel scheduled tasks at runtime, with no redeploy. Use the JS SDK, CLI or HTTP API to set one-time or recurring runs that call a private function, an HTTP path or a Queue topic. Static schedules still live in vercel.json. Test on Preview deployments and trigger runs from the Schedules tab. Builds on Vercel Cron Jobs.
Free Options
Launch tags:Artificial Intelligence
Launch Team
Render Sandboxes: a computer for every agentIsolated compute, persistent state and a real filesystem
Promoted
Google Cloud Platform
Cloudflare Pages
Netlify
Railway
Vercel Schedules, now in public beta, lets your app or an AI agent decide when work runs while the app is live, with no redeploy.
Problem: Vercel Cron Jobs are set once in config, so changing a schedule means editing it and redeploying. That’s a poor fit when a user or an agent needs to say “remind me tomorrow at 9” or “check this every 30 minutes”.
Solution: Schedules builds on the Cron Jobs approach. A schedule tells Vercel when to trigger a task and where to send it, and your application supplies the code that does the work. You can create, change or cancel schedules through the JS SDK, CLI or HTTP API, for one-time or recurring runs.
What makes it different: Dynamic schedules can be created at runtime, including by AI agents, while static schedules still live in vercel.json and sync on deploy. When a task is due, Vercel uses Queues to deliver the saved request to your app, which checks permissions and starts the work. Private functions are called directly with no public URL, and Vercel verifies each call comes from the scheduling service.
Key features:
One-time and recurring schedules, created or changed at runtime with no redeploy
Targets: private functions, HTTP paths or Queue topics
Static schedules in vercel.json or Build Output API config
Runs on Preview deployments and custom environments before Production
A “Run Schedule” button in the project’s Schedules tab to trigger a task now and see past runs, plus vercel dev for local testing
An experimental Nitro 3 integration
Who it’s for: Developers building apps or AI agents on Vercel that need reminders, follow-ups, recurring jobs or agent tasks that users can set themselves.
Availability: Public beta. The post doesn’t state pricing, plan availability or limits, so check the docs.
If my agent schedules "remind me tomorrow at 9" for a user in another timezone, does it keep their local time through DST, or is the run stored in UTC?