From the source
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.






