Vercel Queues now in public beta
By Steven Van ·
The durable event streaming system behind Vercel Workflows is open to all teams, billed from $0.60 per million operations.
Vercel Queues, a durable event streaming system built on Fluid compute, is now in public beta for all teams. It sits underneath Vercel Workflows: Queues handles direct message publishing and consumption, while Workflows adds ergonomic multi-step orchestration on top.
Messages are sent to a durable topic, which fans them out to subscribed consumer groups. Each group processes messages independently, and the queue keeps redelivering a message until it's handled successfully or expires. That gives a function a way to defer expensive work, such as sending emails or calling external APIs, and guarantees the work still completes if the function crashes or a new deployment rolls out.
- Messages are published from any route handler with the send function from @vercel/queue.
- A consumer is created with handleCallback, and its consumer group is set by adding an experimentalTriggers entry to vercel.json.
- Adding a trigger makes that route private: it gets no public URL, and only Vercel's queue infrastructure can invoke it.
Vercel Queues is billed per API operation, starting at $0.60 per 1M operations, and includes multiple-AZ synchronous replication, at-least-once delivery, and customizable visibility timeouts.