AntiBrow OEM edition: run an antidetect browser service under your own brand
Some teams do not want to send their users to someone else's antidetect browser. An agency running accounts for clients, a media buying team with its own tooling, a reseller with its own customer base: they want the browser to carry their name, the accounts to live on their servers, and the plans to be theirs to set.
That is what the OEM edition is for. You get the server, the admin panel and a desktop app under your brand, deployed on your own infrastructure. The browser engine is the same one AntiBrow ships, and it keeps getting engine updates.
What is in it
A server you deploy yourself. One codebase with two ways to run it: on Cloudflare Workers, or as a Node build in Docker. Users, API keys and plans live in a Postgres database you own. Profile archives for cloud sync live in any S3-compatible bucket, whether that is R2, MinIO, Aliyun OSS or your own object store. Schema changes ship as versioned Prisma migrations, so pulling an update does not mean hand-editing tables.
An admin panel. Sign in with a password you set in the server's environment. From there you define plans (concurrency and cloud sync limits), create users and put them on a plan with an optional expiry date, issue and revoke API keys, and set the latest and minimum desktop version your users are asked to install. Everything the panel does goes through an admin API that also accepts a bearer token, so your own billing system or back office can drive it directly.
A desktop app under your brand. Two ways to ship it, covered below.
Open SDKs that point at your server. The JavaScript SDK (anti-detect-browser on npm) and the Python SDK (antibrow on PyPI) take a server option, or read ANTI_DETECT_BROWSER_SERVER. Point them at your deployment and profiles, sync and engine tokens all come from you:
from antibrow import launch
browser = launch(profile="client-042", server="https://api.your-brand.com", api_key="...")
The SDK asks your server's /api/v1/config what it offers. Features your server does not run fail with a clear FeatureUnavailableError instead of quietly calling antibrow.com.
Two ways to ship the desktop app
Your own branded build. The desktop source comes through a private repository shared with you. You add a small config directory with your product name, app id, icon, accent color and server address, and a build workflow produces installers for macOS, Windows and Linux. The server address is compiled in, so users cannot point the app anywhere else. Your CI signs it with your own certificates and uploads the installers to your own storage, so the publisher your users see is you, not us.
No build at all. Your users install the official AntiBrow desktop app and enter your server address on the login page. The app reads your brand name, logo, accent color and links from your server and hides the features your server does not offer. The app itself, its icon and its updates stay AntiBrow's, because it is the same signed installer. This is the fastest way to start, and you can move to your own build later.
One safety rule applies to the second option: the official app only downloads the browser engine from AntiBrow's own download site, whatever a server's config says. Otherwise anyone could hand out a server address that makes the app fetch and run an arbitrary binary.
What is not included
The OEM edition is the core of the product, not all of it. Payments, a marketing site and end-user sign-up are yours to build around the admin panel; there is no self-service registration or email login, because how your customers pay and sign up is your business. These AntiBrow features are not part of it either:
- team features, and sharing or transferring profiles between users
- managed proxies (your users bring their own; on plans with cloud sync, their proxy list syncs along with their profiles)
- Live View
- the real-device fingerprint library (profiles use locally generated fingerprints)
Running it
The server lives in the server/ directory of the public repository, github.com/antibrow/antibrow, next to the SDKs. With Docker, the compose file starts the app, Postgres and an S3-compatible store on one machine, and the image runs database migrations on every start. On Cloudflare you run the migrations yourself before each deploy. The README lists every setting.
If you want to run it for your own users, the OEM edition page has the overview, and you can write to partners@antibrow.com with a little about your users and how you plan to run the service. Terms are per deal.
Try it on the free tier.
Unlimited local profiles, no credit card. Check it against the detectors yourself.