What is a cloud browser?

Cloud browsers change a bill because their meters often follow consumed resources rather than completed pages. Session time, rounding, proxy traffic, CAPTCHA attempts, concurrent sessions, browser creation, and operation calls can each matter. Leaving a session open can remain billable even when no useful output is produced. (Browserbase cost optimization, Browserless unit consumption, and Bright Data Browser API, checked 2026-07-25.)

Browserbase plans include browser hours and residential proxy data as separate allowances, with separate overage meters. Each created browser session has a one-minute minimum billing period, and a keep-alive session must be explicitly released or it continues billing until its timeout. Its plans also set concurrent-browser limits. (Browserbase pricing, Browserbase cost optimization, and Browserbase keep-alive sessions, checked 2026-07-25.)

Browserless uses a shared Unit balance. Browser time costs one Unit per started thirty-second increment; datacenter and residential proxy data add separate Units per megabyte; and each CAPTCHA solve attempt consumes Units under the billing documentation, even if the attempt fails. The pricing page instead describes the CAPTCHA meter per successful solve, so the two first-party statements do not reconcile. Session-duration caps and concurrency vary by plan. (Browserless unit consumption and Browserless pricing, checked 2026-07-25.)

Bright Data Browser API takes a different approach: it bills traffic transferred through the managed browser and publishes no separate session-time fee. The product automatically chooses the IP type, and premium-domain traffic can use a higher rate that is visible in customer configuration rather than on the public page. Each session supports one initial navigation under the reviewed FAQ. (Bright Data Browser API and Bright Data Browser API FAQ, checked 2026-07-25.)

Firecrawl Browser Sandbox uses credits per browser minute and currently allows up to twenty concurrent browser sessions on all plans. Firecrawl’s Interact mode has its own timeouts and remains billable until stopped or expired, while an initial scrape is billed separately from interaction time. (Firecrawl Browser Sandbox and Firecrawl Interact, checked 2026-07-26.)

Before signing up, measure active session duration, page traffic, session count, and expected concurrency. Check time rounding, minimums, inactivity timeout, maximum duration, proxy and CAPTCHA meters, and the exact stop or release call. A page-count estimate is insufficient when the product bills time or bytes. (Browserbase cost optimization, Browserless unit consumption, and Bright Data Browser API FAQ, checked 2026-07-25; Firecrawl Interact, checked 2026-07-26.)