VercelVercel
Queues

Vercel Queues

Last updated February 28, 2026

Vercel Queues are available in Beta on all plans

Vercel Queues is a durable event streaming system built for serverless applications. You publish messages to topics, and independent consumer groups process them in parallel with automatic retries, sharding, and delivery guarantees.

Each topic is a durable, append-only log that retains messages until they expire. Messages fan out to every consumer group subscribed to the topic, and new consumer groups can join at any time to replay non-expired history.

Producer Topic Producer Consumer Group A(email notifications) Consumer Group B(analytics pipeline) Consumer Group C(audit log)

Vercel Queues is useful when you need to:

  • Defer expensive work: Offload tasks like sending emails, generating PDFs, or calling external APIs so your response returns fast.
  • Absorb traffic spikes: Buffer incoming requests and process them at a controlled rate.
  • Guarantee delivery: Make sure work completes even if a function crashes or a deployment rolls out.
  • Schedule tasks: Delay message delivery by up to the retention period.
  • Deduplicate messages: Use idempotency keys to prevent duplicate processing.
  • Isolate consumers: Process the same messages in multiple independent pipelines without interference.

Vercel Queues is the lower-level primitive that powers Vercel Workflow. Workflow provides a higher-level SDK with durable steps, sleep, and hooks that makes building multi-step applications more ergonomic. If you need direct control over message publishing, consumption, and routing, use the Queues SDK directly. If you're building stateful multi-step workflows, start with Workflow.

  • Durable delivery: Persist messages with retries and visibility timeouts for reliable processing.
  • Fan-out consumers: Send one message stream to multiple independent consumer groups without coordination.
  • Push and poll modes: Process on Vercel with push callbacks or run your own workers.
  • Automatic scaling: Scale producers and consumers without managing partitions or throughput capacity.
  • SDK and API: Publish and consume with the SDK or HTTP API.

Was this helpful?

supported.