Introduction
Deploy, operate, and automate consistent browser identities across local machines or a self-hosted fleet.
VeilBrowser gives infrastructure and automation teams a controlled way to create, isolate, and operate browser identities at scale. Each profile keeps its fingerprint, proxy, storage, and network signals aligned across launches.
Choose your deployment path
Use Platform when VeilBrowser manages profiles, teams, and billing while browsers run through the Local API. Use Self-hosting when your organization operates the control plane and worker fleet inside its own network.
Platform
Create profiles, launch sessions, and automate with Puppeteer, Playwright, Selenium, or REST.
Self-hosting and enterprise
Deploy the control plane, operate worker fleets, and govern licensing on your infrastructure.
Start with an outcome
Launch your first profile
Go from account setup to a running, isolated browser identity.
Connect automation
Attach Puppeteer, Playwright, or Selenium over CDP.
Plan a self-hosted deployment
Understand control-plane, worker, release, and cloud boundaries.
Operate a production fleet
Manage releases, configuration changes, backups, and upgrades.
Enterprise operating model
Self-hosted VeilBrowser separates the control plane, worker fleet, and cloud licensing authority. Browser sessions stay on your infrastructure, operational changes remain auditable, and plan limits are enforced across the organization.