The Local World is bundled with workflow and used automatically during local development. No installation or configuration required.
To explicitly use the local world in any environment, set the environment variable:
WORKFLOW_TARGET_WORLD=localObservability
The workflow CLI uses the local world by default. Running these commands inside your workflow project will show your local development workflows:
# List recent workflow runs
npx workflow inspect runs
# Launch the web UI
npx workflow webLearn more in the Observability documentation.
Testing & Performance
E2E Tests
Spec compliance is tested against Next.js (Turbopack) built in production mode and started with `next start`. View CI run →
View comprehensive E2E test results against all frameworks/configurations
Benchmarks
Click on a benchmark to view performance history over the last 30 commits.
| Benchmark | Time | Min | Max | Samples | |
|---|---|---|---|---|---|
Promise.all with 10 concurrent steps | 1.55s | 1.50s | 1.69s | 15 | |
Promise.all with 25 concurrent steps | 3.16s | 3.06s | 3.35s | 8 | |
Promise.all with 50 concurrent steps | 8.95s | 8.70s | 9.45s | 4 | |
Promise.race with 10 concurrent steps | 1.57s | 1.48s | 1.65s | 15 | |
Promise.race with 25 concurrent steps | 3.15s | 3.04s | 3.24s | 8 | |
Promise.race with 50 concurrent steps | 9.30s | 9.23s | 9.43s | 3 | |
workflow with 1 step | 1.13s | 1.12s | 1.17s | 10 | |
workflow with 10 concurrent data payload steps (10KB) | 623ms | 467ms | 1.26s | 59 | |
workflow with 10 sequential data payload steps (10KB) | 1.02s | 986ms | 1.07s | 34 | |
workflow with 10 sequential steps | 11.01s | 11.00s | 11.03s | 3 | |
workflow with 25 concurrent data payload steps (10KB) | 2.59s | 2.37s | 2.93s | 30 | |
workflow with 25 sequential data payload steps (10KB) | 3.09s | 3.01s | 3.15s | 23 | |
workflow with 25 sequential steps | 15.07s | 15.03s | 15.11s | 4 | |
workflow with 50 concurrent data payload steps (10KB) | 11.55s | 11.14s | 11.68s | 10 | |
workflow with 50 sequential data payload steps (10KB) | 9.43s | 9.20s | 9.70s | 12 | |
workflow with 50 sequential steps | 16.98s | 16.87s | 17.05s | 6 | |
workflow with no steps | 44ms | 38ms | 64ms | 10 |
Stream Benchmarks
| Benchmark | Time | TTFB | Slurp | Min | Max | Samples | |
|---|---|---|---|---|---|---|---|
| 10 parallel streams (1MB each) | 1.31s | 2.02s | 0ms | 1.23s | 1.37s | 30 | |
| fan-out fan-in 10 streams (1MB each) | 3.73s | 4.10s | 0ms | 3.46s | 4.05s | 15 | |
| stream pipeline with 5 transform steps (1MB) | 765ms | 1.01s | 10ms | 730ms | 873ms | 59 | |
| workflow with stream | 214ms | 1.00s | 13ms | 209ms | 230ms | 10 |
Last updated: 4/8/2026, 1:35:19 AM · Commit: a261b21
Configuration
The local world works with zero configuration, but you can customize behavior through environment variables or programmatically via createLocalWorld().
WORKFLOW_LOCAL_DATA_DIR
Directory for storing workflow data as JSON files. Default: .workflow-data/
PORT
The application dev server port. Used to enqueue steps and workflows. Default: auto-detected
WORKFLOW_LOCAL_BASE_URL
Full base URL override for HTTPS or custom hostnames. Default: http://localhost:{port}
Port resolution priority: baseUrl > port > PORT > auto-detected
WORKFLOW_LOCAL_QUEUE_CONCURRENCY
Maximum number of concurrent queue workers. Default: 100
Programmatic configuration
import { createLocalWorld } from "@workflow/world-local";
const world = createLocalWorld({
dataDir: "./custom-workflow-data",
port: 5173,
// baseUrl overrides port if set
baseUrl: "https://local.example.com:3000",
});Limitations
The local world is designed for development, not production:
- In-memory queue - Steps are queued in memory and do not persist across server restarts
- Filesystem storage - Data is stored in local JSON files
- Single instance - Cannot handle distributed deployments
- No authentication - Suitable only for local development
For production deployments, use the Vercel World or Postgres World.