Cloud antidetect browser API

Cloud browsers that stay signed in. For agents and scripts.

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
  • Playwright, Puppeteer, MCP, any CDP client
  • Live view for 2FA hand-off
  • Free tier, no card
Why browser automation fails

Your code works. Your browser looks like a bot.

403 · "Verify you are human"

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.

Redirect → /login · "New device detected"

Logged out every session

Most cloud browsers start clean each time. Every run logs in again, triggers 2FA and security emails, and the account gets flagged.

OOM killed · chrome exited with code 137

Running browsers yourself doesn't scale

Hosting Chrome means containers, memory limits, proxy rotation and stealth patches that break with every Chrome release.

How it works

From API key to a signed-in browser in three steps

  1. Create a profile

    Pick a country and proxy type. Personari generates a consistent fingerprint and binds it to that profile with its own storage.

  2. Connect over CDP

    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.

  3. Run it again tomorrow

    Every session reopens the profile with the same fingerprint, cookies and IP. Log in once and every later run stays logged in.

Persistent browser profiles

Stay logged in across runs

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.

  • Storage that survives. Cookies, localStorage and IndexedDB are saved when the session closes and restored on the next connect.
  • Fingerprint that doesn't drift. Canvas, WebGL, fonts, screen and audio stay identical for the life of the profile.
  • Proxy bound to the profile. Sticky residential or mobile IP in the same country as the profile's timezone and locale.
  • Human hand-off when a run needs it. Share a live view link so a person can pass 2FA once, then the script or agent continues.
create-profile.sh
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" }
Antidetect

Fingerprints changed in the browser, not patched in JavaScript

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.

  • Coherent profiles. OS, GPU, fonts, timezone, language and IP all match.
  • Real headful browsers. No HeadlessChrome user agent and no navigator.webdriver flag.
  • Re-tested every release against public fingerprint checkers before it ships.
CheckResult
Fingerprint checkers
PixelscanConsistent
CreepJSNo lies detected
BrowserScanNo spoofing detected
FingerprintJSNo bot detected
Iphey / WhoerConsistent
Bot protection
Cloudflare TurnstilePassed
Google reCAPTCHAPassed
hCaptchaPassed
DataDome / Akamai protected sitesPassed
Tested by the Personari team, November 2026. Results vary by site, proxy and traffic pattern.
Fingerprint research

Browser fingerprinting is all we work on

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.

Our own Chromium build

Fingerprint signals are set in the browser engine itself, not injected with JavaScript after the page loads. We maintain every patch in-house.

Current with every Chrome release

New Chrome stable versions reach Personari within one week, so your browser version and features never lag behind real users.

Ahead of detection updates

We watch how Cloudflare, DataDome, Akamai and others change their checks, and update profiles before your runs start failing.

up to date Engine: Chromium [version] Last fingerprint update: [date] Read the changelog →
Integrations

Works with the tools you already use

One standard CDP endpoint per profile for scripts and agents, plus an MCP server and workflow nodes.

Your script or agent"Export this month's invoices"
PersonariOpen profile · billing-agent
WebsiteAlready signed in
ResultInvoices returned to your code

Playwright

Connect with one line and keep your existing selectors and tests.

chromium.connectOverCDP(url)

Puppeteer

Swap launch() for connect(). No stealth plugin needed.

puppeteer.connect({ browserWSEndpoint })

Agent frameworks

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.dev

MCP

Let Claude, Cursor or any MCP client drive a persistent profile.

personari-mcp

Any CDP client

Selenium 4, chromedp, Rod or anything else that accepts a CDP WebSocket URL works without changes.

wss://connect.personari.dev

n8n, Make, HTTP

Run the same profiles from no-code workflows, including n8n Cloud.

n8n-nodes-personari
Compare

What it replaces

The three setups people usually build before they find us.

PersonariSelf-hosted headless ChromeHeadless Chrome + stealth pluginDesktop antidetect app + VPS
Servers to runNoneContainers + memory tuningYour own infraWindows VPS, always on
Built for scripts and agentsCDP, MCP, live view hand-offCDP onlyCDP onlyGUI first, API second
FingerprintBrowser-level, stable per profileDefault headlessJavaScript patchesBrowser-level
Sessions between runsPersistent by defaultManual cookie filesManual cookie filesPersistent
ProxiesBuilt in, bound to profileBring your ownBring your ownBring your own
Scale to 100 parallel runsChange a numberBuild a browser poolBuild a browser poolBuy bigger machines
Pricing

Pay for profiles and browser hours

Start free. Upgrade when your workflows need more profiles or more parallel browsers.

Free

$0 / month
  • 3 persistent profiles
  • 5 browser hours
  • 1 concurrent browser
  • n8n node and CDP access
Get a free API key

Pro

$49 / month
  • 50 persistent profiles
  • 100 browser hours
  • 10 concurrent browsers
  • Residential proxies included
Start Pro trial

Scale

Custom
  • Unlimited profiles
  • Volume browser hours
  • 100+ concurrent browsers
  • Dedicated IP pools and SLA
Talk to us
FAQ

Common questions

How do I keep an AI agent logged in across runs?

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.

What is a cloud antidetect browser?

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.

Why do AI browser agents get blocked?

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.

What happens when the agent hits 2FA?

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.

Is this better than puppeteer-extra-plugin-stealth?

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.

Do I need to change my Playwright, Puppeteer or agent code?

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.

How quickly do you update after a new Chrome release?

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.

Can I use it from n8n?

Yes. The n8n node opens the same persistent profiles, and it works on n8n Cloud, where you can't run Puppeteer yourself.

Built for

Automations on accounts and data you're allowed to use

  • AI agents working inside your own SaaS accounts
  • Price, stock and listing monitoring
  • QA and end-to-end tests from real locations
  • Public web data collection for research and analytics
Not for

We close accounts that do this

  • Fraud, payment testing or account takeover
  • Creating fake accounts or evading bans
  • Spam, fake reviews or vote manipulation

Read the acceptable use policy.

Give your scripts and agents a browser that stays signed in.

Get an API key, create your first persistent profile and connect your code in about five minutes.