What is it
Browser-hour pricing is a billing unit where each hour of headless browser compute time is metered, common in web scraping and browser automation platforms.
The browser-hour is the scraping equivalent of the GPU-hour: you pay for the time a real browser engine is running — rendering JavaScript, executing event handlers, and waiting on network responses. Browserbase surfaces the unit most explicitly because it operates a fleet of cloud-hosted Chromium instances; the cost it must cover is raw compute time, not a proxy like page counts or bytes transferred. Its plans bundle an hour pool (1 hour free, 100 on the $20/mo Developer plan, 500 on the $99/mo Startup plan) and then meter overage at $0.12/browser hr (Developer) or $0.10/browser hr (Startup). Browserbase notes a typical scrape runs under two minutes, so 100 hours is roughly 3,000 page-level tasks.
What distinguishes browser-hours from simpler per-request models is the treatment of rendering complexity. A static HTML page might return in under a second; a React SPA with lazy-loaded content can hold a browser session open for 10–30 seconds. Per-request models hide that variation; browser-hours expose it. This makes the unit better aligned with actual infrastructure cost, though it is harder for customers to forecast without running representative test workloads — the kind of usage-based metering trade-off that trades predictability for fairness.
Firecrawl and ZenRows both run real browser sessions for JavaScript-rendered pages but express the browser-hour cost through their primary unit rather than as a headline hour. Firecrawl’s Interact endpoint costs 2 credits per browser minute, and ZenRows meters its Scraping Browser at $0.09 per session-hour (billed in 30-second increments) drawn from a shared dollar balance. The three-company corpus therefore spans a spectrum: Browserbase (a direct browser-hour meter), ZenRows (an explicit per-session-hour line inside a shared balance), and Firecrawl (browser minutes priced as credits).
How it works
Browser-hour billing starts a timer when a headless browser session opens and stops when the session closes. The platform converts session time to billing units — usually fractional hours or minutes — and aggregates across the customer’s account for the billing period.
| Company | Browser billing unit | Published rate | Free tier |
|---|---|---|---|
| Browserbase | Browser-hours (session compute time) | $0.12/hr (Developer, after 100 hrs); $0.10/hr (Startup, after 500 hrs) | Yes — 1 browser hour free |
| Firecrawl | Browser minutes, priced in credits | 2 credits/browser minute (Interact); Scrape/Crawl 1 credit/page | Yes — 1,000 credits/month |
| ZenRows | Session-hours (Scraping Browser) | $0.09/session-hour, 30-second increments, from a shared balance | Yes — 14-day trial ($1 allowance) |
The unit math for browser-hour pricing:
Cost = hours × hourly rate, where hours = Σ(session_duration in hours) across all sessions in the billing period.
Worked example (Browserbase Startup plan). A team runs 800 browser hours in a month. The $99/mo Startup plan includes 500 hours, leaving 300 overage hours at $0.10/hr = $30. Total browser-hour cost for the month is $99 + $30 = $129, before Search, Fetch, proxy, or model-token charges.
Concurrency is an important secondary dimension. Most platforms gate the number of simultaneous browser sessions by tier — a customer running 5 concurrent browsers accumulates 5× the hours of a single-session customer for the same wall-clock time. Browserbase exposes concurrent-session limits per plan (3 on Free, 25 on Developer, 100 on Startup, 250+ on Scale), making concurrency a capacity dimension alongside the raw hour count; ZenRows similarly scales concurrency from 5 on the trial to 400 on Business 3K. For Firecrawl, browser time folds into the credit ledger: an Interact run burns 2 credits per browser minute, so heavy browser automation quietly draws down the same monthly pool that a plain 1-credit-per-page Scrape uses. See billing-cycle mechanics for how these aggregated meters roll up into an invoice.
Companies using this
All three companies in the corpus meter browser compute time, differing only in how visible the hour is: a direct meter on Browserbase, an explicit session-hour line inside a shared balance on ZenRows, and browser minutes folded into credits on Firecrawl. Each targets engineering teams building web data-extraction and browser-automation pipelines at scale.
| Company | Product | Pricing model | Billing units | Free tier | Verified |
|---|---|---|---|---|---|
| Browserbase | Browser-agent infrastructure: headless browser sessions, web Search/Fetch APIs, agent identity, runtime, and a model gateway behind one API key | Yes | 2026-06-02 | ||
| Firecrawl | Web-scraping and data-extraction API for AI agents — scrape, crawl, map, search, and extract pages into clean markdown/JSON | Yes | 2026-07-30 | ||
| ZenRows | Fetch, Extract, Batch, and Browser Sessions (plus legacy standalone Residential Proxies) | Yes | 2026-08-04 |
Explore this theme in the knowledge graph
FAQ
What is browser-hour pricing for web scraping platforms?
Browser-hour pricing meters the amount of headless browser compute time consumed — each hour of a running Chrome or equivalent instance counts against a metered allowance. Browserbase charges per browser hour of session time (overage $0.12/hr on Developer, $0.10/hr on Startup); Firecrawl and ZenRows fold browser compute into their credit or shared-balance bundles. The unit is analogous to GPU-hours in ML infrastructure: it captures the dominant cost — compute while the browser renders JavaScript — rather than a proxy like page count.
How much does a browser hour cost?
On Browserbase, browser-hour overage is $0.12 per browser hour on the $20/mo Developer plan and $0.10 per browser hour on the $99/mo Startup plan, after each plan's included pool (100 and 500 hours). Firecrawl expresses browser time as credits — its Interact endpoint costs 2 credits per browser minute (≈120 credits/hour). ZenRows meters its Scraping Browser at $0.09 per session-hour, billed in 30-second increments, drawn from a shared dollar balance.
How does browser-hour pricing compare to per-request pricing for scraping?
Per-request pricing charges per URL fetched regardless of how long the page takes; browser-hour pricing charges for actual compute time. For heavy JavaScript-rendered sites a single page can hold a browser session open for 10–30 seconds, making per-request pricing unpredictable. Browserbase meters browser hours directly so slow crawls of complex SPAs pay proportional to the compute consumed. ZenRows and Firecrawl use request- and credit-based models but surface browser time as a separate line (a $0.09 session-hour and a 2-credit browser minute, respectively), bridging the two approaches.
Which companies use browser-hour pricing?
Three companies in the UsagePricing blueprint corpus meter browser compute time: Browserbase (a direct browser-hour meter), Firecrawl (browser minutes priced in credits via its Interact endpoint), and ZenRows (a $0.09/session-hour Scraping Browser drawn from a shared balance). All three target engineering teams building web data-extraction and browser-automation pipelines.
Related billing units
- Credit-Based BillingA billing unit where customers pre-purchase or are allocated a pool of credits that deplete as they use the product, often at variable rates per feature.
- Token-Based PricingA billing unit common in LLM and AI products, where customers are charged per input and output token processed.
- Per-Seat PricingA billing unit where the vendor charges a fixed fee per named user, regardless of how much each user consumes.
- Per-Resolution PricingA billing unit unique to AI customer-support products, where the vendor charges only when an AI agent resolves a customer issue without escalation.
- Bandwidth-Based PricingA billing unit where customers are charged per gigabyte of data transferred out of the platform.
- Per-Function-Invocation PricingA billing unit where customers are charged per serverless function invocation, often combined with a separate compute-time charge.
- CPU-Hour PricingA billing unit where customers are charged for the CPU time their workloads consume, typically measured in vCPU-seconds or vCPU-hours.
- GB-Hour PricingA billing unit where customers are charged for the memory their workloads consume over time, measured in gigabyte-hours.
- GPU-Hour PricingA billing unit where customers are charged for GPU time consumed, typically measured per-second or per-hour by GPU type.
- Per-API-Call PricingA billing unit where customers are charged per API request, regardless of payload size or processing time.
- Per-GB Storage PricingA billing unit where customers are charged per gigabyte of data stored on the platform per month.
- Media-Minute PricingA billing unit where customers are charged per minute of audio or video processed — used by speech, voice, and video AI vendors.
- Per-Request PricingA billing unit where customers are charged per request served — the generic meter for inference endpoints, search, scraping, and browser infrastructure.
- Per-Event PricingA billing unit where customers are charged per event ingested — the native meter of observability and billing-infrastructure platforms.
- Vector Storage PricingA billing unit where customers are charged for vectors stored or indexed — the storage dimension of vector database pricing.
- Per-Character PricingA billing unit where customers are charged per character of text processed — the standard meter for text-to-speech and translation.
- Per-Document PricingA billing unit where customers are charged per document processed or generated — common in AI writing, SEO, and document-intelligence tools.
- Per-Page PricingA billing unit where customers are charged per page crawled, parsed, or rendered — the meter for web scraping and document parsing.
- Per-Transaction PricingA billing unit where customers are charged per financial or billing transaction processed — the meter of billing and accounting platforms.
- Active-User PricingA billing unit where customers are charged per monthly or daily active user rather than per provisioned seat.
- Per-Task PricingA billing unit where customers are charged per task an automation or agent executes — Zapier's historical unit, now spreading to AI agents.
- Per-Unit PricingA billing unit used by robotics, hardware AI, and some SaaS companies where the metered object is a physical or abstract 'unit' — a robot deployed, a device sold, or a defined deliverable.
- Workflow Execution PricingA billing unit where each end-to-end workflow or automation run is metered and billed, regardless of the compute steps it contains.
- Per-Message PricingA billing unit where each individual message or reply in a conversation is metered, common in AI chat and voice platforms.
- Per-Invoice PricingA billing unit used by billing infrastructure platforms where each invoice generated or processed is metered as the primary cost driver.
- Per-Action PricingA billing unit where each discrete action taken by an AI agent or automation is metered — common in browser automation and agentic workflow tools.
- Per-Image PricingA billing unit where each AI-generated image is metered, common in image generation APIs and multimodal AI platforms.
- Per-Conversation PricingA billing unit where each complete customer conversation — from first message to resolution — is metered as a single chargeable event.
- Per-Record PricingA billing unit where each data record processed, labeled, or extracted is metered — common in data platforms and web scraping services.
- Per-Word PricingA billing unit common in translation and localization platforms where the metered object is the word count of content processed.
- Per-Video PricingA billing unit where each AI-generated video is metered, common in video generation and synthetic media platforms.
- Milestone-Based PricingA billing unit used in drug discovery and biotech AI where payment is tied to achieving defined research milestones rather than time or compute consumed.
- Per-Outcome PricingA billing unit where payment is triggered by verified outcomes delivered — distinct from outcome-based pricing models, this refers specifically to 'outcomes' as a countable billing unit.
- Per-Datapoint PricingA billing unit where each individual data measurement or signal ingested is metered — common in cloud cost intelligence and ML evaluation platforms.
- Per-Interaction PricingA billing unit where each patient-agent or user-agent interaction is metered, common in healthcare AI and customer engagement platforms.
- Data Licensing PricingA pricing structure where access to proprietary datasets or data assets is licensed separately from the software or services, common in AI training data and clinical data platforms.
- Robot-Hour PricingA billing unit where each hour a robot or autonomous system operates is metered — the robotics equivalent of a GPU-hour.
- Per-Contact PricingA billing unit where each contact or lead in the database is metered, common in AI sales development and outbound automation platforms.
- Per-Mailbox PricingA billing unit where each connected email mailbox or sending account is metered, common in AI outbound sales and email automation platforms.
- Per-Generation PricingA billing unit where each AI-generated creative asset — image, video, or design — is counted as a 'generation' and metered accordingly.
- Per-Ticket PricingA billing unit where each customer support ticket handled by an AI agent is metered — common in AI customer service platforms.
- Per-Log PricingA billing unit where each LLM request log ingested or stored is metered — common in AI observability and evaluation platforms.
- Per-Trace PricingA billing unit where each distributed trace — a complete record of an LLM request chain — is metered, common in AI observability platforms.
- Per-IP PricingA billing unit where each IP address or proxy endpoint allocated is metered — used by web scraping proxy providers.
- Per-Device PricingA billing unit where each hardware device or endpoint connected to the AI platform is metered.
- Per-Case PricingA billing unit used in legal AI platforms where each case or matter processed by the AI is metered.
- Per-Report PricingA billing unit where each AI-generated report or analysis document is metered as a discrete output.