Vercel’s Workflow SDK Goes Native Inside Nitro v3
Vercel shipped the Workflow SDK native Nitro v3 integration in beta on June 13, 2026. The update gives developers a cleaner, more efficient way to handle long-running workflow steps inside Nitro-based apps.
Previously, Workflow SDK steps ran in a separate bundle, cut off from the rest of the app. Now, steps execute inside the same bundled runtime as the broader Nitro app. That shared context matters. Nitro’s native APIs, including useStorage(), work directly inside "use step" functions without any extra configuration.
The change also delivers real performance gains. Nitro now bundles workflow routes as part of the standard app build. It traces dependencies automatically and tree-shakes unused code. Consequently, builds run faster and output bundles stay smaller, containing only the code that actually executes.
On top of that, the Nitro dev server now serves a built-in workflow web UI at workflow. Developers can open that URL to inspect, monitor, and debug workflow runs in real time. That addition alone removes a lot of friction for anyone managing complex, multi-step processes.
Getting started takes minimal effort. Vercel’s documentation covers the full setup in the Workflow SDK on Nitro guide. The integration sits within Vercel’s broader Workflow product, which targets long-running tasks at scale.
For Nuxt and Nitro developers especially, this Workflow SDK native Nitro v3 integration removes a real barrier. Shared runtimes, tighter bundling, and a live debug UI make it straightforward to build and maintain reliable workflow logic alongside the rest of an application’s server code.
