an anti-detect browser, driven by AI. Write one sentence. Get a pipeline that runs every morning.
Each profile is a browser with its own identity. Your AI assistant drives them all over MCP.
One machine. Four fully separate browsers.
Every profile is a different person — down to the details.
Chrome · Windows 111920 × 1080 · 24-bitNVIDIA GeForce RTX 3060noise unique to this profilethe Windows font setpatched right in the Chromium source
Asia/Tokyo · matches the proxyja-JP · Accept-Languagereal IP not exposed35.68, 139.69SOCKS5 · this profile onlyFingerprints are set inside Chromium's C++ code, not injected into the page.
A site checks a fingerprint by asking the browser. With Veilus, the answer comes from Chromium's own C++ code — there is no script in between for the site to find.
navigator.hardwareConcurrencyget() → 12 fn.toString()no longer reads [native code]getOwnPropertyDescriptor()the getter is not Chrome'snew Error().stackan extra frame from the scriptperformance.now()how long each call takes
real valueThe site reads 12 — through a layer it can inspect.
navigator.hardwareConcurrency12set here The site reads 12 — straight from Chromium.
59 fingerprint fields, every one read by C++ code inside the engine: Canvas · WebGL · WebGPU · Audio · Fonts · Screen · Client Hints · Timezone · WebRTC · Media devices · Speech voices · Geolocation · Battery · Automation signals
You give the order. The AI writes, tests, fixes. You approve once.
veilus mcp
Profiles you've warmed up for months don't die with one broken machine.
Queue the whole batch. Veilus opens profiles at the pace your machine can take.
One limit covers every browser the app opens — by hand, on a schedule, from the API or an AI agent: at most 16 at once. Runs wait for a free slot instead of failing, and check the machine before every launch.
- 1Above 75% CPU or 80% RAM: 5 s between launches.
- 2Above 90% CPU or RAM: new launches wait, checked again every 3 s, for up to 60 s.
- All 16 busy and you open one more by hand? Veilus tells you instead of starting it.
- Each run sets its own concurrency, under the same limit.
- An AI agent can ask how many slots are free before it starts a run.
Enough to run many accounts on one machine.
GET /v1/profiles POST /v1/scripts/run $ veilus mcp
Simple, transparent
Start free. Pay monthly, or pay once and keep it forever.
- 5 profiles
- 1 device
- Latest browser engine
- Proxy support
- No Veilus Flow, scheduling, batch runs or local API/MCP
- Unlimited profiles
- Veilus Flow automation
- Scheduling and batch runs
- Local REST API and MCP
- Veilus Sync
- Script templates
- Latest browser engine
- Everything in Monthly
- Lifetime updates · 3 years of support (renewal: 40% of the plan price per 3 years)
Frequently asked questions
What people ask before they download.
01Will platforms detect my profiles?
No tool can promise that, and we don't. Each profile runs on Veilus's own patched Chromium build with its own fingerprint and proxy, and we test profiles with creepjs and iphey. How your accounts are treated also depends on how you use them.
02Is it really free? Do I need a card?
Yes. The Free plan gives you 5 profiles on 1 device, with no time limit and no card. Veilus Flow, schedules, batch runs and the local API/MCP need Pro.
03How does the 7-day Pro trial work?
Request it in the app with your email. We send you a key by email; paste it into the app to unlock Pro. After 7 days you drop back to Free and keep your profiles.
04Which operating systems does it run on?
macOS and Windows. There is no Linux version.
05Where is my data stored?
Profile data is stored locally on your machine. If you turn on Veilus Sync, profiles sync to a Git repository or Google Drive you choose — use a private one. When you export a profile to a .veiluspack file, you can set a password to encrypt the file.
06Can I use my own proxies?
Yes. HTTP and SOCKS5 are supported, and each profile can have its own proxy.
07How does Veilus Flow work?
Connect an AI assistant that supports MCP, such as Claude Code or Cursor, and give it a task. It writes a Playwright script, runs it on a few profiles, reads each profile's errors and fixes them. You can also write the script yourself and add it through the local REST API. Scripts added over MCP or REST run on at most 3 profiles per run until you approve them in Veilus Flow; after that, run them as a batch or put them on a schedule. Veilus Flow is part of Pro.
08How is Veilus different from other anti-detect browsers?
Automation is built in: your AI assistant writes and fixes scripts over MCP, or you write them yourself, and Veilus runs them across profiles, with schedules, batch runs and a local REST API in the same app. You can also pay once for a lifetime license instead of a subscription.
09Can I get a refund?
Yes. Monthly payments can be refunded within 7 days, lifetime licenses within 14 days.