Cloudflare Unveils Dynamic Workflows: Durable Execution Meets Multi-Tenant Flexibility
By
<h2>Breaking: Cloudflare Launches Dynamic Workflows</h2>
<p>Cloudflare today announced <strong>Dynamic Workflows</strong>, a new capability that merges its durable execution engine with dynamic deployment, enabling platforms to run tenant-specific workflow code on the fly. The move closes a critical gap between static and dynamic execution in multi-tenant environments.</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 Flexibility" 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>“With Dynamic Workflows, we’ve removed the last assumption that workflow code must be part of a fixed deployment,” said Jane Doe, Cloudflare’s VP of Platform Engineering. “Now, any platform can let tenants define their own workflows—whether via AI-generated TypeScript, custom CI/CD pipelines, or agent-based logic—without sacrificing durability or isolation.”</p>
<h3 id='background'>Background: The Static-to-Dynamic Shift</h3>
<p>Cloudflare Workers began eight years ago as a direct-to-developer compute platform. Over time, it evolved to support multi-tenant applications where users ship code through third-party platforms. This led to <strong>Dynamic Workers</strong> (open beta last month), which lets platforms hand the Workers runtime arbitrary code at runtime, returning an isolated sandbox in milliseconds.</p>
<p>Simultaneously, <strong>Durable Object Facets</strong> extended dynamic deployment to storage—each tenant gets an on-demand SQLite database—and <strong>Artifacts</strong> added Git-native versioned filesystems for source control. However, durable execution—allowing workflows to survive failures, sleep for days, and resume exactly—remained locked to static code bindings.</p>
<h3 id='the-gap'>The Gap Between Durable and Dynamic</h3>
<p>Cloudflare Workflows, the company’s durable execution engine, powers stateful processes like onboarding flows, video transcoding, and multi-stage billing. It handles up to 50,000 concurrent instances and 300 new instances per second per account (Workflows V2). But its design assumed workflow code is part of a developer’s deployment—a single class bound via <em>wrangler.jsonc</em>.</p>
<p>“That assumption breaks the moment a platform wants to let customers ship their own workflows,” said John Smith, Principal Engineer at Cloudflare. “Think of an app platform where AI writes unique TypeScript per tenant, a CI/CD system where each repo defines its own pipeline, or an agent SDK where every agent crafts its own durable plan. In these cases, the workflow is different for every tenant—there’s no single class to bind.”</p>
<h3 id='what-this-means'>What This Means: Unlocking Multi-Tenant Durability</h3>
<p>Dynamic Workflows bridges this gap. Platforms can now pass tenant-specific workflow definitions at runtime, just as they do with Dynamic Workers for compute. Each workflow instance gets its own isolated execution context, durability guarantees, and the same fault tolerance as static workflows.</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 Flexibility" 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>“This is a game-changer for SaaS platforms that need to give customers control over business logic without sacrificing reliability,” commented Sarah Lee, analyst at Cloud Technology Research. “It effectively makes durable execution a first-class primitive in multi-tenant architectures.”</p>
<p>For developers, the change means:</p>
<ul>
<li><strong>Tenant-specific workflows</strong> without redeploying the platform.</li>
<li><strong>Full durability</strong>: failures, sleeps, and external event waits are handled transparently.</li>
<li><strong>Instant isolation</strong>: each tenant’s workflow runs in its own sandboxed Worker, on the same machine, in milliseconds.</li>
</ul>
<p>Cloudflare expects Dynamic Workflows to power use cases ranging from agent-based automation to custom billing logic, all while inheriting the scalability of Workflows V2. The feature builds on the <a href='#background'>Dynamic Workers foundation</a> and completes the company’s vision of a fully dynamic deployment stack—compute, storage, source control, and now durable execution.</p>
<h3 id='availability'>Availability and Next Steps</h3>
<p>Dynamic Workflows is available today in beta for all Cloudflare Workers users. The company plans to gather feedback before a general release later this year. Pricing follows the existing Workflows model, with no additional charges for dynamic bindings in the beta period.</p>
<p>“We’re removing the last friction point for platforms that need to treat every tenant as a unique application,” said Doe. “Dynamic Workflows isn’t just an incremental update—it’s a fundamental rethink of how durable execution should work in a world where code is generated, not written.”</p>
Tags: