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 agent skill provides routing and isolation. The agent stack retains permissions and logs. The cited homepage establishes 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 during 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.

This page evaluates 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.

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 can reduce orchestration choices. It cannot prove code-level compatibility.

Cloudflare provides several observation paths. Live View supports interactive browser access. Native developer tools remain available. Generated CDP links expire after configured windows.

Structured handoff supports human intervention. The documented timeout reaches thirty minutes. Applications receive completion signals afterward. That creates an explicit control transition.

Session recording remains a beta feature. It records structured rrweb events. It does not produce video files. Recordings remain available for thirty days.

These details matter during procurement. Operators may need live intervention. Reviewers may need later evidence. The cited homepage establishes no matching review surface.

Cloudflare publishes usage and concurrency pricing. Free accounts receive ten browser minutes daily. They also receive three concurrent sessions. Paid accounts include ten browser hours monthly.

Additional paid usage costs nine cents hourly. Included concurrency equals ten averaged browsers. Added average concurrency costs two dollars. Billing follows documented monthly calculations.

Paid defaults now allow two hundred browsers. New launches default to three each second. Quick Actions default to thirty each second. Cloudflare accepts requests for higher limits.

Capacity limits differ from included capacity. Procurement models should separate both numbers. Usage cost and concurrency cost also differ. A representative workload reveals both charges.

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

Opt-in recordings remain thirty days. Quick Action caching defaults to five 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. Routing requirements must account for both facts.

Legba states browser sessions run elsewhere. It also provides routing within its skill. The cited homepage establishes no matching retention controls. 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. Routing and isolation arrive together. That may simplify one workflow boundary. These cited scopes establish no broad replacement.