OEM edition

Your own antidetect browser service, on your infrastructure.

Get the server, the admin panel and a desktop app under your brand. Your users sign in to your service, your data stays on your servers, and the browser engine is the same one AntiBrow ships.

What you get.

Full source and control

The complete server and admin panel source, deployed on your own infrastructure. You decide who gets access, on which plan, and when.

Your server, your admin panel

Create users and API keys and set concurrency and cloud sync limits per plan. The admin API is documented and token-authenticated, so you can build your own front end on it.

Your branded desktop app

Build the desktop app under your own name, logo and colors with your server address baked in. Or skip the build entirely - see the two options below.

Open SDKs on your server

The JavaScript and Python SDKs can point at your server. Profiles, sync and engine tokens all come from you.

The same browser engine

The same engine AntiBrow uses, downloaded from the AntiBrow download site, with engine updates as they ship.

Source you can follow

The server and SDKs are open source on GitHub; pull updates when you want them. The desktop app source comes through a private repository shared with you.

Two ways to ship the desktop app.

Pick what fits your team. You can start with the second and move to the first later.

Option 1

Your own branded build

Build the desktop app yourself from a private repository shared with you, with your name, logo, colors and server address built in. Your own CI builds and signs it and you host the installers on your storage; the app carries your brand, not ours.

Option 2

No build: a custom server on the official app

Users install the official AntiBrow desktop app and enter your server address on the login page. The app picks up your name, logo, colors and links from your server, and hides features your server does not offer. There is nothing to compile or sign. The app itself stays AntiBrow, with its own icon and updates.

How you deploy it.

One codebase, two ways to run it. Step-by-step instructions are in the server deployment docs on GitHub.

Cloudflare Workers

No servers to manage. You still provide Postgres and an S3-compatible bucket, and run database migrations before each deploy.

Docker

Run the Node build in a container next to your other services.

S3-compatible storage

Profile archives live in any S3-compatible bucket: your cloud, or self-hosted.

Postgres

Users, keys and plans in a Postgres database you own, with versioned migrations.

What the admin panel does.

Plans

Define concurrency and cloud sync limits. Change a plan and it applies to everyone on it.

Users

Create, disable and re-plan users.

Admin access

The panel is protected by a password you set in your environment. Scripts can use a bearer token.

API keys

Issue and revoke keys per user. A revoked key stops working for all API calls.

Desktop releases

Set the latest and minimum desktop version your users are prompted to install.

What is not included.

Payments, a marketing site and end-user sign-up are yours to build around the admin panel. These AntiBrow features are not part of the OEM edition:

Talk to us.

Tell us about your users and how you plan to run the service, and we will get back to you with terms and next steps.