Worlds Ecosystem
Overview of official and community Workflow World implementations with compatibility status and performance benchmarks.
Workflow Worlds Ecosystem
The Workflow World is an interface that abstracts how workflows and steps communicate with the outside world. This page shows the compatibility status and performance of all available World implementations.
Filesystem-based world for local development and testing
PostgreSQL-based world for multi-host deployments
Production-ready world for Vercel platform deployments
Starter template for building Workflow DevKit Worlds
8 failing, 0 skipped
Turso/libSQL World for embedded or remote SQLite databases
1 failing, 0 skipped
MongoDB World using native driver
1 failing, 0 skipped
Redis World using BullMQ for queues, Redis Streams for output
1 failing, 0 skipped
Jazz Cloud world for local-first sync and real-time collaboration
30c0274What is a World?
A World implementation handles:
- Workflow Storage: Persisting workflow state and event logs
- Step Execution: Managing step function invocations
- Message Passing: Communication between workflow orchestrator and step functions
Choosing a World
| Use Case | Recommended World |
|---|---|
| Local development | Local World |
| Vercel deployment | Vercel World |
| Self-hosted with PostgreSQL | Postgres World |
| Edge/embedded databases | Turso World |
| High-throughput queues | Redis World |
Contributing a World
Want to build your own World implementation? Check out the World interface documentation and the reference implementations for guidance.
Community worlds are tested in CI against our E2E test suite. To add your world to this dashboard:
- Implement the World interface
- Publish to npm
- Open a PR to add your world to
worlds-manifest.json