Cloudflare OS opens a waitlist for managed workspaces
A month after open-sourcing its agent workspace, Cloudflare is offering to run Cloudflare OS for companies that would rather not operate it themselves.
Cloudflare has opened a waitlist for fully managed Cloudflare OS deployments, a month after publishing the agent workspace as open source. The managed option runs the same product for organisations that would rather not configure, operate and update it themselves.
What the managed version hands over
An administrator still decides what matters: the custom domain the workspace lives on, the Cloudflare Access policies that govern who gets in, which organisational skills and context are available, and which systems the agent may reach. Cloudflare takes the deployment, the running of it and the updates. Setup happens from the Cloudflare dashboard by naming those choices and connecting an AI Gateway.
The company says thousands of organisations have been using the open-source version since launch, mostly to work with internal data, produce documents and slides, build small internal tools, and automate recurring work with agents.
What the past month added
Agents can now mount an existing GitHub repository. Ask one to explore a codebase, fix a bug, add a feature or open a pull request, and it can search and edit files, review its own changes, create commits and push them to GitHub. The first release deliberately started outside software development; this closes that gap.
Google Workspace support has been rebuilt around its Gatekeeper service, the per-service Worker that sits between Cloudflare OS and an outside system. The workspace can read and research Gmail threads, create drafts and send email, and connect a whole Google Drive, a single folder, a document or a sheet.
Work can also leave in the formats a team already uses. Documents, presentations and spreadsheets export to Microsoft Excel, CSV, PDF, Markdown or HTML, with Word and PowerPoint support promised next. Tools that teams build define their own export options, so an agent can add a calendar-file download to a schedule if it is asked.
Self-hosting is still available
Cloudflare OS remains open source and can be deployed into a customer's own Cloudflare account, which keeps full control but leaves the operator responsible for configuration and upkeep. The waitlist covers the alternative: Cloudflare-managed deployments with the customer retaining the access and context decisions.
Our opinion
Cloudflare's pitch is not the model, it is the plumbing: an agent workspace that already knows the company's terminology, procedures and systems is a different product from a chat window pointed at a folder of documents, and the GitHub mount is the clearest signal of where this is heading. Starting with slides and internal tools and then adding repositories describes the classic path from the people who write documents to the people who ship software. The managed tier is the more interesting bet, because it says operating an agent workspace is not a good use of a customer's engineers, which is exactly the argument that has to be true for this category to sell outside large platform teams. The open question is the one Cloudflare's customers will have to answer themselves: an agent that can push commits and send mail on a company's behalf is only as safe as the Access policies wrapped around it.