Vercel Flags and Workflows GA
Vercel announced general availability of Vercel Flags, letting developers define feature flags in code and manage them through a dashboard. The company also made Vercel Workflows generally available to orchestrate code‑driven agents and backends without manually managing queues or retries. (x.com) (x.com)
Vercel has made two developer tools generally available: Flags for turning features on and off in production, and Workflows for running long, multi-step code without managing the plumbing underneath. (vercel.com) Feature flags are simple switches inside an app: a team can ship code to everyone, then expose it only to employees, 10% of users, or a single customer segment. Vercel said on April 16 that its Flags product is now generally available in the dashboard, with targeting rules, user segments, and environment controls. (vercel.com) Vercel’s docs say developers can define flags in code with the Flags Software Development Kit, then manage rollout rules in the dashboard. The service supports Next.js and SvelteKit directly, and it also works through the OpenFeature standard for other frameworks and backends. (vercel.com 1) (vercel.com 2) The same docs say Flags can return boolean, string, number, or JavaScript Object Notation values, which lets teams use them for feature gates, A/B tests, thresholds, and structured configuration. Vercel says changes replicate globally in milliseconds and that flag data can be tied into runtime logs and web analytics. (vercel.com) Workflows tackles a different problem: jobs that take too long or fail too often for a normal web request. Vercel describes Workflows as a fully managed platform for durable execution, meaning code can pause for minutes or months, survive crashes or deployments, and resume from the same point later. (vercel.com) In practice, that covers jobs like agent orchestration, document processing, data sync, or any chain of external application programming interface calls that can time out halfway through. Vercel says developers write these flows in async JavaScript or TypeScript with `"use workflow"` and `"use step"` directives instead of wiring up queues, retries, and persistence by hand. (vercel.com 1) (vercel.com 2) The product shipped first as the open-source Workflow Development Kit public beta on October 23, 2025. Vercel’s current documentation says the managed Workflows service runs on Vercel Functions and Vercel Queues, stores state and event logs in managed persistence, and exposes logs, metrics, and tracing in the dashboard. (vercel.com 1) (vercel.com 2) Vercel has been tightening that system in recent months. A February 3 update moved Workflow 4.1 Beta to an event-sourced architecture, and an April changelog post said median application programming interface response time fell from 37 milliseconds to 17 milliseconds, a 54% improvement. (vercel.com) (vercel.com) The release fits Vercel’s broader push to sell more of the stack around modern web apps and artificial intelligence agents, not just hosting. Over the past year, the company has also expanded products including AI Gateway, Sandbox, Observability, and marketplace integrations for agents and services. (vercel.com) (vercel.com) (vercel.com) (vercel.com) That leaves Vercel pitching a tighter loop to developers: ship code behind a flag, watch what happens, and hand longer-running jobs to a managed workflow engine. The company’s latest message is that both controls now live inside the same platform. (vercel.com) (vercel.com)
