Cloudflare AppsSearch apps/

All apps / AI

cloudflare-os

An open-source AI productivity environment where agents build and run sandboxed personal apps called Gadgets, with a capability-based security layer for external services. It runs on Workers, Durable Objects, and Dynamic Workers, and can be deployed to a visitor-controlled Cloudflare account or run locally via wrangler.

Stars
11,804
Forks
1,462
License
Apache-2.0
Category
AI
Latest push
Published
Refreshed
Updated

Review

Agent chat beside an AI-generated slide deck in a Cloudflare OS workspace
A Q3 planning workspace with a deck the agent built. Image from the Cloudflare OS repo (Apache-2.0).

What the workspace does

Cloudflare OS gives every employee a browser workspace whose agent is grounded in skills and context the company curates. Ask for a customer briefing and it researches, then writes the document, slides or spreadsheet, using the tools you connect.

The apps it builds are Gadgets. Each one is a private instance for a person or team, sandboxed, shareable like a document and editable by asking the agent. Outside services go through a Gatekeeper, a Worker per service that holds the OAuth credential and scopes access to named resources. It logs every read and simulates side effects so approvals can be batched later. Cloudflare ran a first version internally from May 2026, and the launch post says thousands of employees use it daily.

What running it costs

There is no per-seat price to replace, because Cloudflare’s managed version is a waitlist with no published price. Self-hosting runs on a Workers Paid account at a $5 monthly minimum, which includes Durable Objects usage. Model spend is separate and bills to your own Cloudflare credits through AI Gateway: with ENABLE_CLOUDFLARE_LIMITS set, each user gets 100 LLM calls a day and then needs a connected account holding at least $2 of credit, or the agent stops.

What Workers ships, and what the repo writes

Every workspace is a Durable Object, and OverseerDurableObject supervises each Gadget as a Durable Object Facet, so a Gadget’s SQLite database is one its supervisor’s code cannot read. Gadget server code runs in a Dynamic Worker with outbound networking disabled and reaches services only through bindings the user granted. Client code runs in a sandboxed iframe and talks to its server over Cap’n Web RPC.

Workers supplies those primitives and stops there. Routing, sign-in, admin settings, blueprint storage, gatekeeper packaging, the interface and the policy on what an agent may do are all application code here, on a backend that binds the Worker Loader, KV, R2 and Browser Rendering.

What the repo packages

The monorepo holds 37 packages and 2,408 tracked files, with packages/workshop-backend as the kernel and packages/workshop-frontend as the shell. It ships 22 gatekeeper packages, 14 with setup instructions, from GitHub and Google to Slack, Microsoft 365 and PagerDuty, plus starter blueprints, an eval harness and integration tests. You can start it with pnpm run-local on workerd, a guided deploy at os.cloudflare.app/deploy, or the starter repo for a config-and-pipeline deployment. Sign-in takes a username and password, Cloudflare Access, or gatekeeper OAuth when AUTH_GATEKEEPERS lists the vendor.

Who’s behind it

Cloudflare’s Workers team built it, and the architect is Kenton Varda, a Distinguished Engineer there who has led Workers since he joined. He describes Cloudflare OS as a remake of Sandstorm.io, the startup he founded in 2015, built this time on Workers.

It was open sourced in August 2026 under Apache-2.0. By Nov. 12 the core repo showed 11,774 stars, 1,454 forks and 30 contributors, with commits through the day before and no releases or tags.

Where it falls short

  • The project calls itself early access. This repo is v2, a rewrite “in a state of heavy development” with “many rough edges”.
  • Off-Cloudflare deployment is unwritten. The instructions for running it on your own servers under workerd read COMING SOON, so today it runs in your Cloudflare account or locally.
  • Upstream is closed by policy. The project is not seeking outside contributions and closes pull requests beyond a dozen or so lines, so a fix you need belongs in your fork.
  • Gatekeepers carry the setup cost. Each service needs its own OAuth app registered with the provider, which the README says providers intentionally do not make easy.
  • There are no versions. Upgrades follow commits, so a change you did not ask for arrives with the next pull.

Verdict

If your team already runs on Cloudflare, wants company-wide agents with per-user apps, and will spend the effort on gatekeepers and internal context rather than on writing a platform, deploy it into your own account. If you want a priced product with support and an upgrade path, wait for the managed one.

Based on reading the source at commit 3441200 and public research, .

How these reviews are made

Research and source context

This profile is compiled from public repository data. Repository details were captured and the profile was last researched .

More in AI