# Vercel — Workflow SDK 5: built for production

- Company: Vercel (vercel.com)
- Announced: 2026-11-12T13:00:00+00:00
- Category: developer-tool-release
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://vercel.com/blog/workflow-sdk-5
- Record: https://forck.live/items/35940-workflow-sdk-5-built-for-production
- Subject: v0 / AI SDK / AI Gateway

Vercel released Workflow SDK 5, adding end-to-end payload encryption and per-region execution to the durable workflow tool, after customers ran more than 4 billion steps and 700 million runs on it. The SDK encrypts workflow and step inputs and outputs, hook payloads and stream data with AES-256-GCM, using a unique key for each run, so any backend including Vercel only stores ciphertext. On Vercel the encryption needs no setup or code changes, and each run's key is derived from a deployment-scoped key so a run can only decrypt its own data. Self-hosted Worlds can enable the same protection by implementing getEncryptionKeyForRun() with their own key management, returning the same 32-byte key per run. Cross-run writes are encrypted to the target run's public key, and setting payload retention to experimental_retention: 0 deletes inputs, outputs and stream contents once a run completes or fails. Vercel also deployed Workflow infrastructure to every Vercel Function region, so each run's state, queue dispatch and streams are served from the region where it started, instead of the single iad1 region used in Workflow SDK 4.

## Evidence

Verbatim from https://vercel.com/blog/workflow-sdk-5:

> When we first launched Workflow SDK, the goal was simple: write regular async JavaScript, and let the SDK keep it running through crashes, deployments, and long waits.
> 
> import { sleep } from "workflow" ; export async function welcomeUser ( email ) { "use workflow" ; const user = await createUser ( email ) ; await sendWelcomeEmail ( user ) ; // Survives crashes and deployments // while it waits await sleep ( "3d" ) ; await sendCheckInEmail ( user ) ; }
> 
> A basic durable workflow
> 
> Last year, we shipped just that , with the world-class developer experience Vercel is known for. Then we watched what our customers built with it.
> 
> More than 4 billion steps and 700 million runs later, two clear patterns have emerged.
> 
> The first is automation : Traditional workflows that move data, process orders, coordinate background jobs, manage subscriptions, and run ETL and data pipelines.
> 
> The second is agents and harnesses : Agents are expensive and long running, so they naturally require durability too.
> 
> As those workloads matured, Workflow matured with them. Our priorities have always been security, reliability, and performance.
> 
> Here’s how Workflow SDK 5 delivers on all three.

---

Record: https://forck.live/items/35940-workflow-sdk-5-built-for-production
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
