What is VeilBrowser
Concepts behind VeilBrowser: profiles, browser-level fingerprints, local-first execution and automation.
VeilBrowser is an antidetect browser platform. It gives every browser profile a consistent, browser-level fingerprint, runs each profile in isolation, and lets you drive profiles by hand or through automation.
Core concepts
Profile
A saved browser identity: fingerprint, proxy, storage and cookies. Profiles are isolated from each other.
Fingerprint
A curated browser build — canvas, WebGL, audio, fonts, client hints and device metrics — selected by OS and version criteria and stable across launches.
Launch / session
A running instance of a profile. Every launch exposes a CDP endpoint for automation.
Proxy
A per-profile network route over HTTP, HTTPS, SOCKS5 or SOCKS5H. Timezone, locale and geolocation align to the proxy's exit IP.
Why browser-level matters
Most tools patch fingerprint signals with JavaScript injected into a normal browser. Those patches drift: values change between launches and get correlated across sessions. VeilBrowser ships the signals inside the browser build itself, so a profile presents the same device every time you open it.
Consistency is the product
The goal is not a random fingerprint per launch — it is a stable, believable one per profile. One profile equals one device.
Local-first execution
Browsers run on your machines, through a worker. VeilBrowser manages profiles, teams and orchestration; the browser process and everything it writes to disk stay on your hardware, and page traffic leaves through the proxy you configured rather than through us. What does cross to VeilBrowser — account records, profile metadata, the launch authorization — is enumerated in the trust boundary. Enterprises can go further and self-host the entire stack.
Next steps
- Getting started — create and launch your first profile.
- Fingerprints — what a fingerprint is and what you control.
- Network and leak prevention — proxy-derived alignment, WebRTC and DNS.
- Run a worker — pull the image and start the thing that launches browsers.
- Connect — launch a profile and attach Puppeteer, Playwright or Selenium.
- API reference — provision and orchestrate over REST.