Self-hosting the OEM edition

The OEM edition runs the AntiBrow service on your own infrastructure: the API server the SDKs and the desktop app talk to, plus an admin panel for plans, users and keys. The source is MIT-licensed, in the server/ directory of the public repository, whose README is the full reference. This page is the short version. What the edition includes and leaves out is on the OEM edition page.

What you need

  • PostgreSQL 15 or newer.
  • An S3-compatible bucket (R2, MinIO, Aliyun OSS and similar) if your users get cloud sync.
  • Either a Docker host or a Cloudflare account. One codebase builds for both.
  • An engine signing key arranged with us (see FP_LICENSE_PRIVKEY below).

Run with Docker

cp .env.example .env   # set FP_LICENSE_PRIVKEY
docker compose up -d --build
curl localhost:4321/api/v1/health

The compose file starts the app, PostgreSQL 17 and an S3-compatible object store on one machine. The image runs prisma migrate deploy on every start, so the database is migrated before the server listens. For a real deployment, set S3_PUBLIC_ENDPOINT to an address your users can reach; the compose default only works on the same machine.

Run on Cloudflare Workers

pnpm build:cf
DATABASE_URL=postgresql://... pnpm db:migrate

Copy deploy/cloudflare.jsonc.example to your own config, set the secrets it lists with the Cloudflare CLI, and deploy the dist directory. You still provide PostgreSQL and the bucket. Run the migrations yourself before each deploy.

Configuration

  • DATABASE_URL - PostgreSQL connection string. Required.
  • FP_LICENSE_PRIVKEY - Ed25519 seed (64 hex characters) that signs engine license tokens. Required. The engine has to recognize your signing key, so arrange it with us when you set up the OEM edition.
  • OEM_ADMIN_PASSWORD - Password for the admin panel. Without it every admin route answers 404, bearer token included.
  • OEM_ADMIN_TOKEN - Optional bearer token for scripts calling the admin API.
  • OEM_SESSION_SECRET - Signs the admin session cookie.
  • S3_ENDPOINT, S3_BUCKET, S3_ACCESS_KEY_ID, S3_SECRET_ACCESS_KEY - S3-compatible storage for profile archives. All four together, or none (no cloud sync).
  • S3_PUBLIC_ENDPOINT - The address clients use for presigned uploads and downloads, if it differs from S3_ENDPOINT. Must be reachable by your users.
  • S3_ADDRESSING, S3_REGION - path (default) or virtual addressing. Aliyun OSS needs virtual and its region id.
  • OEM_PUBLIC_URL, OEM_BRAND_NAME - Your public server address and the brand name clients show.
  • KERNEL_MANIFEST_URL - Engine catalogue. Defaults to the AntiBrow download site.

Admin panel & API

Open /admin and sign in with OEM_ADMIN_PASSWORD. There you create plans (concurrency and cloud sync limits), create users on a plan with an optional expiry date, issue and revoke API keys, and set the latest and minimum desktop version. The first migration seeds a FREE default plan; users whose plan expires fall back to it.

Everything the panel does goes through the admin API under /api/admin/ (plans, users, users/:id/keys, releases, status), which also accepts Authorization: Bearer <OEM_ADMIN_TOKEN>. That is how your own billing or back office creates users and extends plans.

Point the SDKs at it

from antibrow import launch

browser = launch(profile="client-042", server="https://api.your-brand.com", api_key="...")

The JavaScript SDK takes the same server option, and both read ANTI_DETECT_BROWSER_SERVER. The SDK reads your server's /api/v1/config to learn what it offers; features it does not run raise FeatureUnavailableError instead of calling antibrow.com.

Desktop app

Two options. Without building anything, your users install the official AntiBrow app and enter your server address on the login page; the app shows your brand name, logo, color and links from your server, and still downloads the engine only from the AntiBrow download site. Or build your own branded app from the private desktop repository shared with you, with your server address compiled in, signed by your own certificates and published to your own storage.

Updates

Pull new versions of server/ from GitHub when you want them. Schema changes ship only as Prisma migrations, and every change has a version and a changelog entry. Questions about setup or terms: partners@antibrow.com.