Introducing Dynamic Workflows: durable execution that follows the tenant
Cloudflare has introduced Dynamic Workflows, a new capability that enables durable execution for multi-tenant applications by allowing tenant-specific workflow code to be dynamically loaded and executed. This addresses the limitation of traditional workflows, which required predefined, static code bindings per deployment. Dynamic Workflows integrate with existing dynamic systems like Dynamic Workers and Durable Object Facets to support use cases such as AI-generated code, per-repository CI/CD pipelines, and agent-driven automation.
- ▪Dynamic Workflows allow tenant-specific code to be dynamically loaded and executed within Cloudflare's durable execution environment.
- ▪The solution bridges the gap between durable execution and dynamic deployment, enabling workflows to survive failures and resume after long delays.
- ▪It supports use cases like AI-generated business logic, per-tenant pipelines in CI/CD, and autonomous agent workflows.
- ▪The @cloudflare/dynamic-workflows library is a lightweight TypeScript module that routes workflow execution to tenant-specific code via a Worker Loader.
Opening excerpt (first ~120 words) tap to expand
Introducing Dynamic Workflows: durable execution that follows the tenant2026-05-01Dan LapidLuís Duarte9 min readWhen we first launched Workers eight years ago, it was a direct-to-developers platform. Over the years, we have expanded and scaled the ecosystem so that platforms could not only build on Workers directly, but they could also enable their customers to ship code to us through many multi-tenant applications. We now see on Workers: Applications where users describe what they want, and the AI writes the implementation. Multi-tenant SaaS where every customer's business logic is, at runtime, some TypeScript the platform has never seen before. Agents that write and run their own tools.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at The Cloudflare Blog .