How Hyperbrowser Pricing Works and What the Free Tier Includes

Updated

Hyperbrowser starts with a free account at $0 that includes 5,000 credits, and paid tiers are listed on its pricing page. The free credits let you test browser sessions, sandboxes, and Web API calls before committing to a plan. The site does not publish per-credit rates or what each action costs in credits, so treat the pricing page as the source of truth for tiers and usage rates.

What the Free Tier Covers

The free tier is a credit allowance, not a separate product. The same platform features are available:

  • Cloud Chrome sessions controlled through an API, with Playwright or Puppeteer connections
  • Sandboxes (isolated microVMs) for running code, installing dependencies, and saving memory snapshots
  • Web API calls that fetch pages, crawl sites, or search the web and return Markdown, HTML, screenshots, or schema-matched JSON
  • AI agents such as HyperAgent, Browser Use, or computer-use models in a managed browser

With 5,000 credits, the practical question is how far that goes. Because the site does not state a credit-to-action conversion, the reliable approach is to run a small representative task first and check your credit balance afterward.

What Consumes Credits

Every billable surface on the platform is a candidate for credit usage:

Surface What it does What likely drives cost
Browser sessions Cloud-hosted Chrome via API Number and duration of sessions
Sandboxes Isolated VMs for code execution Runtime and snapshot storage
Web API Fetch, crawl, search Number of pages or requests
AI agents Prompt-driven browser tasks Task length and steps taken

The platform advertises 100M+ sessions run, 1,000+ concurrent sessions, and under 500 ms startup from request to ready browser. Those figures describe capacity, not price. Concurrency and session volume are the levers that will most affect a paid plan, so size your plan around peak parallel sessions rather than total monthly runs alone.

A Practical Way to Test the Free Tier

  1. Create a free account and confirm the 5,000-credit balance.
  2. Run one small task per surface — for example, a single Web API fetch of one page, one short browser session, and one sandbox command.
  3. Check the credit balance after each step to see which surface consumes credits fastest.
  4. Scale the test to a realistic workload, such as a crawl of a few dozen pages, and compare consumption against your expected monthly volume.
  5. Use the result to pick a paid tier on the pricing page.

Expected result: you learn your own cost per task, which is more useful than a generic rate because usage patterns differ sharply between a fetch-heavy pipeline and long-running agent sessions.

Decision Factors Before Paying

  • Concurrency needs: if you run many agents in parallel, the 1,000+ concurrent session capacity matters more than total credits.
  • Session volume: high-volume scraping favors predictable per-request pricing; long interactive sessions favor plans priced by runtime.
  • Startup requirements: the sub-500 ms startup is a platform feature, not a paid add-on, so it should not change your tier choice.
  • State reuse: saved browser profiles and memory snapshots reduce repeated setup work, which can lower effective usage.

Common Pitfalls

  • Assuming the free tier is unlimited because the account costs $0 — it is a 5,000-credit allowance.
  • Estimating cost from the marketing metrics (100M+ sessions, 1,000+ concurrency) instead of from your own test runs.
  • Forgetting that sandbox snapshots and agent tasks may consume credits differently from simple fetches.

For exact tier names, prices, and credit rates, check the pricing page at hyperbrowser.ai/pricing, since those details are not included in the available site information.