Vercel ships Workflow SDK 5: run payloads are encrypted end to end by default, and a 1,020-step workflow's median finish drops from 21.0 to 3.0 minutes
Synopsis
Vercel released Workflow SDK 5, which encrypts durable workflow payloads end to end by default and keeps each run's state in the region where it started. Previously every run's event log, queue and streams lived only in iad1, so steps elsewhere made cross-region requests to record progress; v5 deploys Workflow infrastructure to every Vercel Function region and rewrites the engine to cut queue hops. On a 1,020-step benchmark, v5.2.0's median time to finish all steps fell from 21.0 minutes on v4.8.12 to 3.0 minutes.
Interpretation
A durable workflow's run data is now encrypted before it leaves the code, and the backend sees only ciphertext. Previously the event log stored step arguments and return values, which can include customer information, model context, credentials and tool-call results, and that data was persisted in readable form. Workflow and step inputs and outputs, hook payloads and stream data are encrypted with AES-256-GCM under a unique key per run; on Vercel this needs no setup or code change, the key is derived from the deployment's scope, and a run can only decrypt its own data.
Run state now follows the region of the function that starts it, removing cross-region round trips from the hot path. In Workflow SDK 4 every run lived in iad1, so even a project deployed to several regions made cross-region requests whenever a step elsewhere recorded its progress. v5 deploys Workflow infrastructure to every Vercel Function region, and a run's state, queue dispatch and streams are served from its starting region; start() accepts a region to place the data, and existing v4 runs stay in iad1.
The rewritten engine cuts queue hops and network and CPU work per step for long agent workloads. In v4 each step invocation took one queue hop to start the step and another to continue the workflow, acceptable for slow background automation but a bottleneck for agent loops with thousands of sequential events. In a five-step benchmark, p75 step-to-step overhead fell from 618 ms to 109 ms; in the final sampled range of a 1,020-step benchmark, overhead fell from 1,748 ms to 70 ms, and median time to finish all 1,020 steps fell from 21.0 minutes to 3.0 minutes.
Perspective
The performance measurements were taken on October 8, 2026, on Vercel production in iad1 against the managed Vercel World, with each version deployed as the same app and steps taking 1 KB of JSON in and out; the numbers describe one workload in one region, not a prediction for every application. Encryption works with zero configuration on Vercel, while a self-hosted World must implement getEncryptionKeyForRun() and return a stable 32-byte key for each run.
Vercel says anonymized telemetry and customer collaboration let it find and fix dozens of rare bugs and race conditions in the runtime, and that with v5 almost no runs fail or stall because of a platform or runtime bug, but it gives no corresponding failure-rate figure. During failover, steps can execute in a fallback region while the run's state stays pinned to its home region and does not migrate.
