Introducing Dynamic Workflows: durable execution that follows the tenant

Dynamic Workflows combines durably executing workflows with dynamic tenant-specific deployment, enabling a single Worker to dispatch runs to each tenant’s own code while preserving state across hours, days or deploys. The feature sits on top of Cloudflare Workflows and Dynamic Workers, letting tenants ship their own workflow code without the platform needing to know its details in advance.

A small TypeScript library, roughly 300 lines, routes create() calls to a tenant’s code and ensures the Workflows engine calls back into the correct tenant when needed. Tenants write normal Workflows bindings, while the Worker Loader handles per-tenant routing, envelope wrapping and RPC stubs so the flow remains seamless. The approach enables per-tenant, on-demand sandboxes that boot in single-digit milliseconds, with idle tenants costing essentially nothing thanks to isolate-level multi-tenancy.

Cloudflare expects other bindings to gain dynamic counterparts in time, so developers can offer multi-tenant capabilities across queues, databases, AI bindings and more, all with zero provisioning overhead. According to Cloudflare, the system can dramatically reduce the floor for multi-tenant platforms, enabling tens of millions of active tenants without a corresponding rise in idle costs.