Vercel releases Workflow SDK 5 with payload encryption and per-run home regions
Vercel released Workflow SDK 5, which encrypts workflow and step inputs, outputs, hook payloads, and stream data with AES-256-GCM using a unique key per run, and lets self-hosted Worlds implement encryption through getEncryptionKeyForRun(). Each run now has a home region for its state, queue dispatch, and streams, and runs start in the region of the function that starts them unless a region is passed to start().

Why it matters
Builders storing customer data, credentials, or model context in workflow runs can enable encryption and set experimental_retention: 0 to delete payloads on completion, which changes how sensitive data is stored. Region placement via start() also affects where run data lives, which matters for data residency and latency.
Who should care
Developers and teams running durable workflows on Vercel or self-hosted Worlds, especially those handling sensitive customer data or regional data residency requirements.
What you can do
Review the Workflow SDK 5 docs for payload encryption and experimental_retention, and decide whether runs handling sensitive data should use encryption and zero retention before upgrading from v4.