One browser identity per account
An account that logs in from a new machine every time stands out, and so do two accounts that share one. Clearcote gives each account its own seed, so it comes back as the same device every session while the next account looks like a different machine.
Seeded identities are in every tier. Running several at once needs Pro or the open build.
A seed and a profile directory per account
import { launchPersistentContext } from "clearcote";
// one seed and one user-data directory per account
const ctx = await launchPersistentContext("./profiles/account-42", {
fingerprint: "account-42",
lightStealth: true,
proxy: { server: "http://gateway:8080", username: "u", password: "p" },
geoip: true,
});Highlights
Same seed, same device
Reuse a seed and the persona comes back identical: same GPU, screen, hardware tier and fonts. There's nothing to store; the seed is the identity.
New seed, different machine
Canvas and WebGL readbacks differ per seed and per site, so two accounts don't share a rendering fingerprint.
State that persists
A persistent context keeps cookies, localStorage, IndexedDB and TLS session continuity between runs, the way a real browser profile does.
A proxy per identity
Pair each identity with its own exit and geoip, so its timezone and language follow that IP every time.
Saved profiles in code
Profile stores the seed, proxy and launch options as JSON under ~/.clearcote/profiles, so a script launches an account by name.
A desktop app for hands-on work
The Profile Manager creates, tags and launches profiles as normal browser windows, each with its own proxy and storage.
What makes an identity
Two things make an identity: what the browser reports and what it remembers. The seed covers the first, deterministically. A user-data directory, or a hosted profile, covers the second: cookies, site storage and everything else a returning visitor carries.
Know what separates identities and what doesn't. Canvas and WebGL separate accounts. Rendered audio and client rects don't, because they come from the machine underneath and are the same for every identity on it, exactly as they would be for two people on identical hardware. If a site correlates on those, the answer is separate machines, not a different switch.
An imported device profile changes the values a page reads, not how pixels are rendered, so two accounts on two profiles on one machine still draw the same canvas. For render separation, use a per-account seed and no profile, and don't combine a seed with a profile.
Where to keep identities
| Tool | What it stores | Best for |
|---|---|---|
| SDK persistent context | A user-data directory per account | Scripts on your own machines |
SDK Profile | Seed, proxy and launch options as JSON | Launching accounts by name from code |
| Profile Manager | A data directory per profile, plus proxy, tags and notes | Driving identities by hand in a window |
| Hosted profiles | Cookies, localStorage and IndexedDB, encrypted | Cloud sessions that start signed in |
What people use it for
Agencies
Keep each client's logins on its own identity, so one client's sessions never mix with another's.
Storefront operations
Run separate stores or regions without their sessions bleeding into each other.
QA with many test users
Hold dozens of signed-in test accounts, each on a stable device.
Longitudinal research
Revisit the same pages as the same device over weeks and measure what changes.
Clearcote is built for privacy, testing, research and lawful automation. You're responsible for how you use it and for following the terms of the sites you visit.
Which plan includes it
Seeded identities and persistent contexts are in every tier. Free with GitHub runs one browser at a time, so several identities at once on the latest build need Pro.
Compare plansFAQ
How do I keep accounts from being linked?
Give each one its own seed, its own persistent profile directory and its own proxy with geoip on. Don't share cookies or storage between them, and don't rotate an account's seed.
Should I change the fingerprint every session?
No. A logged-in account that arrives on a new device every visit is a louder signal than any value you'd be rotating. Keep one seed for the life of the account.
What's the difference between a seed and a device profile?
A seed derives a whole synthetic persona and the per-site canvas and WebGL noise. A device profile substitutes the exact values a real Chrome reported, but rendering still comes from your machine. Use one or the other: passing a seed with a profile turns on the noise layer without adding anything the profile doesn't already supply.
Can I manage profiles without writing code?
Yes. The Profile Manager is a desktop app that creates, organises and launches profiles as normal browser windows, with a proxy and persistent storage for each.
Is running multiple accounts allowed?
That depends on each site's terms and on the law where you are, not on the browser. Clearcote is built for privacy, testing, research and lawful automation, and you're responsible for how you use it.
Go deeper in the docs
Related features
Canvas, WebGL, WebGPU, audio, fonts, screen, hardware and locale set in the C++ engine from one seed, so every surface agrees with every other.
Set a proxy with geoip on and the timezone, languages and WebRTC follow the exit IP. SOCKS5 with a username and password works directly.
Start a Clearcote browser in the cloud with one API call and connect Playwright or Puppeteer over CDP. Residential IP included, billed per GB of traffic.
One option turns Playwright's clicks, typing, drags and scrolls into trusted native input on curved paths, with human timing.
Related reading
Try Clearcote
Open source, a drop-in for Playwright & Puppeteer, and coherent down to the TLS handshake.
Free for one browser with GitHub. No card.