Cloudflare shipped Dynamic Workflows. Multi-tenant agent platforms finally get durable per-tenant code.

Cloudflare released Dynamic Workflows on May 1, a 300-line MIT TypeScript library that routes durable execution to whichever tenant code needs it. It is the piece Cloudflare’s Agents Week 2026 was missing and a real answer to a year-old duct-tape problem.

The setup looks like this. An LLM wrote a workflow ten seconds ago. The platform has to run it. As Cloudflare’s Dan Lapid and Luís Duarte put it in the launch post, “the workflow is different for every tenant, every agent, every request. There is no single class to bind.” Static workflow bindings break under that load. Dynamic Workflows wraps each binding in metadata, hands execution to a Worker booted on demand by Workers Loader, and re-routes back to the same tenant code when the engine resumes after a sleep or crash. Plans move with the tenant. The platform guarantees they survive.

What problem this solves

Agent platforms have an awkward shape. The classic Cloudflare Workflow assumes the workflow class is part of your static deployment, baked into wrangler config. That works fine if you’re a single-tenant SaaS where every customer runs the same business logic. It falls over the moment one of your customers is a coding agent that just wrote its own multi-step plan and wants you to run it. As the Cloudflare post puts it, “the workflow is different for every tenant, every agent, every request. There is no single class to bind.”

The previous workaround was to split a single tenant workflow into a thousand boilerplate if branches inside one massive Worker, or to spin up a per-tenant deployment and pay the cost. Dynamic Workflows replaces both with the obvious thing: a WORKFLOWS binding inside the tenant’s own code, executed on a Dynamic Worker the host platform boots when needed.

The compute primitive is Dynamic Workers, which Cloudflare has been quietly turning into the runtime layer underneath everything agentic. Boot time is in single-digit milliseconds, isolates cache across steps, and the same machinery already handles Sandboxes for code execution and Workflows V2’s checkpointing. Pile up enough of those primitives and the platform starts looking like the substrate for the AWS Lambda generation of agent products.

How it fits the rest of Agents Week

Cloudflare’s April 17-20 Agents Week 2026 launched four pieces in a single morning: Agent Memory, Shared Dictionaries for compression, an Agent Readiness score for sites, and Redirects for AI Training. The follow-up week added Lightning Workers for compressed inference and a Stripe-linked flow that lets agents create Cloudflare accounts and buy domains.

Dynamic Workflows is the connective tissue. Agent Memory gives an agent state that persists between turns. Sandboxes give it a place to run untrusted code. Workers Loader gives it a runtime per tenant. None of those, on their own, gave you durable, restartable execution per tenant. Now you can layer all four into a coherent platform: a tenant’s agent runs in their own isolate, persists state to their own memory store, and survives a regional restart without dropping the plan it wrote two minutes ago.

What this means for you

If you’re building a multi-tenant agent platform on Cloudflare today, Dynamic Workflows lets you delete a chunk of your dispatch layer this week. The library is on npm under MIT, so vendor lock-in is the usual amount, not extra. It runs on Dynamic Workers, which is open-beta on the Workers Paid plan. Try it on a non-critical workflow first; the boot semantics are a real change from the static binding model and your debugging tools will need to follow tenant code into ephemeral isolates.

If you’re not on Cloudflare, take it as a signal. Vercel and Fly are both pushing in the same direction. Per-tenant durable execution is becoming the table-stakes primitive for agent infrastructure, in the same way that “function as a service” became table stakes for the previous platform generation. Pricing is the open question. Cloudflare’s bet is that 300 lines of TypeScript and a generous free tier on Workers gets developers to default to them while the others are still writing whitepapers. Watch the next Vercel keynote.