Cloudflare Completes Its Agent Infrastructure Stack with Browser Run Rebuild and Six‑Layer Platform

Cloudflare announced that its Browser Run service has been rebuilt on top of the company’s native Containers platform. The new architecture delivers four times higher concurrency—120 simultaneous headless browsers versus the previous 30—and 50 % lower latency for quick‑action calls. In addition, the service now supports WebGL and the WebMCP protocol, enabling agents to render graphics‑intensive pages and exchange model context directly through the browser.

The rebuild required no code changes for existing users, which means developers can immediately benefit from the performance gains. This upgrade caps a rapid series of launches over the past two months that together form a full‑stack, edge‑distributed platform for AI agents.

---

The six layers of Cloudflare’s agent platform

1. Compute – Two tiers of execution:
   • Dynamic Workers – V8 isolates that start in milliseconds, ideal for lightweight tasks such as linting, type‑checking, or simple API calls.
   • Sandboxes (GA) – Full Linux containers with secure credential injection via an egress proxy. Agents can run git, start dev servers, compile code in multiple languages, and keep secrets hidden from the runtime.
2. Orchestration – Dynamic Workflows, an MIT‑licensed 300‑line library that extends Cloudflare’s durable execution engine. Each step is retryable, sleeps are free (the worker hibernates), and idle tenants incur near‑zero cost.
3. Memory – Agent Memory (private beta) extracts structured knowledge from conversations using a dual‑pass ingestion pipeline and serves it through a five‑channel parallel search with Reciprocal Rank Fusion. Shared memory profiles let teams of agents reuse common facts.
4. Browsing – The rebuilt Browser Run on Containers gives agents headless Chromium instances controllable via the DevTools Protocol or the new Agents SDK. The addition of WebMCP lets agents send model context through the browser, turning the browser itself into a model‑aware conduit.
5. Commerce – A co‑designed protocol with Stripe lets agents create Cloudflare accounts, register domains, start subscriptions, and deploy code without human intervention. Stripe enforces a default $100 / month spending cap per provider to prevent runaway costs.
6. Security & Observability – Integrated edge‑level DDoS protection, request‑level logging, and per‑tenant telemetry dashboards ensure that autonomous agents operate within strict safety boundaries.

---

Why the rebuild mattered

• Workload mismatch – Browser Run originally shared infrastructure with Cloudflare’s Browser Isolation (BISO) product. Human‑focused sessions are long and steady, while AI agents generate short, spiky bursts of requests. The shared pool caused contention and throttling.
• State management – Moving from Workers KV (eventual consistency) to D1 with Queues eliminated race conditions. Transactional assignment and batch writes now support up to 500 000 containers per location.
• Simplified protocol – Replacing the multi‑step WebSocket choreography for quick actions with a single HTTP request executed entirely inside the container reduced round‑trip time and removed a source of failure.

---

Use cases enabled by the stack

Scenario	How the stack helps
Autonomous web‑scraping agents	Browser Run provides a pre‑warmed Chromium instance; Sandboxes give access to curl and wget; Dynamic Workflows coordinate pagination and retries.
Customer‑support bots that need up‑to‑date docs	Agent Memory stores the latest knowledge base; Workers fetch new releases; the bot queries memory with sub‑second latency.
Self‑service SaaS onboarding	Commerce protocol creates accounts, provisions domains, and triggers a Deploy workflow; all actions are auditable via edge logs.
LLM‑augmented browsing	WebMCP lets the model push context into the browser, enabling “think‑while‑you‑browse” patterns for research assistants.

---

Trade‑offs and considerations

• Cost model – While idle Workers are cheap, containers incur a per‑second charge that scales with concurrency. Teams must monitor container usage to avoid unexpected bills, especially when running large‑scale batch jobs.
• Vendor lock‑in – The stack is tightly coupled to Cloudflare’s edge network. Migrating to another provider would require re‑architecting the six primitives, which may be non‑trivial for large agent fleets.
• Feature parity with hyperscalers – AWS Bedrock AgentCore offers a managed registry and model hosting but lacks a managed browser or memory service. Google Cloud’s GKE Agent Sandbox provides container isolation but not the integrated commerce flow. Cloudflare’s advantage is vertical integration; the downside is a smaller ecosystem of third‑party integrations.
• Operational complexity – Managing state across Workers, D1, Queues, and Containers adds operational surface. Cloudflare’s documentation is improving, but teams should adopt the Agents SDK early to hide low‑level plumbing.

---

What this means for platform teams

If you are evaluating where to run AI agents, Cloudflare now offers a complete, edge‑native stack that covers the entire lifecycle—from code execution to persistent memory, from browsing to billing. The platform’s edge distribution reduces latency for globally dispersed users, and the per‑tenant pricing model keeps costs low for sporadic workloads.

However, the decision still hinges on integration needs. Teams that rely heavily on existing AWS or GCP services may prefer staying within those ecosystems for unified IAM, monitoring, and data pipelines. Conversely, organizations that value low latency, built‑in browsing, and a unified commerce protocol may find Cloudflare’s stack compelling.

---

Getting started

1. Sign up for a Workers plan (the Browser Run improvements are live on all tiers).
2. Install the Agents SDK from the official repository.
3. Provision a Sandbox via the Cloudflare dashboard or the cf CLI.
4. Enable Agent Memory in beta through the dashboard and start ingesting conversation logs.
5. Explore the Dynamic Workflows library in the documentation.

---

Steef‑Jan Wiggers is a senior cloud editor at InfoQ and a domain architect at VGZ. He focuses on integration platforms, Azure DevOps, AI, and cloud architecture.