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
Canvas, WebGL, audio, fonts, client hints and device metrics — controlled at the browser level 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. Timezone and locale auto-align to the proxy 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 controls the signals at the runtime layer, 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 the Local API. VeilBrowser manages profiles, teams and orchestration; your actual browsing sessions never leave your infrastructure. Enterprises can go further and self-host the entire stack.
Next steps
- Getting started — create and launch your first profile.
- Automation — connect Puppeteer, Playwright or Selenium.
- API reference — provision and orchestrate over REST.