Blocked before the first click
A fresh headless Chrome on a datacenter IP is the easiest bot to spot. Scripts fail on CAPTCHA pages, and agents burn tokens on them.
Persistent profiles with real fingerprints and built-in proxies. Your AI agents and Playwright or Puppeteer scripts keep their cookies, fingerprint and IP between runs, so sites see a returning user instead of a new bot. Nothing to host.
const browser = await chromium.connectOverCDP( 'wss://connect.personari.dev?profile=prf_7Kq2&token=YOUR_KEY' ); const page = browser.contexts()[0].pages()[0]; await page.goto('https://app.example.com/invoices'); // still signed in
{
"mcpServers": {
"personari": {
"command": "npx",
"args": ["-y", "personari-mcp"],
"env": { "PERSONARI_KEY": "YOUR_KEY", "PERSONARI_PROFILE": "prf_7Kq2" }
}
}
}
A fresh headless Chrome on a datacenter IP is the easiest bot to spot. Scripts fail on CAPTCHA pages, and agents burn tokens on them.
Most cloud browsers start clean each time. Every run logs in again, triggers 2FA and security emails, and the account gets flagged.
Hosting Chrome means containers, memory limits, proxy rotation and stealth patches that break with every Chrome release.
Pick a country and proxy type. Personari generates a consistent fingerprint and binds it to that profile with its own storage.
Hand the WebSocket URL to Playwright, Puppeteer or any CDP client, or add the MCP server to your agent. The rest of your code stays the same.
Every session reopens the profile with the same fingerprint, cookies and IP. Log in once and every later run stays logged in.
Most cloud browsers start clean on every session. A Personari profile is a long-lived identity your scripts and agents reuse, one per user, account or task.
curl -X POST https://api.personari.dev/v1/profiles \ -H "Authorization: Bearer $PERSONARI_KEY" \ -d '{ "name": "billing-agent", "country": "DE", "proxy": "residential", "os": "windows" }' # → { "id": "prf_7Kq2", "fingerprint": "fp_a91c…4e02", # "connect": "wss://connect.personari.dev?profile=prf_7Kq2" }
Stealth plugins override properties after the page loads, and detection scripts check for exactly that. Personari sets the fingerprint inside the browser build, so every signal agrees with every other signal.
HeadlessChrome user agent and no navigator.webdriver flag.| Check | Result |
|---|---|
| Fingerprint checkers | |
| Pixelscan | Consistent |
| CreepJS | No lies detected |
| BrowserScan | No spoofing detected |
| FingerprintJS | No bot detected |
| Iphey / Whoer | Consistent |
| Bot protection | |
| Cloudflare Turnstile | Passed |
| Google reCAPTCHA | Passed |
| hCaptcha | Passed |
| DataDome / Akamai protected sites | Passed |
Detection changes every week. We track Chrome releases and anti-bot vendors full time, so your profiles stay ahead and you never have to read a changelog.
Fingerprint signals are set in the browser engine itself, not injected with JavaScript after the page loads. We maintain every patch in-house.
New Chrome stable versions reach Personari within one week, so your browser version and features never lag behind real users.
We watch how Cloudflare, DataDome, Akamai and others change their checks, and update profiles before your runs start failing.
One standard CDP endpoint per profile for scripts and agents, plus an MCP server and workflow nodes.
Connect with one line and keep your existing selectors and tests.
chromium.connectOverCDP(url)Swap launch() for connect(). No stealth plugin needed.
puppeteer.connect({ browserWSEndpoint })Plug a signed-in browser into LangChain, CrewAI, the OpenAI Agents SDK or your own agent loop through its Playwright or CDP tool.
cdp_url=wss://connect.personari.devLet Claude, Cursor or any MCP client drive a persistent profile.
personari-mcpSelenium 4, chromedp, Rod or anything else that accepts a CDP WebSocket URL works without changes.
wss://connect.personari.devRun the same profiles from no-code workflows, including n8n Cloud.
n8n-nodes-personariThe three setups people usually build before they find us.
| Personari | Self-hosted headless Chrome | Headless Chrome + stealth plugin | Desktop antidetect app + VPS | |
|---|---|---|---|---|
| Servers to run | None | Containers + memory tuning | Your own infra | Windows VPS, always on |
| Built for scripts and agents | CDP, MCP, live view hand-off | CDP only | CDP only | GUI first, API second |
| Fingerprint | Browser-level, stable per profile | Default headless | JavaScript patches | Browser-level |
| Sessions between runs | Persistent by default | Manual cookie files | Manual cookie files | Persistent |
| Proxies | Built in, bound to profile | Bring your own | Bring your own | Bring your own |
| Scale to 100 parallel runs | Change a number | Build a browser pool | Build a browser pool | Buy bigger machines |
Start free. Upgrade when your workflows need more profiles or more parallel browsers.
Use a persistent profile. Log the agent in once, and every later session reopens the same profile with the same cookies, storage, fingerprint and proxy, so the site sees a returning user instead of a new bot.
A browser that runs on someone else's servers and presents a consistent, realistic fingerprint (canvas, WebGL, fonts, timezone, IP) for each profile. Your agent or script controls it over CDP instead of you running Chrome yourself.
Most agents drive a fresh headless Chrome. It has a bot-like fingerprint, a datacenter IP and no history, so bot protection treats every run as a new suspicious visitor. A stable fingerprint, a matching residential IP and saved cookies fix most of it.
Open the session's live view and pass the check yourself, or send the link to the account owner. The profile saves the result, so the agent won't be asked again on the next run.
Stealth plugins patch a standard headless Chrome from JavaScript, and detection scripts look for those patches. Personari changes the fingerprint at the browser level and keeps it stable per profile, and you do not have to host or update anything.
Only the line that starts the browser. Replace launch() with a connect call, or pass your profile's WebSocket URL as the CDP endpoint. Everything after that works as before.
New Chrome stable versions ship to all profiles within one week of Google's release. Existing profiles keep their fingerprint and only the browser version moves forward, the same way a real user's Chrome updates.
Yes. The n8n node opens the same persistent profiles, and it works on n8n Cloud, where you can't run Puppeteer yourself.
Read the acceptable use policy.
Get an API key, create your first persistent profile and connect your code in about five minutes.