Every team building a computer-use agent eventually faces the same decision: run your own browser fleet or rent one. The rental market has exploded. Browserbase, the category leader, raised a $40M Series B at a $300M valuation in June 2025 and says it has served over 50 million browser sessions across more than 1,000 companies. Steel, Kernel, Hyperbrowser, Anchor Browser, Browser Use Cloud, Browserless and Cloudflare all sell hosted Chromium behind an API, and each one bills in a different unit. The headline rates look comparable at $0.02 to $0.12 per browser-hour. The actual bills are not.
Eight billing meters, one product

The cleanest way to see the spread is to walk the pricing pages, all checked against the field survey AC0.AI published on October 29, 2026, which normalized the market to between $0.02 and $0.24 per browser-hour.
Browserbase sells subscriptions with included hours and per-hour overage. The $20 Developer plan includes 100 browser hours, then bills $0.12 per hour. The $99 Startup plan includes 500 hours, then $0.10. That looks like the whole story until you read the rows underneath: proxy traffic is metered separately at $10 to $12 per GB depending on plan, Search calls run $5 per 1,000, the stateless Fetch API adds $1 per 1,000 calls, and model tokens pass through a Model Gateway at "Market price." A $99 plan can quietly become a $400 invoice if your agents move a lot of bytes.
Browser Use Cloud skipped subscriptions entirely: $0.02 per browser-hour, plus $5 per GB of residential proxy traffic that is on by default. Drop to direct routing and proxy traffic costs $0.20 per GB instead. Agent runs are billed as model cost plus a 20% fee. Concurrency is itself a meter: you start with 10 concurrent sessions and unlock 250 at $1,000 lifetime payments and 1,000 at $25,000. The $0.02 rate is the cheapest browser-hour in the market and routinely not the cheapest bill.
Kernel bills per GB-second, not per hour. A 1 GB headless browser running an hour costs about $0.06 at its published rate of $0.0000166667 per second; headful browsers cost 8 times more and GPU-accelerated sessions more again. The billing clock stops when a browser goes idle: Kernel's Standby Mode ends charges five seconds after the last CDP activity, which is a real difference for agents that pause to think. Idle browsers in a warm pool cost nothing, though they still occupy concurrency slots.
Anchor Browser runs a credit system with a per-task twist: plans list $5 in monthly free credits, a $50 Starter tier and a $2,000 Growth tier, and the docs' infrastructure rate card charges $0.01 per browser creation, $0.05 per browser hour and $0.01 per AI step. Note the creation fee: workloads built from thousands of short sessions pay a fixed toll per session that hour-billed rivals roll into time.
Hyperbrowser pools one credit balance across four products (browsers, sandboxes, web data, agents) at 1,000 credits to the dollar. Browser time is 100 credits per hour ($0.10), proxies 10,000 credits per GB ($10), fetches $0.001 per page, and sandboxes meter vCPU-hours and GiB-hours separately, like a cloud VM invoice wearing a browser costume.
Steel sells metered time ($0.10 per hour pay-as-you-go after $30 of one-time credits, $0.08 on the $250 Scale plan) around an Apache-2.0 open-source core, steel-browser, that you can run yourself. Browserless charges in "units": one unit is up to 30 seconds per connection, residential proxy traffic costs 6 units per megabyte and a CAPTCHA solve costs 10 units. At overage rates a continuously running browser costs roughly $0.24 per hour, the most expensive effective rate in AC0's table. Cloudflare Browser Rendering is the incumbent bundle play: 10 browser hours a month included with the $5 Workers Paid plan, then $0.09 per hour plus $2 per additional concurrent browser.
The proxy line is where budgets die

Time is easy to compare and hard to get wrong. Traffic is the opposite. Residential proxy bandwidth is what actually lets an agent past bot checks, and it is priced per gigabyte everywhere: $12/GB overage on Browserbase Developer, $10/GB on Hyperbrowser, $5/GB on Browser Use (default-on), $8/GB in Anchor's rate card, and Browserless converting every megabyte into 6 units, which at its $0.002 unit rate works out to about $12 per GB before your plan allowance.
Run the arithmetic a buyer has to do. A JS-heavy page with images moves 2 to 5 MB, per Anakin's comparison of the market. At 10,000 sessions a month and a 500 KB average you pay roughly $25 in proxy fees on Browser Use's $5/GB rate, on top of $10 of browser time. Push the average payload to 3 MB and the same fleet costs $150 in proxy traffic. The $0.02 hour becomes about $0.07 an hour on 500 KB pages and north of $0.30 on media-heavy 3 MB payloads, and the vendors whose pages you screenshotted will not all tell you the same number because payload size is yours, not theirs.
Stealth quality is the other side of that spend. Browser Use ran a benchmark of seven providers against 200 visits to 100 protected sites (its own study, so discount accordingly): Browser Use got through 90.5% of visits, Anchor 82%, Kernel 80.5%, Browserbase 78.5%, Browserless 77.5%, Steel 74.5% and Hyperbrowser 73.5%. A vendor that fails 1 in 4 sessions forces retries, and retries burn both meters. No independent number exists for the whole field at once; every cross-provider comparison currently published was written by one of the bidders.
Idle time, warm pools and the fine print on the clock
How the billing clock starts and stops matters as much as its rate. Browserless starts a fresh unit on reconnect. Anchor charges per browser created regardless of what it does afterward. Kernel stops the clock after five idle seconds, so agents that think for 90 seconds between clicks pay only for compute, not contemplation. Browser Use bills by the minute with a one-minute minimum and keeps residential proxies on by default. Browserbase counts browser hours but sells CAPTCHA solving, identity features and concurrency across plan tiers, so two users with identical usage can land in different plans.
The self-host lane is real but is a different purchase. Steel's core is Apache-2.0 and runs in Docker; Browserless offers a Docker build under SSPL or a commercial license; Kernel publishes its browser image as open source. What none of them open-source is the IP pool, the fingerprint maintenance and the CAPTCHA infrastructure that makes remote browsers worth renting in the first place. Self-hosting the container is the easy 20% of the problem.
How to actually pick
Price three workloads against the rate cards rather than the headline: your average session length, your average page weight, and your expected block-and-retry rate. If your sessions are short and bursty, per-browser fees (Anchor) and 30-second unit granularity (Browserless) will loom larger than hourly rate. If your agents pause between actions on long tasks, idle-billing policy separates Kernel from everyone else. If you already live on Cloudflare Workers, the included 10 hours make Browser Rendering free for prototyping and $0.09/hour after that, no subscription. And if your volume is large enough that concurrency is a constraint, remember that Browser Use sells it back to you as a function of lifetime spend.
The product across all these vendors is the same: a disposable Chromium that an agent can drive while looking human. What differs is where the meter sits and what it quietly multiplies. Compare bills, not rates.
Sources
- Browserbase pricing: https://browserbase.com/pricing
- Browserbase Series B: https://www.upstartsmedia.com/p/browserbase-raises-40m-and-launches-director and https://sacra.com/c/browserbase
- Browser Use Cloud pricing: https://browser-use.com/pricing
- Browser Use cloud browser comparison (Stealth Bench V2, vendor-run): https://browser-use.com/cloud-browsers
- Kernel pricing docs: https://kernel.sh/docs/info/pricing and https://www.usecarly.com/blog/kernel-browser
- Anchor Browser pricing docs: https://docs.anchorbrowser.io/pricing and https://aiagentstore.ai/ai-agent/anchor-browser
- Hyperbrowser pricing: https://www.hyperbrowser.ai/pricing
- Steel pricing and overview: https://steel.dev and https://aiidelist.com/ide/steel
- Browserless unit mechanics and plans: https://www.scrapeunblocker.com/compare/scrapeunblocker-vs-browserless and https://browser-use.com/posts/browser-use-vs-browserless
- Cloudflare Browser Rendering pricing: https://developers.cloudflare.com/browser-run/pricing
- AC0.AI cross-provider rate normalization (checked Oct 29, 2026): https://www.ac0.ai/en/field-notes/headless-browsers-ai-agents-comparison
- Proxy payload-size arithmetic: https://anakin.io/blog/firecrawl-browserbase-bright-data-ai-agents
