Durable Objects in Dynamic Workers: Give each AI-generated app its own database

Durable Objects in Dynamic Workers lets you give each AI-generated app its own database by dynamically loading and instantiating a Durable Object class, with a SQLite database attached that lives on local disk. The system pairs a normal Durable Object namespace, written by you, with a Dynamic Worker that loads the app code, allowing the app to run as a facet of your object; each facet has its own SQLite database, separate from the supervisor’s, but stored together within the same overall Durable Object.

This approach enables a supervisor pattern where requests first go to your code for logistics—like logging, observability, and billing—before forwarding into the agent’s code, which can itself implement a Durable Object class. The example shows an AppRunner Durable Object that stores and loads app code, loads the Dynamic Worker, and forwards requests to a facet named "app" that runs the exported App class; the AppRunner’s storage and the facet’s storage remain isolated.

Facets are available in open beta to users on the Workers Paid plan, and the post provides a complete code sample and wrangler configuration to run locally. Published on 13 April 2026.