Cloudflare has opened a waitlist for fully managed Cloudflare OS deployments, offering organisations an agent workspace connected to their company context, data and systems. The important change is who runs it: teams would choose the access and connections, while Cloudflare handles deployment, operation and updates. This is a waitlist announcement, not general availability. The existing open-source version remains an option for organisations that want to deploy and manage their own workspace.
Cloudflare Watch analysis
What happened
In its 1 October announcement, Cloudflare describes a managed service that would let organisations launch their own workspace from its dashboard. Teams would specify a custom domain and access policies, and choose which organisational skills, context and external systems the workspace can use.
The workspace is intended for both completing tasks and building reusable team tools. Cloudflare gives customer-meeting preparation as an example: bringing together company procedures, account information, support tickets and product usage, then producing a presentation for colleagues.
The announcement also adds a concrete capability to Cloudflare OS: connecting an existing GitHub repository. Previously, Cloudflare says, agents could write code for an application but could not work with code in an existing Git repository.
Organisations interested in the managed option can join the waitlist through the Cloudflare OS announcement.
Why it matters
A company agent needs more than a clever answer box. It needs the right context and permission to reach the systems where work actually happens. Those connections are useful, but somebody still has to keep the workspace running.
The managed option shifts that operational job to Cloudflare without removing the organisation’s decisions about access and scope. That could make a trial easier for teams that want to test agent workflows without also volunteering to maintain another service. The GitHub connection broadens the workspace’s usefulness beyond documents, presentations and internal tools.
Our read
This is a worthwhile expansion because it tackles a practical adoption barrier: running the workspace, not merely demonstrating it. An agent preparing a customer briefing is appealing; an unexpected maintenance rota is rather less so.
Start with one bounded workflow and decide which information and systems it genuinely needs. Meeting preparation is a sensible candidate because colleagues can review the output before using it. The existing self-managed option offers more direct control; the managed waitlist offers a route towards less operational work. Neither choice removes the need to define what the agent may do.
What to watch
- When managed deployments become available beyond the waitlist.
- What pricing and service terms accompany access.
- How much organisational customisation the managed option supports.
- Whether connected-repository workflows make this a useful shared workspace for development teams.
Discussion spark: Would you trade direct operational control for a managed company-agent workspace, or should a system connected to internal data remain something your own team runs?
Sources and evidence
- Source update (1 October 2026, 13:00 UTC)
not affiliated with or endorsed by Cloudflare