# Vercel releases Workflow SDK 5 with encryption and regional runs

published: 2026-11-13T22:05:34.118Z
topic: infrastructure
source: https://vercel.com/blog/workflow-sdk-5
url: https://aiagentnews.io/stories/vercel-releases-workflow-sdk-5-with-encryption-and-regional-runs

Vercel has released Workflow SDK 5, which encrypts workflow and step payloads by default and lets each run live in its own home region. The release also adds run attributes, a redesigned trace viewer and payload retention controls.

Workflow SDK 5 encrypts every payload before it leaves the developer's code, using AES-256-GCM with a unique key for each run. On Vercel the encryption needs no setup or code changes, and Vercel manages the keys by default so observability keeps working. Names, timings and statuses stay visible, and payloads can be decrypted in the dashboard or CLI with access to the project.

Previously every run lived in iad1. In v5 Workflow infrastructure runs in every Vercel Function region, and each run is served from the region where it started. A run can be placed elsewhere by passing a region to start(), and existing v4 runs stay in iad1.

The release also adds run attributes for searchable context such as an order ID, which are stored as plaintext. Setting payload retention to experimental_retention: 0 deletes inputs, outputs and stream contents once a run completes or fails, while run metadata remains visible.

## Why it matters if you build agents

Agent builders on Vercel can keep sensitive model context, credentials and tool-call results encrypted in the event log without changing workflow code.

Runs now start in the region that serves the request, so teams with data residency needs can pin a run's data to a specific region with the region option.

Run attributes are plaintext, so they should not hold secrets.
