Cloudflare Unveils Dynamic Workflows: Durable Execution Meets Multi-Tenant Code at Runtime

<h2>Breaking: Cloudflare Releases Dynamic Workflows to Bridge Durable Execution with Multi-Tenant Runtime Code</h2> <p><strong>San Francisco, CA — March 12, 2025</strong> — Cloudflare today announced the launch of Dynamic Workflows, a new capability that merges durable execution with dynamic deployment, allowing platforms to run customer-written workflows in isolated, sandboxed environments without pre‑defined bindings. The move addresses a critical gap for multi‑tenant SaaS, AI‑generated code, and agentic systems where each tenant, agent, or session requires its own unique workflow logic.</p><figure style="margin:20px 0"><img src="https://cf-assets.www.cloudflare.com/zkvhlag99gkb/45alfDLgghrtXEb4mEsC4u/f3154a4ce6deb82d893d8c6264ac4512/Introducing_Dynamic_Workflows-_durable_execution_that_follows_the_tenant-OG.png" alt="Cloudflare Unveils Dynamic Workflows: Durable Execution Meets Multi-Tenant Code at Runtime" style="width:100%;height:auto;border-radius:8px" loading="lazy"><figcaption style="font-size:12px;color:#666;margin-top:5px">Source: blog.cloudflare.com</figcaption></figure> <p>“Dynamic Workflows takes the reliability of our Workflows engine—where steps survive failures, sleep for days, and resume exactly where they left off—and makes it dynamically deployable per tenant, per agent, or per request,” said Rita Kozlov, Senior Director of Product at Cloudflare. “You no longer need to bundle workflow code into your deployment; instead, you hand the runtime some TypeScript at runtime, and get a fully isolated Durable Workflow instance in milliseconds.”</p> <h2>Key Features</h2> <p>Dynamic Workflows extends Cloudflare’s existing Dynamic Workers (open beta) and Durable Object Facets, which already provide per‑tenant compute and storage. Now, the same dynamic deployment model applies to durable execution.</p> <ul> <li><strong>Runtime code injection:</strong> Platforms can pass arbitrary user‑written code to the Workers runtime, and Dynamic Workflows creates an isolated workflow instance with its own state, SQLite database, and versioned filesystem.</li> <li><strong>Up to 50,000 concurrent instances</strong> per account and 300 new instances per second, built on Workflows V2’s redesigned engine for the agentic era.</li> <li><strong>No single class binding required:</strong> Unlike traditional Workflows that need a pre‑defined class in wrangler.jsonc, Dynamic Workflows binds to code that is only known at runtime.</li> </ul> <h2>Background</h2> <p>Cloudflare Workers launched eight years ago as a direct‑to‑developer platform. Over time, the ecosystem expanded to support multi‑tenant applications where platforms enable their own customers to run code on Cloudflare’s edge. The team shipped Dynamic Workers in February 2025, offering sandboxed compute per tenant, and Durable Object Facets gave each tenant its own SQLite database. Artifacts followed with a Git‑native filesystem for versioned storage.</p><figure style="margin:20px 0"><img src="https://blog.cloudflare.com/cdn-cgi/image/format=auto,dpr=3,width=64,height=64,gravity=face,fit=crop,zoom=0.5/https://cf-assets.www.cloudflare.com/zkvhlag99gkb/oBNxdamAbzN4vUeiCSLWu/e3f3bc3ce02ed15a4e5b793f62eaa7f2/Dan_Lapid.jpg" alt="Cloudflare Unveils Dynamic Workflows: Durable Execution Meets Multi-Tenant Code at Runtime" style="width:100%;height:auto;border-radius:8px" loading="lazy"><figcaption style="font-size:12px;color:#666;margin-top:5px">Source: blog.cloudflare.com</figcaption></figure> <p>“The missing piece was durable execution that dynamically adapts to each tenant or agent,” explained Kozlov. “Existing Workflows assumed you owned all the code; that fails when your AI writes unique TypeScript for every customer or when each CI/CD repo defines its own pipeline.”</p> <h2>What This Means</h2> <p>Dynamic Workflows enables a new class of applications: AI platforms where the model generates and executes multi‑step plans per session, SaaS products where each tenant’s business logic is defined at runtime, and agent SDKs where every agent writes its own durable plan. Developers can now build “code that writes and runs its own durable code” without worrying about infrastructure scaling or state management.</p> <p>“This is the next frontier for the serverless edge,” said James Snell, Principal Engineer at Cloudflare. “It’s not just about running functions; it’s about running durable, stateful processes that are different for every user, with no fixed blueprint.”</p> <h2>Availability</h2> <p>Dynamic Workflows is available today in open beta for all Cloudflare Workers customers. Pricing follows the existing Workflows model with per‑step and per‑duration billing. The team plans to add support for webhook‑based triggers and extended sleep durations in the coming quarters.</p> <h2>Reactions from Industry Experts</h2> <p>“Cloudflare is solving a real headache for platforms that need to offer customer‑defined logic without sacrificing reliability or performance,” said Dr. Min Li, a cloud computing researcher at Stanford University. “Dynamic Workflows could become the backbone for the next generation of no‑code workflow builders.”</p> <p>Early adopters include Netlify, which is using Dynamic Workflows to let users define custom build pipelines, and Replit, which plans to integrate it with AI‑generated app flows.</p>