Workflow Studio

Workflow Studio

Workflow Studio runs Workflow DevKit functions on a remote worker.

Your workflow functions and start(...) trigger routes stay the same. Remote execution is enabled by configuration, deployment, and one production reroute setting.

In production, you run that worker as a separate Node service on your own compute platform such as Fly.io, Railway, Render, EC2, GCP, Sevalla, or Cloudflare Containers.

What Workflow Studio provides

• Remote execution through a dedicated worker runtime.
• Cohesive deploy and rollback commands.
• Framework helpers for Next.js, Nitro, and SvelteKit.
• Ownership validation and diagnostics for remote routing.

Start here

1. Install workflow-studio and add remote execution config.
2. Deploy a separate worker service and start it with workflow-studio worker start.
3. Build and deploy your workflow artifact to that worker.
4. Set WORKFLOW_TARGET_WORLD=workflow-studio/world-remote on the application service.
5. Run ownership validation.

See Getting Started for the full setup.

Production reroute requirement

For unchanged start(...) paths to execute remotely, set this environment variable on the application service:

WORKFLOW_TARGET_WORLD=workflow-studio/world-remote

How execution works

1. You compile your workflow functions into JS bundles with workflow build.
2. You run workflow-studio deploy, which packages .well-known/workflow/v1/{flow.js,step.js,webhook.js}, uploads the artifact, and activates it.
3. Your app receives a request and calls start(...).
4. In remote mode, the request is routed through workflow-studio/world-remote and the worker executes the active deployment.
5. Workflow state still lives behind the existing World seam and event log.

Packages

Workflow Studio docs focus on three packages.

Quick links