Vercel has announced that its new feature, Vercel Schedules, is now available in public beta across all plans. This service enables users to automate the execution of various tasks, either at predetermined recurring intervals or at specific, one-time points. These scheduled tasks can operate within different deployment contexts, including production, preview, and custom environments, offering flexibility for diverse development and operational needs.
Developers can define schedules in two primary ways. For static, persistent tasks, configurations can be added directly within the vercel.json file. These static schedules are designed to target a private Vercel Function, an external HTTP path, or a specific Vercel Queue topic. When a Vercel Function is triggered by a static schedule, it operates privately, meaning it lacks a public URL and can only be invoked by the Vercel scheduling infrastructure, enhancing security. Alternatively, schedules can be created dynamically at runtime, primarily targeting a Vercel Queue topic for more programmatic control.
A key advantage of Vercel Schedules is the ability to manage them without requiring a redeployment of the application. Users can easily enable, disable, or manually trigger any schedule on demand, providing significant operational agility. This capability streamlines the management of background processes and automated workflows directly within the Vercel platform.
Why it matters for businesses and developers
This feature provides businesses with a robust mechanism for automating critical background operations and recurring tasks, enhancing operational efficiency and reliability. For developers, Vercel Schedules simplifies the implementation and management of scheduled jobs directly within their existing Vercel projects, reducing the need for external scheduling services and streamlining deployment workflows.
This brief is our own summary. Read the original story, “Vercel Schedules is now in public beta”, at Vercel (published 5 Nov 2026).