Cloudflare Browser Run alternatives for agent workflows.

Browser Run is developer infrastructure. It runs headless Chrome globally. Developers control it through several surfaces. Those surfaces create different replacement requirements.

Quick Actions provide stateless browser outputs. Browser Sessions provide direct browser control. Workers can call both surfaces. External clients can connect through CDP.

Legba occupies a narrower position. Its published skill provides routing and isolated browser sessions. Agents reach hosted sessions through scripts or MCP. Legba publishes no Browser Run compatibility.

Begin with the current dependency. Record every interface and state requirement. Separate required controls from convenient controls. Then compare the smallest complete replacement.

Cloudflare renamed Browser Rendering on April 15, 2026. The current developer product is Browser Run. Older searches still use Browser Rendering. That history explains mixed result wording.

Cloudflare Browser Isolation has another buyer. It belongs within Cloudflare One. Its controls address workforce web access. Its procurement path follows Zero Trust programs.

Our comparison covers Browser Run only. It covers automated browser execution. It does not score workforce policy controls. Those belong within another comparison.

Mixing both products distorts procurement. Browser automation needs interfaces and capacity. Workforce isolation needs identity and policy. Those jobs require separate evidence.

Several platforms host remote browsers for code and agents. Each matches a different Browser Run surface. Match your current integration before comparing prices.

Vendor documentation defines each row below. No row reflects a benchmark. Legba appears last because its scope is narrowest.

The endpoint rarely defines the whole migration. Execution shape affects code ownership. It also affects retries and observability. This matrix exposes those hidden commitments.

Browser Run supports several development styles. That breadth reduces some integration work. It also increases migration surface later. A narrower skill changes that tradeoff.

Quick Actions optimize defined browser outputs. They include screenshots, PDFs, content, markdown, and extraction. They reduce browser lifecycle code. They also standardize the interaction boundary.

Browser Sessions expose deeper control. Cloudflare supports Puppeteer, Playwright, CDP, and Stagehand. That path suits existing automation code. It also preserves lower-level debugging options.

The choice affects failure ownership. Quick Actions return a defined result. Session code owns more browser behavior. Teams should price engineering ownership separately.

Legba should not win protocol checklists. Its published skill serves agents directly. That narrower path cannot prove code-level compatibility. Raw CDP code carries its own upgrade risk.

Cloudflare provides several observation paths. Live View supports interactive browser access. Native developer tools remain available. Generated links must connect within 5 minutes by default.

Structured handoff supports human intervention. An optional timeout caps at 30 minutes. Without one, the handoff has no timeout. Applications receive a completion signal afterward.

Session recording remains a beta feature. It records structured rrweb events, not video. Recordings stay 30 days. Input fields are masked by default.

Legba documents handoff through a private view link. Agent writes pause while the person holds control. Legba session recording remains undocumented. Plan review evidence around that gap.

Cloudflare publishes usage and concurrency pricing. Workers Free includes 10 browser minutes daily. Free accounts also get 3 concurrent browsers. Workers Paid includes 10 browser hours monthly.

Extra paid usage costs $0.09 per hour. Included concurrency is 10 browsers, averaged monthly. Each added averaged browser costs $2. The average uses each day's peak.

Paid defaults allow 200 concurrent browsers. New launches default to 3 each second. Quick Actions default to 30 requests each second. Cloudflare accepts requests for higher limits.

Capacity limits differ from included capacity. Procurement models should separate both numbers. Legba lists its agent plans on its pricing page. Compare one representative workload across vendors.

Most Cloudflare browser processing remains ephemeral. The official FAQ lists important exceptions. Crawl results can remain 14 days. A crawl can run 7 days.

Opt-in recordings remain 30 days. Quick Action caching defaults to 5 seconds. Teams can change or disable caching. These controls deserve explicit review.

Cloudflare requests use Cloudflare network addresses. Customers cannot rotate them per request. Cloudflare also adds identifiable request headers. Site allowlists must account for both facts.

Legba's hosted sessions run on its infrastructure. Each view link ends with its session. The published skill states no retention period. Record that gap as unknown.

A credible comparison starts with one workflow. Choose a task containing authentication and review. Include expected failures and retry behavior. Then estimate monthly browser usage.

Map each step to an owner. Mark Workers code and external clients. Mark every saved state requirement. Mark every human approval point.

Keep Browser Run for broad programmability. Its documented interfaces support existing automation stacks. Its capacity model supports explicit planning. Its review tools cover operator transitions.

Evaluate Legba for narrower agent work. One skill covers routing and isolated sessions. Handoff covers steps that need a person. These cited scopes establish no broad replacement.