Cloudflare OS is open source — agents in your own account

Most "AI workspace" products are a SaaS seat you rent, with your company's context living on the vendor's side of the line. On August 5, Cloudflare open-sourced Cloudflare OS under Apache 2.0 — an agent workspace, a security layer, and an app platform that deploy into your Cloudflare account. The interesting part isn't the demo. It's that the open-source Cloudflare OS release moves the whole thing to infrastructure you already pay for.

What actually happened

Cloudflare's announcement describes three pieces that ship together.

The agent workspace. A browser interface where agents run against context and skills your company curates, inside an isolated runtime where they can write and execute code. No developer setup to use it.

Gatekeepers. Service-specific Workers that sit between agents and your internal systems. Each one enforces policy on what the agent can reach and tracks what data it has already seen, so an agent can't quietly launder information from one system into another.

The app platform. Agents build full-stack apps — client UI plus server code — that run as Dynamic Workers with their own SQLite database. Apps are shareable two ways: as a running instance, or as a blueprint someone else forks and modifies.

It runs on Workers, Durable Objects, Cloudflare Access for identity, and AI Gateway for model routing and cost control. Cloudflare built it for itself first and gave every employee access in May; open-sourcing followed in August. Two repos are public — the core product and a starter example — plus a deploy flow at os.cloudflare.app/deploy and a pnpm run-local path that boots it on localhost:8787 via wrangler. Running it on your own servers with workerd is documented as "coming soon." Cloudflare named Presidio and Happy Cog as deployment partners.

Why an open-source agent platform matters for your business

The pitch for internal AI tools has always come with a hostage clause: your terminology, your SOPs, your system connections all get encoded inside someone's product. Switching costs compound quietly for a year, then you find out what they are.

Apache 2.0 plus deploy-to-your-own-account changes the shape of that bet. You still depend on Cloudflare's runtime — this is not vendor-neutral — but the application code is yours to read, fork, and audit. The gatekeeper pattern is worth stealing whether or not you deploy any of this: a thin per-service policy layer that knows which agent, acting for which person, touched which record beats a blanket API key every time.

The honest caution is maturity. This is a first public release of a tool that has existed internally for three months. There is no pricing page, no SLA, and no published guidance on what happens when a Dynamic Worker app someone built in an afternoon becomes load-bearing. Deploy it to a team, put a real workflow through it, and see whether the governance holds before it touches customer data.

Sources: Cloudflare Blog, cloudflare/cloudflare-os on GitHub, SiliconANGLE.