Hyperbrowser sells one credit pool across cloud browsers, sandboxes, a web API and hosted agents, and its profiles are read-only unless you ask otherwise. AntiBrow runs persistent fingerprinted profiles on your own machine. Pricing and docs captured 2026-10-22.
Hyperbrowser sells four things on one credit balance: cloud browsers, compute sandboxes, a fetch and search API, and hosted agents. Only the first overlaps with an antidetect browser, and only when the agent signs in somewhere and must keep that login. This page covers that overlap: how Hyperbrowser profiles save state, what a typical agent run costs in credits, and what AntiBrow does instead.
Pricing below is from hyperbrowser.ai/pricing. Behaviour is from their docs on profiles, stealth, session lifecycle and regions. All captured 2026-10-22.
The unit is a credit, and 1,000 credits equal $1 of usage. Every plan's credits work across all four products: browsers, sandboxes, the web API and AI agents.
| Plan | Price | Included | Concurrent sessions | Data retention | Stealth |
|---|---|---|---|---|---|
| Free | $0 | 5,000 credits | 1 | 7 days | - |
| Startup | $30/mo | 30,000 credits | 25 | 30 days | basic |
| Scale | $100/mo | 100,000 credits | 100 | 30 days | basic |
| Enterprise | custom | custom | 1,000+ | 180+ days | ultra |
At the listed rates a browser costs 100 credits per hour ($0.10/hr) and proxy data 10,000 credits per GB ($10/GB). Agent steps through HyperAgent or Browser Use add 20 credits per step on top of browser time. Paid plans include automatic CAPTCHA solving. Plan credits reset at renewal and do not roll over.
Profiles are read-only unless you say otherwise. A Hyperbrowser profile is "a saved snapshot of a browser's user data directory": cookies, local storage, session storage and cache. To write to it you pass persistChanges: true when creating the session, and the default is false. Forget that flag after a login and the next session starts from the old snapshot. The docs also note profiles "can take a few seconds" to save after the session closes, and that Playwright or Puppeteer must use the default context for profiles to work.
The fingerprint is a session parameter. The session-create API takes operatingSystems, device, platform, locales and screen. The profiles page lists what a profile stores, and the fingerprint is not on that list.
Stealth is tiered. Paid plans get basic stealth mode. The stealth doc says ultra stealth "is only available on enterprise plans."
Sessions end on their own. A session stops at its timeout, from a team default or timeoutMinutes, and by default when your automation library disconnects, unless you add keepAlive=true to the WebSocket URL. Regions are us-central, us-east and us-west, with asia-south on Enterprise and Select plans.
None of this is a flaw for fast, isolated, disposable work. It just leaves keeping an identity stable to you.
The browser hour is the cheap line on that page. Take a task of 30 HyperAgent steps that keeps a browser open for 10 minutes and pulls 50 MB through a proxy: steps cost 600 credits, browser time about 17, proxy data about 500. Roughly 1,117 credits, or $1.12. On those assumptions Free covers four such runs and Startup about 27 a month. Your step count and page weight will differ, but steps and proxy traffic dominate, so a cheaper browser hour elsewhere changes little. Model your real task before comparing anyone's headline rate, ours included.
An AntiBrow profile is a directory on your own disk, and the browser writes cookies, localStorage, IndexedDB and passkeys into it the way any browser writes to its user data. There is no persistChanges to remember after a login, and the fingerprint is generated once per profile and stays with it, applied in the browser engine below the JavaScript layer. A passkey an agent enrolls is replayed at the next sign-in by the profile's own virtual authenticator (details).
For the agent itself, the SDK runs as an MCP server via npx anti-detect-browser --mcp and the browser stays alive between tool calls, so there is no session timeout or keepAlive to manage. See MCP browser automation. There are no credits: local profiles are unlimited on every plan, and paid plans from $9.9/mo meter concurrent browsers. You pay instead by running the machine yourself.
Proxy reputation, behaviour and account history decide most detection outcomes, on any platform. We have no current test run comparing the two products, so this page does not claim either is detected less.
In Hyperbrowser, sign in to a test account on a profile once with persistChanges: true and once without, and see which next session is still signed in; per their docs, only the first.
Then compare devices. Open CreepJS in two sessions on that profile with identical operatingSystems, device and screen values, and in two launches of one AntiBrow profile. Record navigator.userAgent, screen.width, Intl.DateTimeFormat().resolvedOptions().timeZone and the fingerprint ID, and see which setup reports the same machine twice. The consistency check lists more fields worth comparing.
Unlimited local profiles on the free tier, no card. Run the detectors before you trust any of this.