wikis / Cloudflare OS / wiki / concepts / cloudflare-os-overview.md view as markdown report a mistake

Cloudflare OS Overview

Definition

Cloudflare OS is an open-source "operating system" for AI productivity, originally built for internal use at Cloudflare, where it is used daily by a large portion of the workforce across engineering, sales, and other functions (raw/github_doc-readme-md.md). It is not a traditional computer operating system. The README explicitly says the term "operating system" is used in two senses: (1) an operating system for the company to be productive with AI in a way that is safe, "so that the security team can sleep at night," and (2) an operating system for AI workloads, analogous to how a traditional OS manages compute workloads (raw/github_doc-readme-md.md). The project is open source specifically so other organizations can copy and customize it — the stated goal is not that a company runs "Cloudflare OS" but that it makes it "Your Company OS" (raw/github_doc-readme-md.md).

How It Works

Cloudflare OS provides three things, referred to in this KB as its three pillars (raw/github_doc-readme-md.md):

1. An agent chat UI where users ask agents to do tasks, preloaded with knowledge about how the company operates. See agent chat and company knowledge.
2. Sandboxed application development — asking agents to build "gadgets" (small personal apps) and safely sharing what's built with others. See gadgets and sharing.
3. A security framework called Gatekeepers, which applies guardrails to both agents and apps so that non-technical users can safely "go nuts" without anything bad happening. See gatekeepers.

The Cloudflare blog announcement frames the same three pillars slightly differently as: an agent workspace grounded in company context and skills with an isolated runtime for agents to write and run code; a new security and governance framework for safe access to internal data and services; and a platform for personal, modifiable apps that people can build, share, and continue changing (raw/web_community-cloudflare-os-an-open-platform-for-agents-apps-and-work-the-.md). These map directly onto the README's agent chat / Gatekeepers / gadgets framing.

Cloudflare OS is described in the README as "actually analogous to an operating system on a technical level," with an explicit component-to-component mapping: packages/workshop-backend is the kernel, packages/gatekeeper-* are device drivers, packages/workshop-frontend is the shell, gadgets are processes, blueprints are executables, and agents are called out as something traditional OSes lack an analog for (raw/github_doc-readme-md.md). See architecture for the technical substrate this runs on.

The blog post adds historical context: Cloudflare gave every employee access to a first version of Cloudflare OS in May of the release year, and thousands of people across every function used it daily for documents, slides, automating repeatable tasks, and building small apps. That first version's limitations — static apps rather than live software connected to internal systems, and a security gap where MCP access told the platform which tools an agent could call but not which underlying resources it had observed — motivated rebuilding the security and governance model into the platform itself rather than leaving it to each app or agent builder (raw/web_community-cloudflare-os-an-open-platform-for-agents-apps-and-work-the-.md).

Key Parameters

• The two senses of "operating system": company-productivity-and-safety OS vs. AI-workload-management OS (raw/github_doc-readme-md.md).
• Self-host thesis: deploy into your own Cloudflare account, connect your own internal systems and Access policies, and customize the interface and add internal Gatekeepers "without changing the core product" — the goal is "Your Company OS," not adopting Cloudflare's own instance (raw/github_doc-readme-md.md; raw/web_community-cloudflare-os-an-open-platform-for-agents-apps-and-work-the-.md).
• Two repositories are released: the Cloudflare OS core, and an example deployment repo reflecting how Cloudflare runs it internally, which consumes the core without patching it (raw/web_community-cloudflare-os-an-open-platform-for-agents-apps-and-work-the-.md). The README separately points to a cloudflare-os-starter repo for more sophisticated deployment with custom gatekeepers/code changes (raw/github_doc-readme-md.md).
• v2, August 2026 early access: this repository is described as "actually version 2, a complete rewrite" that took what was learned from v1 and put it on a new foundation. As of the August 2026 release it is "very capable, but still has many rough edges" — an explicit early-access disclaimer (raw/github_doc-readme-md.md).
• Built by the Workers team, on Workers: Cloudflare OS is built by the people who built Cloudflare Workers, and makes heavy use of Durable Objects, Dynamic Workers, and Facets — several of which were added to the Workers Runtime specifically to support this project (raw/github_doc-readme-md.md). See architecture.

When To Use

• Evaluating whether to adopt Cloudflare OS as an internal AI platform for a company (not just for individual coding), where both "safe for the security team" and "flexible enough for non-technical users to build tools" both matter.
• Understanding the product's own self-description before diving into any specific mechanism (gadgets, blueprints, Gatekeepers) — this page is the entry point the other five pages in this batch link back to.
• As of the August 2026 snapshot, treat it as early access: expect rough edges, and expect some documented plans (e.g. architecture's pi-ai migration, multi-gadget workspaces) describing in-flight or recently-landed work rather than long-stable behavior.

Risks & Pitfalls

• The "early access" warning is explicit and should not be glossed over: the README states there are "many rough edges" as of the August 2026 release (raw/github_doc-readme-md.md).
• AGENTS.md describes the project as "building a platform for 'vibe coded' personal applications and AI agents that run inside a strong sandbox" (raw/github_doc-agents-md.md) — the security model (Gatekeepers, capability-based access) is not incidental but central to the pitch; deployments that skip it lose the "safe by default" premise.
• At time of this snapshot the project states it is "not seeking outside contribution" beyond small, trivially-verified PRs (raw/github_doc-readme-md.md) — relevant to anyone planning to fork-and-upstream rather than fork-and-maintain.
• Deploying to your own Cloudflare account via workerd on your own servers (rather than Cloudflare's managed platform) was, at this snapshot, marked "COMING SOON" with documentation and tooling still in progress (raw/github_doc-readme-md.md).

Related Concepts

• getting started — running the stack locally or deploying it.
• architecture — the Workers substrate and monorepo package structure.
• agent chat and company knowledge — the agent chat UI pillar.
• gadgets — the sandboxed app pillar.
• gatekeepers — the security framework pillar.
• blueprints — how gadgets become shareable templates.
• sharing — how gadgets and their outputs are collaborated on.

Sources

• raw/github_doc-readme-md.md
• raw/web_community-cloudflare-os-an-open-platform-for-agents-apps-and-work-the-.md
• raw/github_doc-agents-md.md