<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/workflow-sdk-5-faster-steps-per-run-encryption-regional-runs-5sqakmmm2" -->

---
title: Workflow SDK 5: faster steps, per-run encryption,...
description: Vercel released Workflow SDK 5 with major speed, security and regional improvements. Step-to-step overhead dropped from 618ms to 109ms, and a 1,020-step run...
canonical: https://daily.dev/posts/workflow-sdk-5-faster-steps-per-run-encryption-regional-runs-5sqakmmm2
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Workflow SDK 5: faster steps, per-run encryption, regional runs | daily.dev
og:description: Vercel released Workflow SDK 5 with major speed, security and regional improvements. Step-to-step overhead dropped from 618ms to 109ms, and a 1,020-step run...
og:url: https://daily.dev/posts/workflow-sdk-5-faster-steps-per-run-encryption-regional-runs-5sqakmmm2
og:image: https://api.daily.dev/og/posts/5SQakMMm2.png
og:image:alt: Workflow SDK 5: faster steps, per-run encryption, regional runs
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow SDK 5: faster steps, per-run encryption, regional runs

**[Collections](https://daily.dev/sources/collections)** · 2 min read · 0 upvotes · 1 comments

## Summary

Vercel released Workflow SDK 5 with major speed, security and regional improvements. Step-to-step overhead dropped from 618ms to 109ms, and a 1,020-step run finished in 3 minutes instead of 21. Benchmark gains overall range from 1.6x to 25x. Streaming now defaults to WebSockets, and in one benchmark a 52.4-second response took 53.5 seconds, down from 226 seconds. Every payload is encrypted end to end with AES-256-GCM using a per-run key, runs can now live in any Vercel Function region instead of only iad1, the durability log is now reusable as a standalone project called durable-harness, and a Python SDK is in beta.

## Content

Vercel has released Workflow SDK 5. @rauchg calls it, along with Vercel Workflows, "a monumental step forward for agents." The numbers back up at least part of that.

## Speed

The biggest change is how quickly runs move from one step to the next. In a five-step benchmark, step-to-step overhead dropped from 618ms to 109ms. A 1,020-step run finished in 3 minutes instead of 21. Across benchmarks the improvements range from 1.6x to 25x.

Streaming on the Vercel World now defaults to WebSockets. In one benchmark, delivering a 52.4-second response took 53.5 seconds, down from 226 seconds.

## Encryption

Every payload is now encrypted end to end with AES-256-GCM, using a separate key for each run. On Vercel it needs no configuration.

## Regional runs

Runs used to live only in iad1. They can now live in any Vercel Function region, which cuts cross-region latency.

## Reliability and debugging

Rauch says the system has been proven at massive scale, with many subtle details ironed out and many disaster-recovery scenarios exercised. The release also adds new debugging tools.

## durable-harness

The underlying durability log is now reusable for any agent harness. That work became a project called `durable-harness`.

## Python

A Python SDK is now in beta.

## Questions this post answers

### How much faster is Vercel Workflow SDK 5 compared to the previous version?

Step-to-step overhead dropped from 618ms to 109ms in a five-step benchmark, and a 1,020-step run that took 21 minutes now finishes in 3 minutes. Across benchmarks, the reported improvements range from 1.6x to 25x faster execution.

_Teams running long agent workflows can track performance changes like this on daily.dev._

### Does Vercel Workflow SDK 5 encrypt workflow run data?

Yes, every payload is encrypted end to end with AES-256-GCM, using a separate encryption key for each individual run. On Vercel's platform this encryption requires no manual configuration from the developer.

_Developers evaluating workflow security guarantees can follow updates like this on daily.dev._

### Can Vercel Workflow SDK runs execute outside the iad1 region?

Yes, runs that previously lived only in the iad1 region can now run in any Vercel Function region, reducing cross-region latency for geographically distributed applications.

_Anyone optimizing latency across regions can keep up with platform changes like this on daily.dev._

## Community take

How the wider developer community reacted, aggregated from 1 discussion and 83 comments across x (as of 2026-11-13).

**TL;DR:** Reaction is largely enthusiastic, with the biggest excitement around cutting inter-step latency for long agent runs and making the durability log reusable across harnesses, while many replies press for details on crash recovery, idempotency, and whether encryption extends to logs and retries.

**Sentiment:** 58% positive · 30% mixed · 12% skeptical

**The case for**

- Reducing time between steps is seen as the change that matters most for making long multi-step agent runs feel usable.
- Making the durability log reusable as a standalone, framework-agnostic project is viewed as the standout feature, saving teams from rebuilding retry/state logic themselves.
- Encryption by default is welcomed as a sensible security baseline, with some saying it helps clear internal security reviews.

**The pushback**

- Several ask whether a crashed step replays a side effect (like a charge or email) twice instead of resuming cleanly, calling this unproven.
- Some want clarity on whether encryption actually covers step inputs/outputs in logs and retries, not just headline payloads.
- A few note durability only proves what ran, not why a branch was chosen, and worry about serialization/state overhead as runs grow longer.

**By community**

- x (positive): Most replies praise the latency cuts and reusable durability log, though many press for specifics on crash recovery and encryption coverage.

**Hottest debate:** Whether replayed/resumed steps after a crash avoid duplicating side effects (like double charges or duplicate emails) or just rerun from scratch.

**Open questions**

- If a step crashes right after a side effect (charge, email, tool call, git push), does replay know not to repeat it?
- Does encryption cover step inputs/outputs persisted in logs and during retries, and who holds the keys?
- How does durable-harness work with agent harnesses not built on the AI SDK, like OpenAI Agents SDK or custom loops?
- Does a run stay cheap while sleeping for a long human approval wait?
- How much of the latency improvement comes from the durability log changes versus added encryption overhead?

**Highlights**

> @rauchg for agents running real businesses most of the wall clock is waiting on a human yes. curious what a run costs while it sleeps 3 days on an approval
> — [lautaroseth on x](https://x.com/lautaroseth/status/2121282693631803861)

> @rauchg the log is only as good as the retry boundary, if a failed call reruns the whole turn the durable log just replays the mistake faster
> — [MaximalVibe on x](https://x.com/MaximalVibe/status/2121318548652089740)

> @rauchg the durability log is the underrated part. every step every agent took, in one place. thats the dataset people will want to query later
> — [marchoeffl on x · 4 points](https://x.com/marchoeffl/status/2121313759297991164)

> @rauchg encrypted payloads by default is the part i'd want details on. who holds the keys, and do step outputs stay encrypted in logs and retries too? that's usually where tokens end up leaking
> — [Sagarvd01 on x](https://x.com/Sagarvd01/status/2121279277417332852)

> @rauchg durability makes the step replayable, not the decision. a replayed model call is a fresh sample, so the log proves what ran and never why that branch got picked.
> — [johnroodepic on x](https://x.com/johnroodepic/status/2121281758058696869)

**Source threads**

- [x](https://x.com/rauchg/status/2121277727940776114) · 0 points · 83 comments

## Community discussion

Top comments from developers on daily.dev.

**@pdfopsdev** · 0 upvotes

> 109ms step overhead is huge if you're chaining hundreds of steps, that's minutes vs feeling broken. wonder how the per-run AES key plays with replay though, does inspecting an old run mean a fresh KMS call every time?

## Similar posts on daily.dev

- [A new programming model for durable execution](https://daily.dev/posts/a-new-programming-model-for-durable-execution-8hk6zrkca) · Vercel · 0 upvotes · 0 comments
- [End-to-end encryption for Vercel Workflow](https://daily.dev/posts/end-to-end-encryption-for-vercel-workflow-0r6jv9cyy) · Vercel · 0 upvotes · 0 comments
- [Durable AI Workflows 2026: Inngest, Trigger.dev, Vercel Workflow](https://daily.dev/posts/durable-ai-workflows-2026-inngest-trigger-dev-vercel-workflow-un2tgyyqs) · Alex CloudStar · 0 upvotes · 0 comments
- [Deployment step now 15% faster](https://daily.dev/posts/deployment-step-now-15-faster-thiazmjbv) · Vercel · 1 upvotes · 0 comments

---

Tags: [#encryption](https://daily.dev/tags/encryption), [#vercel](https://daily.dev/tags/vercel)

[View this post on daily.dev](https://daily.dev/posts/workflow-sdk-5-faster-steps-per-run-encryption-regional-runs-5sqakmmm2)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Workflow SDK 5: faster steps, per-run encryption, regional runs","url":"https://daily.dev/posts/workflow-sdk-5-faster-steps-per-run-encryption-regional-runs-5sqakmmm2","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/workflow-sdk-5-faster-steps-per-run-encryption-regional-runs-5sqakmmm2"},"datePublished":"2026-11-13T16:27:43.667Z","dateModified":"2026-11-13T20:58:48.365Z","description":"Vercel released Workflow SDK 5 with major speed, security and regional improvements. Step-to-step overhead dropped from 618ms to 109ms, and a 1,020-step run...","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/workflow-sdk-5-faster-steps-per-run-encryption-regional-runs-5sqakmmm2","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"encryption,vercel","timeRequired":"PT2M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"Workflow SDK 5: faster steps, per-run encryption, regional runs"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/workflow-sdk-5-faster-steps-per-run-encryption-regional-runs-5sqakmmm2","comment":[{"@type":"Comment","text":"109ms step overhead is huge if you’re chaining hundreds of steps, that’s minutes vs feeling broken. wonder how the per-run AES key plays with replay though, does inspecting an old run mean a fresh KMS call every time?","datePublished":"2026-11-13T18:08:09.748Z","url":"https://daily.dev/posts/5SQakMMm2#c-tnc1e76Q7","author":{"@type":"Person","name":"PDFops","url":"https://daily.dev/pdfopsdev","image":"https://media.daily.dev/image/upload/s---8isRBKc--/f_auto/v1782922291/avatars/avatar_orjMeK8QKaaVZwGq7ScPz?_a=BAMAMicg0"}}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/workflow-sdk-5-faster-steps-per-run-encryption-regional-runs-5sqakmmm2#faq","mainEntity":[{"@type":"Question","name":"How much faster is Vercel Workflow SDK 5 compared to the previous version?","acceptedAnswer":{"@type":"Answer","text":"Step-to-step overhead dropped from 618ms to 109ms in a five-step benchmark, and a 1,020-step run that took 21 minutes now finishes in 3 minutes. Across benchmarks, the reported improvements range from 1.6x to 25x faster execution. Teams running long agent workflows can track performance changes like this on daily.dev."}},{"@type":"Question","name":"Does Vercel Workflow SDK 5 encrypt workflow run data?","acceptedAnswer":{"@type":"Answer","text":"Yes, every payload is encrypted end to end with AES-256-GCM, using a separate encryption key for each individual run. On Vercel's platform this encryption requires no manual configuration from the developer. Developers evaluating workflow security guarantees can follow updates like this on daily.dev."}},{"@type":"Question","name":"Can Vercel Workflow SDK runs execute outside the iad1 region?","acceptedAnswer":{"@type":"Answer","text":"Yes, runs that previously lived only in the iad1 region can now run in any Vercel Function region, reducing cross-region latency for geographically distributed applications. Anyone optimizing latency across regions can keep up with platform changes like this on daily.dev."}}]}
```

