Workflow Studio

Workflow Studio

Workflow Studio is an additive overlay package for Vercel Workflow. It enables remote compute deployment, composable topology configuration, and studio-oriented workflows without replacing your existing workflow package usage.

What is Workflow Studio?

Workflow Studio provides:

• Remote Compute: Execute workflows on dedicated workers instead of your app host
• Composable Topology: Mix and match queue backends, stream providers, and execution modes
• Framework Adapters: Convenient setup for Next.js, Nitro, and SvelteKit
• CLI Tools: Build, deploy, and manage workflow artifacts

The Overlay Model

Workflow Studio works as an overlay on top of the existing workflow package:

1. Your workflow functions and workflow imports stay unchanged
2. Workflow Studio adds optional configuration and CLI workflows
3. Runtime resolves compute configuration via workflow.config.* and environment fallbacks
4. Framework adapters are explicit wrappers that are no-op when remote compute is not configured
5. Queue backend, stream backend, and execution location are configured independently

Quick Navigation

Key Concepts

Remote Execution Mode

When execution.mode is set to 'remote', workflow operations are forwarded to a remote compute worker:

• start() calls route to remote world endpoints
• Queue publishing happens via the worker
• Stream operations are proxied
• Local queue handlers return guardrail errors

Active Deployment Pointer

Remote execution uses a single active deployment pointer that determines:

• Which deployment runs new workflows
• Which code executes for queue messages
• Where workflow state is stored

World Proxy Lane

Internal world operations use the world:proxy auth scope, separate from public trigger scopes.