The best workflow engine is a programming language
Vercel just shipped a workflow engine that feels like writing normal code—no DAG files, no infrastructure preamble, no version rot. Here's why that matters.
Why it matters
Workflow SDK abstracts away the operational complexity of durable execution (versioning, infrastructure setup, step overhead) by treating workflows as ordinary sequential code running on infrastructure you already have. For practitioners building stateful systems, this is a significant DX and operational efficiency play—no more choosing between Temporal's power and its complexity tax.
The key facts
7 to knowWorkflow SDK v5 (beta) delivers 5x performance improvement with no API change
Single 'use workflow' and 'use step' directives replace explicit DAGs, signals, queries, updates
Versioning pinned to immutable deployments—runs execute against the exact code version they started on, eliminating in-flight breakage
Open-source, Apache-licensed client-side library; 'World' abstraction lets you swap Postgres, Kafka, Redis, SQS, etc. without changing workflow code
Vercel Workflow Server is stateless CRUD API, not an orchestrator—no bespoke control plane to self-host
Inspired by DBOS (open-source durable execution); no worker fleet required
Published Aug 27, 2026; hiring announced for Workflow team
Go to the source
Vercel Blogvercel.com
Publisher excerpt: The idea of orchestrating long-running, stateful logic on top of unreliable, stateless infrastructure isn't new. We've had message queues, job runners, microservice choreographies, and full-blown workflow engines for a long time. What we never had was a version of it that felt good to write. I'd…