Cloudflare open sourced an agent workspace, and some new Workers primitives with it
Dynamic Workers, Durable Object Facets, a SQLite database per app instance, and a Gatekeeper Worker sitting in front of every internal system.
The product announcement buries the interesting part: the runtime primitives underneath it.
Cloudflare announced and open sourced Cloudflare OS on August 5, 2026, a browser-based agent workspace with a micro-app platform attached, fronted publicly by Kenton Varda, who built Workers. The announcement post is vague enough that the top Hacker News comments argue about what the product actually is, and Varda conceded in the thread that the framing was hard. The infrastructure underneath it is not vague at all, and it is the part worth reading.
The primitives
Apps in Cloudflare OS, which it calls Gadgets, run as Dynamic Workers instantiated as Durable Object Facets, with each app instance getting its own SQLite database. That is a meaningfully different unit of isolation from what most Workers code does today: instead of one Worker with shared state behind it, you get a per-instance object with its own storage, created on demand. If you already build on Durable Objects, these are the primitives to go read about, independent of whether the workspace product interests you at all.
Gatekeepers are the security model
Every agent access to an internal system goes through a Gatekeeper, a service-specific Worker that mediates the call. The reasoning is straightforward once stated: if you let non-technical users point an AI at their own tooling and modify apps, you have created an enormous number of paths into internal systems, and the mitigation is to make every one of those paths run through code you wrote rather than through credentials the agent holds. It is a familiar pattern, a policy proxy per service, applied to the specific problem of agents with too much reach.
What ships today, and what does not
The core is on GitHub now. A fully managed version inside the Cloudflare dashboard, container support, and Slack and chat integrations are announced but not shipped, and there is no pricing. Cloudflare says an internal version has been used across every function of the company since May 2026, which is its own unaudited number. On the lock-in question that dominated the thread, Varda confirmed directly that the whole thing self-hosts on workerd, the open source runtime, Durable Objects included.
Why a build studio cares
This one is close to home. Our own /handoff tool runs on a Cloudflare Worker with a Durable Object per share session, so Dynamic Workers and Facets are not abstract to us, they are a possible refactor. A per-instance object with its own SQLite is very close to what we hand-rolled for signaling rooms. We are not adopting the workspace product; we are going to read the primitives and see whether the next Worker we write should use them.
Next step: read Cloudflare's announcement and the Hacker News thread, where Varda answers the self-hosting question directly. If you want something built on Workers and Durable Objects by people who already run them in production, write to us at hello@gattyworks.com.