By CloudflareLearning Objectives
- Understand what Cloudflare OS is and the internal-tooling problem it targets
- Explain the Gatekeepers permission model and why agent platforms need one
- Evaluate the licensing and maturity trade-offs before adopting a two-day-old platform
What Is Cloudflare OS?
Cloudflare OS is an open-source platform for building and running internal company applications with AI agents, released on August 5, 2026. The pitch is aimed at the long tail of internal software that never gets built: a team needs a small tool, no engineer is free, and the need goes unmet. Cloudflare OS lets someone describe what they want in plain language and have an agent write and run it.
Applications are called Gadgets. Each user's workspace runs as its own isolated instance, and each Gadget runs in its own sandbox, so one person's experiment cannot reach into another's data. Beyond building apps, the platform handles research, document and presentation creation, real-time collaborative editing, and automated workflows.
It is built on Cloudflare's own edge platform — Workers, Durable Objects, Dynamic Workers, and Facets — which is both its architectural advantage and the main thing to weigh before adopting it.
💡Key Concept
Gatekeepers — the security layer. The hard problem in internal agent platforms is not generating code, it is controlling what the generated code may touch. Cloudflare OS routes every reach into an internal system through a capability-based layer called Gatekeepers, which grants an agent narrow, explicit access rather than ambient credentials. An agent that is never handed a capability cannot use it, whether or not it is tricked into trying.
Dogfooded Before Release
Cloudflare deployed the first version internally in May 2026 to thousands of employees across every function, not just engineering, and released the code roughly three months later. That ordering matters for a platform whose entire premise is non-developers building their own tools: the internal deployment is the only real evidence so far that non-engineers actually use it.
Strategic partners Presidio and Happy Cog offer customization and deployment help, and Cloudflare says a managed version will eventually appear in the Cloudflare dashboard.
Licensing
The repository at github.com/cloudflare/cloudflare-os is published under the Apache 2.0 license — a genuinely permissive, standard open-source license that allows commercial use, modification, and redistribution with no revenue threshold or field-of-use restriction. There is no separate agreement to negotiate.
⚠️Warning
Open source, but not open to contribution. The README states plainly that the team is "not seeking outside contribution" — trivial bug fixes are welcome, but pull requests are discouraged because reviewing and maintaining them costs more than writing the code. You can fork, modify, and self-host freely; you should not expect your patches upstream. Plan on carrying local changes yourself.
Pricing
- Full source on GitHub
- Runs on your Cloudflare Workers account
- Starter deployment template provided
- Planned for the Cloudflare dashboard
- No pricing announced
- Presidio and Happy Cog
- Customization and rollout support
The software is free, but it is not costless: it runs on Cloudflare Workers, Durable Objects, and Dynamic Workers, so your real spend is Cloudflare platform usage scaled to how many workspaces and Gadgets you run.
Strengths
- Genuinely permissive licensing — Apache 2.0 with no revenue trigger, no field-of-use carve-out, and no separate commercial agreement
- Security designed in, not bolted on — capability-based Gatekeepers plus per-workspace and per-Gadget isolation, which is the right shape for a platform that runs generated code against internal systems
- Proven at internal scale first — thousands of Cloudflare employees across all functions used it for roughly three months before release
- Aimed past engineers — the target user is the person who needs a tool and cannot get one built, which is where most unmet internal demand sits
Limitations and Considerations
- Two days old as a public project — released August 5, 2026, with no external adoption track record, no third-party security review, and no community yet
- Contributions discouraged — you can fork but should not plan on upstreaming; budget for maintaining your own changes
- Deep Cloudflare coupling — built on Workers, Durable Objects, Dynamic Workers, and Facets, so this is not a portable platform you can lift onto another cloud
- No managed option yet — the hosted version is announced but not shipped and carries no pricing, so today the only path is self-hosting
- Agent-written internal tools carry their own risk — Gatekeepers constrains what an agent can reach, but code generated from a plain-language description still deserves review before it touches anything that matters
Related Tools
- Cloudflare Workers AI — Cloudflare's edge inference platform, the layer Cloudflare OS builds on
Key Takeaways
- Cloudflare OS is an open-source platform, released August 5, 2026, that lets non-developers describe internal apps in plain language and have an agent build and run them
- Applications are called Gadgets, and each workspace and Gadget runs isolated from the others
- Gatekeepers is a capability-based permission layer that grants agents narrow, explicit access to internal systems instead of ambient credentials
- The license is Apache 2.0 — verified on the repository, not inferred from the announcement — but the team explicitly does not want outside contributions
- The main cautions are maturity and lock-in: it is days old with no external track record, and it is built tightly on Cloudflare's edge platform
