Cloudflare Launches Open-Source AI Agent Platform for Enterprise Productivity

Cloudflare open-sources vibe-coding platform for people who aren't coders

Cloudflare has open-sourced its Cloudflare OS platform, which it first developed as an internal workspace for employees to build apps using AI agents -- including people who are not software developers or engineers. The company also touts a security framework designed to reduce the risk of employee vibe-coding sessions creating serious security flaws or leading to data breaches. The tech company spent several months building and internally testing Cloudflare OS, which allows employees to describe workflows in natural language so that an AI agent can code them into applications. In an August 5 blog post announcing the open source version's availability on GitHub, the company claims thousands of Cloudflare employees use the platform on a daily basis to "create documents and slides, automate repeatable tasks, and build small apps to visualize data and help them do their work." "This is a full-on personal app vibe coding platform, in which the sandbox is so secure that you can pretty much go wild -- the AI cannot introduce a significant security bug," said Kenton Varda, principal engineer at Cloudflare, in a post on the social media platform X. "We believe a company's security team can feel comfortable giving non-technical users permission to vibe code and then sleep soundly at night." Building better sandboxes The security model relies on creating fine-grained app instances so that a document editor app would run each document as a separate instance in a separate sandbox, Varda explained. The Cloudflare OS platform manages who has permission to access each instance, and each individual runs their own copy of the code that they can freely modify. This sandboxing mechanism, based on a preexisting Cloudflare feature called Dynamic Workers, does not use typical software containers. Instead, it creates "isolates" -- instances of the V8 JavaScript execution engine -- that take just a few milliseconds to start up and use only a few megabytes of memory. That makes isolates 100 times faster and 10-100 times more memory-efficient than a standard container. To minimize the exposure of company data, AI agents start out with no permissions to access or share resources and must request them through the Cloudflare OS platform. Server code runs with "global outbound networking disabled" while client code "runs in a sandboxed frame in the browser," meaning "neither can reach the Internet except through capabilities you explicitly provide," according to the main company blog post. That sandboxing and permission process baked into the Cloudflare OS framework could prove helpful in practice, even if no system is foolproof. Researchers at Pillar Security just published a report on sandbox escapes and boundary bypasses in popular AI coding agents such as Cursor, Codex, Gemini CLI, and Antigravity. Making vibe coding less sloppy Cloudflare OS can work with just about any AI model and allows organizations to select the most suitable model for the job at hand. "Not every user needs access to the max thinking mode of the latest frontier lab model," said Sam Rhea, chief information officer at Cloudflare, in a separate blog post. "And we do not need team members spending $20 to summarize their email inbox every hour." The company has also improved the platform so that running skill files for specific workflows relies more on deterministic steps with AI inference used only when needed rather than requiring a "token-hungry inference session" each time, Rhea said. The platform also enables administrators to monitor employees' AI inference spending and set budgets and rate limits -- a crucial feature at a time when companies and individuals have found it can be all too easy to burn through their budgets for AI model use. But that won't stop more questionable practices if corporate leaders decide to incentivize AI "tokenmaxxing" to pressure employees to use AI tools. Cloudflare shared some hard lessons learned along the way as it tried to ensure the efficient use of AI tools through Cloudflare OS. One early mistake involved simply giving everyone outside the engineering team "the same tools with slightly friendlier user interfaces" because the AI coding harnesses that engineers typically use are less suitable for knowledge work involving "one-off outputs and work on projects that involve dozens of systems of record," Rhea explained. "If you give everyone a harness workspace that is great at writing code, you'll wind up with way more code than you need," Rhea wrote in his blog post. "The result became a flood of vibe coded apps looking for a problem to solve." The growing use of AI agents within the organization also meant "anyone at Cloudflare could now write bad code, faster, thanks to AI," Rhea said. So the organization created the Cloudflare Engineering Codex, an "authoritative guide" to help both human engineers and AI agents review code and catch potential issues. Over the past four months, the company's AI code reviewer "flagged nearly a quarter of a million deviations from Cloudflare engineering standards and blocked 16,000 merges," said Timo Reimann, a systems engineer at Cloudflare, in a blog post about the Engineering Codex and how the company uses AI agents to uphold engineering standards. Open source but not free of cost Now that the company is open-sourcing Cloudflare OS for others to use, developers can try to run the entire stack on their own machines. A notable caveat is that the Cloudflare OS backend can only be deployed by Cloudflare users who have subscribed to the Workers Paid plan. The paid subscription requirement was not initially made clear up front. A GitHub user raised the issue and shared a screenshot showing that their Workers Free plan had been stopped from deploying the Cloudflare OS backend partway through the process. "You have a right to charge but requirements should be completed before starting the deployment process," wrote the GitHub user mac2net. "I wasted 20 minutes I will never get back." To Cloudflare's credit, the company quickly updated the deployment process to alert users at the start about the paid plan requirements. A company representative also responded to the issue on GitHub.

GitHub - cloudflare/cloudflare-os: Agent workspace built on Cloudflare Workers for creating documents, building apps, and running agents with your company's context and systems.

Cloudflare OS is an "operating system" for AI productivity originally developed for use inside Cloudflare. A large portion of Cloudflare's workforce -- from engineering to sales and everything in between -- uses Cloudflare OS every day to help them do their jobs. This is not a traditional computer operating system. We use the term "operating system" in two senses: * 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. * An operating system for AI workloads, analogous to the sense in which a traditional operating system manages compute workloads. Cloudflare OS provides three things in particular: We are making Cloudflare OS open source so that others can copy it and customize it for their own company. The idea is not that your company uses Cloudflare OS, but rather that you make it "Your Company OS". To quickly run Cloudflare OS locally, install pnpm, then do: Then visit: http://localhost:8787 This runs the whole stack locally on wrangler and workerd. This is not meant for production use, but is a quick way to see what the product does. Alternatively, you can deploy to your Cloudflare account. (More options at the end of this readme.) Try prompts like: * "Make slides for my upcoming meeting with a customer." (This will use the built-in slides blueprint.) * "Make a collaborative whiteboard app." (This will create a new app from scratch.) * "Make a tic tac toe game." followed by "I'll be X and you be O. I've made my first move. Your turn." * "Make an issue dashboard for this GitHub repo." (Attach a repo; requires that the GitHub integration is configured.) * "Fix the typos in this Google Doc." (Attach a doc; requires that the Google integration is configured.) Cloudflare OS is in a state of heavy development. This repository is actually version 2, a complete rewrite taking what we learned from version 1 and putting it on a new foundation. As of the August 2026 release, Cloudflare OS v2 is very capable, but still has many rough edges. We know, and we're working on it. For now, consider this an "early access" release. Cloudflare OS is more than just another chatbox with connectors. The system revolves around a new approach to software, where every user runs their own copy of the productivity apps they use. When you create a slide deck in Cloudflare OS, you are not calling out to some SaaS software running in the cloud. The system creates a private instance of the slide deck software just for you. We call this a "gadget". This instance runs in a separate sandbox from everyone else's slide decks. This has two profound effects: This is a big departure from the last 25 years of cloud architecture and "Software as a Service", but we think AI has changed the equation. When any user is capable of prompting an agent to add the features they need, the centralized model of software stops making sense. Gatekeepers are like supercharged MCP servers. When you introduce an agent or Gadget to an external resource, a Gatekeeper is created to manage that access. The Gatekeeper is a piece of software specific to each external service which moderates a Gadget's connection to that service. It: * Provides a clean Cap'n Web API to the service (wrapping whatever API the service provides natively). * Handles authorization (e.g. via OAuth). * Enforces narrow access to only the specific resource the user intended. * Logs every action the Gadget (or agent) performs, for your review. * For any action which has side effects, provides the human user an opportunity to approve or deny the action ("human in the loop"). On the last point, Gatekeepers implement a significant advancement in the state of the art. Traditionally, human-in-the-loop setups require the human to approve actions synchronously. When the agent wants to do something, it has to stop and wait for said approval before it can continue. This is annoying: you give your agent a task, then walk away and get a coffee, only to come back and find the agent got stuck on an approval on the first step and has made no progress. As a result, people often give in and set their agents to "auto-approve", or , which is, obviously, unsafe. Gatekeepers provide a better way: When the agent (or Gadget) performs an action that requires approval, the Gatekeeper will simulate the outcome locally, allowing the agent to proceed and queue up more actions. The Gatekeeper tells the agent that the action completed, and if the agent tries to read back the results, the Gatekeeper gives it simulated results. Once the agent is done, the user may approve or reject the actions in bulk, or one-by-one, but either way, they can do it later, when it is convenient. Logistically, each Gatekeeper is implemented as a separate Worker. In the future, we envision Gatekeeper services being deployed and maintained independently from OS instances, but the details have yet to be worked out. For now, we have provided a few interesting Gatekeepers in this repository which you can deploy together with your own OS instance. The basic user experience of Cloudflare OS is something like an online office suite, like Google Docs or MS Office. But, imagine that instead of a fixed set of file types (document, spreadsheet, slide deck), each file -- or "Gadget" -- is potentially its own custom application, written by AI to serve exactly your needs. Just like office docs, each gadget is private by default, but can be shared -- securely -- in order to collaborate with your team or your friends. Just like office docs, you can have thousands of them. You can create them on a whim. Just like office docs, you can start from "templates" -- called "Blueprints". But where an office template is just some content, a Blueprint specifies a whole application. Like office docs, you can create new templates (blueprints) from your own docs (Gadgets) and share them with others. But when you do so, you are sharing the code for a whole app. The OS terminology isn't entirely marketing. Cloudflare OS is actually analogous to an operating system on a technical level. Our "kernel" is in the workshop-backend package. The backend legitimately does a lot of things similar to real OS kernels: it connects users to programs and devices (Gadgets and Gatekeepers, as we call them) while implementing security by sandboxing applications and enforcing access control. In this analogy, Gatekeepers -- which connect users and agents to external services -- are like drivers -- which connect users and programs to external devices. There is one thing that traditional OSes don't really manage today, but Cloudflare OS does: AI agents. If you think about it, this is really a missing feature in traditional OSes. We believe that AI agents cannot simply be treated as users. They must be accountable to a human user, while at the same time having their own restricted permissions. Agents do work by writing snippets of code and executing them on the fly. The ideal security model for all of this is capability-based security, not access control lists. See what I mean? Perhaps traditional OSes ought to give AI agents special treatment, too. Cloudflare OS is built on Cloudflare Workers, making heavy use of Durable Objects, Dynamic Workers, and Facets in particular. Every workspace is its own Durable Object, every Gadget runs in a Dynamic Worker Facet, and Gatekeepers also install facets into each workspace to manage access to remote services. Cloudflare OS is, in fact, built by the very people who built Workers itself. It uses cutting-edge features of the Workers Runtime -- in fact, Dynamic Workers, Facets, and several other features were added to the runtime specifically to support Cloudflare OS, with more to come. Studying the Cloudflare OS source code is a great way to understand how the Workers Runtime team thinks Workers should be used. Being built on Workers does not mean that Cloudflare OS can only run on Cloudflare. In fact, , the Cloudflare Workers Runtime, is itself open source, and Cloudflare OS can run entirely on top of it on your own servers. The Cloudflare OS coding agent is actually a fully multi-purpose agent that can perform arbitrary tasks; like other popular coding agents, you don't have to code with it. You can use it to build Gadgets, but you can also skip the Gadget and just have the agent perform tasks directly. The Cloudflare OS agent is a Code Mode agent -- it performs tasks by writing and immediately executing snippets of code. It can be connected to external resources using Gatekeepers (like MCP -- see below). While you can code a Gadget by hand if you want, the expectation is that AI writes the code for you. Cloudflare OS features a built-in coding agent that will build whatever you ask it, test it for you, and debug errors. You can choose your LLM. Cloudflare OS works with many major AI model providers and self-hosted models, with more providers being added all the time. Because of the tightly-integrated and simplified nature of the platform, even when using the same underlying AI models, the Cloudflare OS coding agent often performs better and faster with fewer tokens than a general-purpose coding agent would. Every app built with Cloudflare OS automatically has an agent-friendly API. That means, after you've asked AI to build the app, you can also ask AI to collaborate with you inside the app. No need to build an MCP server nor integrate a custom agent loop. It's just there by default. This works because the client and server portions of a Gadget are required to communicate via Cap'n Web RPC. This is a win-win: You can share your Gadget just like you'd share a document in a typical online office suite. You can give specific users access, or create a share link that provides access to anyone who opens it. And just like those online office suites, you'll be able to see your collaborators' actions in real time. This works because every Gadget is backed by a Durable Object, Cloudflare's stateful serverless primitive which makes real-time multiplayer collaboration easy. It's so easy that the coding agent just implements it by default, without being asked. If you've created a Gadget that might be useful to others, but you don't want to share the Gadget itself, you can instead share a Blueprint, allowing other people to create their own copy of the Gadget. A Blueprint is essentially a copy of the code. It may sound simple, but Blueprints are a major change from cloud software tradition. Traditionally, if you create a web app that you want to share with other users, you host the app on your server, and the users connect to that. Blueprints are much more like mobile apps and traditional PC apps: every user runs their own copy of the software. In the age of AI, this change is critically important. On one hand, AI empowers an individual developer to build more than ever, but it is still difficult for an individual developer to maintain an online service; this eliminates the need. On the other hand -- and even more importantly -- allowing each user to run their own copy of the software empowers the user to change the software to meet their needs, using AI. No need to file a feature request, no need to beg the developer to prioritize it. The end user can solve their own problems. Each Gadget runs in a secure sandbox that prevents it from talking to the internet at all without your explicit consent. In particular: * The server runs in a Dynamic Worker which has had its access to the internet disabled. It can only communicate with specific external resources that you have explicitly designated, via Workers Bindings. * The client code runs in a sandboxed iframe. This iframe can communicate with its server only via a Cap'n Web RPC session provided over to the parent frame. The iframe is otherwise blocked from accessing the internet (to the maximum extent allowed by browsers, via and iframe sandbox settings). Each agent, and each Gadget, by default has access to nothing. Even if you've configured the Gadget Workshop with access to external accounts, agents and Gadgets do NOT automatically get to use them. Instead, you must introduce each agent (or Gadget) to any particular resources you want it to access. For instance, you may introduce a GitHub repository by pasting a link to it, or clicking "add resource" and selecting it via the UI. An agent can also request an introduction to a resource it thinks it needs, which you can then provide or deny. This differs from most agent harnesses, where MCP servers are configured upfront, making broad access to all your services ambiently available to the agent in every chat. Capability-based introductions keep each agent restricted to only the access it actually needs for the job at hand. We've built an online flow that helps you deploy to your own Cloudflare account: https://os.cloudflare.app/deploy Or, for more sophisticated deployment, with your gatekeepers and potentially code changes, check out our deployment starter repo: https://github.com/cloudflare/cloudflare-os-starter To quickly run Cloudflare OS locally, install pnpm, then do: Then visit: http://localhost:8787 This runs Cloudflare OS using , the Workers developer tooling CLI. This is not the right way to run the OS on a production server, but it works fine for trying it out on your local machine. Your data will be stored in a subdirectory named . COMING SOON Cloudflare OS can run entirely on , Cloudflare's open source runtime for Workers. In fact, the "run locally" instructions above use under the hood. We are still working on documentation and tooling to help you smoothly deploy the OS on top of on your own servers. If you are feeling adventurous, read the low-level documentation for workerd config (or point your agent at it) and have a go. Many Gatekeepers require configuration in order to be able to connect to third-party services, including obtaining OAuth client credentials for each service. Unfortunately, many service providers intentionally do not make this easy, since the intended audience for OAuth is developers. Each gatekeeper package contains instructions for how to set it up: * GitHub API * Google API * Cloudflare API * Supabase API * Notion API * Confluence API * Email Workers * Home Assistant * Slack API * Spotify * ZoomInfo API When developing, you'll want to run the front-end and back-end as two separate commands in two terminals: Then visit: http://localhost:3000 At this time, we are not seeking outside contribution. AI has made writing code easy. The hard part, today, is not writing the code, but reviewing it, making sure quality stays high, and keeping the product coherent. In that light, unfortunately, external code contributions are "donating" the easy part of the job, while creating more of the hard work. With that said, we are happy to accept small, trivially-verified PRs that fix a problem. However, we ask that you refrain from submitting low-value PRs (e.g. typo fixes) or PRs that are more than a dozen or so lines. Such PRs will be closed with a reference to this guideline. If you have a big idea you'd like us to consider, feel free to open a discussion about it. This policy may change in the future as the project matures. Until then, thank you for your understanding. Cloudflare OS has far too many open source dependencies to list here. But, we'd like to highlight a few that do particularly heavy lifting:

Cloudflare Announces Open-Source Cloudflare OS As AI "Operating System"

"Cloudflare OS starts with a conversation in your browser, like many other AI tools. What makes it different is that each conversation is grounded in the context and skills your organization has curated. Give your workspace a goal, and it can draw on that knowledge and work with the tools and data your organization already uses to achieve it. Cloudflare OS combines three parts: - An agent workspace grounded in context and skills your company curates, with an isolated runtime where agents can write and run code. - A new security and governance framework for safe access to internal data and services. - A platform for personal, modifiable apps that people can build, share, and continue changing. What begins as a conversation can become a doc, an app, or a workflow that continues doing the work." "This is not a traditional computer operating system. We use the term "operating system" in two senses: - 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. - An operating system for AI workloads, analogous to the sense in which a traditional operating system manages compute workloads."

Cloudflare OS: Here's What's Inside the Open-Source AI Agent Platform

The pitch: run the whole thing on your own systems, connected to your own data, instead of handing agents broad API keys. Cloudflare built the first version of Cloudflare OS for itself. In May, the company gave every one of its thousands of employees access, CEO Matthew Prince wrote, and people outside engineering started using it to draft documents, build slides, and automate repeatable work. Now Cloudflare is open sourcing a rebuilt version that any organization can deploy and connect to its own internal systems. "The security had to be part of the platform, not something every person building an app or using an agent has to implement correctly," the company said in its announcement. That's the real product. What's actually inside Cloudflare OS combines three parts. First, there's an agent workspace that grounds each conversation in your company's curated context and skills, with an isolated runtime where the agent can write and run code. There's also a security and governance framework, new in this version, which sits between agents and your systems of record. And, lastly, there's a layer for personal, modifiable apps that lets a workspace turn a chat into a document, a workflow, or a small full-stack app. Cloudflare's CIO Sam Rhea laid out how the company approached security in this agentic-powered experiment: handing API keys to people and agents is dangerous and doesn't scale, because keys give broad, long-lived access that's hard to constrain or audit. Instead, agents start with access to nothing. So they request a specific resource, and a Gatekeeper -- a service-specific Cloudflare Worker -- mediates. The credential never touches the agent or its code. That's a cleaner model than MCP alone. Model Context Protocol tells an agent which tools it can call, but not which underlying resources it has actually seen. Cloudflare OS logs every observation and checks a person's access before they can open a workspace or view what an agent produced. Each app an agent builds is a real Cloudflare Worker, riding on Dynamic Workers and Durable Object Facets the company built for this project, talking to the client over Cap'n Web, its open-source object-capability RPC system. "If you can build a tool to do a job yourself, agents can use your tool to do the job when you're not there," the post notes. It's a strong vision, but some users may still be skeptical: Cloudflare OS is a Cloudflare product, so the agents, apps, and governance it sells you to run all live on Cloudflare's edge. The "open" in open source gets you the code; the runtime still is controlled by a central entity.

Cloudflare launches Cloudflare OS: an open-source AI agentic workspace for the enterprise

Cloudflare Inc. today announced the launch of Cloudflare OS, an open-source artificial intelligence agentic workspace available through the browser, filled with custom shared micro-applications for enterprise employees. Most AI tools offered to the enterprise are generalized and understand a great deal about the world, but very little about the specific company they're deployed for. Cloudflare OS was built from the ground up for its own employees, its own workforce, and its own teams, who use it daily to perform research, create documents and build apps for their day-to-day jobs. "Cloudflare OS is how we run Cloudflare. For AI to truly transform an enterprise, it can't live in a silo or behind a developer bottleneck. Every employee needs the ability to build, iterate, and automate safely," said co-founder and Chief Executive Matthew Prince. The platform is designed to capture a company's working knowledge from day one and travel with employees by allowing them to create custom micro-apps that help them build their own workflows with their internal knowledge. They can then share that information and collaborate internally without worrying that the context will be lost. Because the framework is open source and it runs on a company's own Cloudflare account, organizations own anything they build on it. The company maintains and possesses the processes, context and internal system connections and will not get locked into a closed product. According to Cloudflare, what they get is this: an AI agent workspace for everyone that is accessible via browser that doesn't require developer expertise that allows employees to conduct research, produce documents tied to live data, run automated workflows, build tools and do busywork, all without waiting for the information technology or development teams. This means they can quickly spin up smart applications they can build and share with everyone with their own isolated database, real-time capabilities, access controls and more, no developer required. As it is built on Cloudflare Access, it is zero trust by default, which verifies every user and every request before access is granted. Another useful part of what Cloudflare built with Cloudflare OS is bring your own model. Through Cloudflare AI Gateway, organizations can use any AI model provider. They are not locked to any one vendor; this means administrators can control how tokens are used and see what's being spent, broken down by person, team, and app. This allows them to set spending budgets, rate limits, or route tasks according to complexity. For example: routine tasks can be sent to small, efficient models and to frontier models when high reasoning is needed. "We built this because nothing else did what we needed. Now any company can start from where it took us years to get," added Prince.

Cloudflare OS Is the First AI Workspace Built Around How Companies Actually Work

New open source agent workspace gives employees AI tools built around how their company operates, with security and governance built in by default Cloudflare, Inc. today announced it will launch Cloudflare OS, an open source AI workspace that runs on Cloudflare's global network. Cloudflare OS will give every employee a secure workspace equipped with AI tools and access to internal company systems - without requiring new infrastructure or months of custom development. Today, Cloudflare OS is available now through Cloudflare's open-source repository. Soon organizations will be able to access Cloudflare OS directly through Cloudflare or work with a select group of global implementation partners - including Presidio, Happy Cog and others - to tailor the deployment to their specific environment. The typical enterprise AI tool knows a great deal about the world and almost nothing about how a specific company operates, its internal systems, approval processes, or the ways teams actually get work done. Every new session starts from zero, with employees re-explaining context the AI should already know. Building a tailored alternative is no small project; a platform with proper security and real integration into internal systems can take years to develop and cost millions to maintain. In the meantime, employees find workarounds, IT loses track of which AI tools are running and who is using them, and costs pile up with little to show for it. Cloudflare OS starts from a different premise: a company captures its knowledge, processes, and ways of working once in a form AI can actually execute, and that knowledge travels with every employee's workspace from day one. Cloudflare OS started as the platform Cloudflare built to run its own global workforce. Thousands of Cloudflare employees across every team use it daily to perform research, create documents connected to live data, automate repetitive tasks, and build working apps for their day-to-day jobs. Internal tools, documents, and company systems are accessible through secure connection points that verify every user and every request before access is granted. That same platform is now available to any organization as open-source software. Because it's open source and runs in a company's own Cloudflare account, organizations own what they build on it. A company's processes, context, and internal system connections don't get locked into a vendor's closed product. Key capabilities include: * An Agent Workspace for Everyone: Cloudflare OS is accessible directly through the browser without needing developer expertise. Employees get an AI that can conduct research, produce documents tied to live data, or run automated workflows in the background without waiting on IT or a development team. * Apps Anyone Can Build and Share: Any output can become a working app with its own isolated database, real-time capabilities, and access controls. Colleagues can use that app directly or adapt it for their own needs. No developer required. * Zero Trust by Default: Cloudflare OS is built on Cloudflare Access, which verifies every user and every request before anything is granted. AI agents start with zero permissions by default and are given access only to what they need for a specific task. Governed connectors called Gatekeepers give the owners of each internal system precise control over what the AI can see, what it can change, and when a human needs to sign off before an action goes through. * Works on Any Model and Controls Cost: Through Cloudflare AI Gateway, organizations can use any AI model provider, and they're not locked into one vendor. Administrators see exactly what's being spent, broken down by person, team, or app. They can set spending budgets, rate limits, or route routine tasks to smaller, more affordable models where a top-tier model isn't needed. "Cloudflare OS is how we run Cloudflare. For AI to truly transform an enterprise, it can't live in a silo or behind a developer bottleneck. Every employee needs the ability to build, iterate, and automate safely. Our employees get AI tools connected to the systems they actually use, and security isn't something IT has to bolt on afterward," said Matthew Prince, co-founder and CEO of Cloudflare. "We built this because nothing else did what we needed. Now any company can start from where it took us years to get."

Cloudflare Launches Cloudflare Os Open Source Ai Workspace

Cloudflare announced it will launch Cloudflare OS, an open source AI workspace that runs on Cloudflare's global network. Cloudflare OS will give every employee a secure workspace equipped with AI tools and access to internal company systems?without requiring new infrastructure or months of custom development. Cloudflare OS is available now through Cloudflare's open-source repository. Organizations will be able to access Cloudflare OS directly through Cloudflare or work with a select group of global implementation partners?including Presidio, Happy Cog and others?to tailor the deployment to their specific environment. Cloudflare OS started as the platform Cloudflare built to run its own global workforce. Thousands of Cloudflare employees across every team use it daily to perform research, create documents connected to live data, automate repetitive tasks, and build working apps for their day-to-day jobs. Internal tools, documents, and company systems are accessible through secure connection points that verify every user and every request before access is granted. That same platform is now available to any organization as open-source software. Because it's open source and runs in a company's own Cloudflare account, organizations own what they build on it. A company's processes, context, and internal system connections don't get locked into a vendor's closed product. Key capabilities include: An Agent Workspace for Everyone: Cloudflare OS is accessible directly through the browser without needing developer expertise. Employees get an AI that can conduct research, produce documents tied to live data, or run automated workflows in the background without waiting on IT or a development team. Apps Anyone Can Build and Share: Any output can become a working app with its own isolated database, real-time capabilities, and access controls. Colleagues can use that app directly or adapt it for their own needs. No developer required. Zero Trust by Default: Cloudflare OS is built on Cloudflare Access, which verifies every user and every request before anything is granted. AI agents start with zero permissions by default and are given access only to what they need for a specific task. Governed connectors called Gatekeepers give the owners of each internal system precise control over what the AI can see, what it can change, and when a human needs to sign off before an action goes through. Works on Any Model and Controls Cost: Through Cloudflare AI Gateway, organizations can use any AI model provider, and they're not locked into one vendor. Administrators see exactly what's being spent, broken down by person, team, or app. They can set spending budgets, rate limits, or route routine tasks to smaller, more affordable models where a top-tier model isn't needed. Cloudflare is collaborating with leading global systems integrators to customize the platform for complex, unique customer environments. These partners build directly on Cloudflare?s infrastructure to tailor Cloudflare OS to specific industry requirements, existing tech stacks, and custom compliance needs. Cloudflare OS is available as an open-source platform. A managed deployment option is coming soon through the Cloudflare dashboard. Organizations interested in a partner-led implementation can reach out.