AntiBrow
The antidetect browser your AI agent can drive.

English | Русский

Kernel-level fingerprint spoofing, driven by the standard Playwright API you already write. Every profile carries a coherent real-device fingerprint — canvas, WebGL, WebGPU, audio, fonts, WebRTC and the protocol layer all agree, because they were sampled from one real machine rather than randomized independently.

This repository holds the open-source SDKs. See Licensing for what is and isn't open.

python/   →  PyPI: antibrow
js/       →  npm:  anti-detect-browser

Python

pip install antibrow

from antibrow import launch

browser = launch()                      # engine downloads on first run
page = browser.new_page()
page.goto("https://example.com")
browser.close()

JavaScript / TypeScript

npm install anti-detect-browser playwright-core

import { openProfile } from 'anti-detect-browser'

const session = await openProfile({ key: process.env.ANTIBROW_KEY, profileName: 'default' })
const page = await session.context.newPage()
await page.goto('https://example.com')
await session.close()

Both SDKs speak the same on-disk format: a profile created by one is launchable by the other, with the identical fingerprint.

• Engine-level spoofing, not JS injection. Fingerprints are produced inside Chromium's C++ layer, so there are no toString / prototype / stack-trace tells for a detector to find.
• Coherent real-device profiles. 30+ categories, 500+ parameters, all drawn from the same real machine. Randomized values contradict each other; these don't.
• Android profiles on a desktop machine. device_type="android" (deviceType: 'android' in JS) gives a profile a real phone's identity - mobile client hints, touch input, portrait screen, mobile GPU - with no device farm and no remote hardware. Real phones ship inside both packages, so it works on the free tier.
• Timezone and locale follow the proxy. Pass a proxy and the exit IP's geo is resolved and written into the fingerprint before launch.
• Proxy auth handled in the engine. http / https / socks5 credentials go inline on --proxy-server; the kernel answers the challenge itself. No helper extension is loaded, so nothing shows up in chrome://extensions.
• Persistent identities. Cookies, storage and passkeys survive restarts — warm an account once and it stays warm.
• Standard Playwright. You get a normal BrowserContext over CDP. No proprietary API to learn, and existing scripts port over by changing how the browser is launched.
• MCP server mode, so an AI agent can drive a profile directly.
• Recipes: task-level site adapters. Ask for reddit/hot and get JSON, instead of a browser handle and a scraping problem. See below.

One command per site, published in a separate repository (antibrow/recipes) and shared by both SDKs, so adding a site is a pull request there rather than a release here.

anti-detect-browser recipe run google/search --profile shopper-01 --jq '.items[].title'
anti-detect-browser recipe fanout amazon/search --profiles 'shopper-*' --concurrency 4

from antibrow import run_recipe, fanout_recipe

print(run_recipe("reddit/hot", temporary=True, args={"limit": 5}).value)

Covered today: Google, Amazon, Walmart, Reddit, X, Medium, Yelp, Indeed, Hacker News, DuckDuckGo, GitHub, PyPI, npm, plus exit-IP and fingerprint checks. Several of those answer a plain scraper with a captcha, which is the point: a recipe runs inside a profile with its own identity and its own exit IP, and fanout runs the same command on N of them at once. Recipes are pinned by SHA-256, only reviewed ones run by default, and each one may only reach the hosts it declares - a request to any other host is blocked.

Want a platform that is not there yet? Sites behind Cloudflare, DataDome, PerimeterX or Akamai are the ones this layer exists for. Open an issue on the recipes repo, or write one from its GUIDE.md - the format is a single file with no dependencies.

Windows x64, macOS (universal) and Linux x64 / arm64.

Read this before you build on it — the SDK and the engine have different licenses.

• The SDKs in this repository are MIT (LICENSE). Use them anywhere, including commercially.
• The browser engine is a closed-source binary distributed separately, under BINARY-LICENSE.md. In short: you may use it for your own work, including commercial work, at any company size — but you may not redistribute, resell, repackage or embed it, and exposing it to third-party customers (bundled, hosted, or behind your own API) needs a separate OEM/SaaS license.
• Listing these packages as a dependency is not redistribution, because the engine is downloaded from official AntiBrow channels on the user's own machine.

BINARY-LICENSE.md is the authoritative text; the summary above is not a substitute for it.

Automating systems without authorization, credential stuffing and bulk account-creation abuse are prohibited. You are responsible for complying with the terms of the sites you automate and with the law in your jurisdiction.

• Website — https://antibrow.com
• Documentation — https://antibrow.com/docs
• Issues — https://github.com/antibrow/antibrow/issues