One machine.
Every account its own device.
XDLogin gives each profile one coherent hardware identity and its own proxy. Accounts stop looking like each other.
10 profiles free. No card. Every build hashed.
People who run accounts for a living.
- Agencies keeping each client in its own profiles
- Media buyers and ad agencies
- Social media managers
- Developers automating browsers
- AI agent builders
- Marketplace sellers
- Scraping and data teams
Every profile is a folder on your disk and a Chrome process of its own.
Profiles live in folders, launch in real Chrome, and carry their own proxy, cookies and fingerprint. Profile data stays on your disk unless you turn on encrypted sync. The app contacts our server to sign you in and check your plan, including how many profiles this device holds, and for sync and teams only if you use them. This is the 3.5.8 window with sample profiles.
Install. Sign in. Launch a profile.
The same three steps on every platform. Platform notes are on the download page.
Install
Run the installer, open the AppImage, drag the .dmg to Applications, or sideload the APK. If you want certainty, compare the file against its published checksum first.
Sign in
Create a free account inside the app. Your plan follows the account onto any machine; the profiles themselves stay on the device you made them on, unless you turn on encrypted sync (Pro and above). What the app does send us is listed in the privacy policy.
Launch a profile
Create a profile, paste a proxy or run direct, and click Launch. It opens as its own browser with its own fingerprint and cookies, and with a proxy, its own IP. Check it with the built-in fingerprint test.
A fingerprint that agrees with itself.
Detection looks for contradictions: a Windows user agent with Apple fonts, a phone screen with 32 cores. Every value an XDLogin profile sets comes from one of 25 real device models, so those values agree. A few signals still come from your own machine, such as the TLS handshake, WebGL limits and font measurements. They’re listed with our test results.
Your profiles are files on your disk.
No cloud VM behind each launch. No per-launch queue. No proxy traffic metered and resold. That’s why 100 profiles cost $9 here and $36–$40 elsewhere. Cloud sync exists, is end-to-end encrypted, and is off by default.
The API and MCP are on every plan. Including free.
Every profile exposes a local REST API and a Chrome DevTools endpoint. Drive it from Puppeteer or Playwright, from Selenium through ChromeDriver, or hand it to an AI agent over MCP. The free plan gets the same API and MCP server as Business. Browser profiles for AI agents →
// launch, then attach Puppeteer await fetch(`${API}/api/profiles/${id}/launch`, { method: 'POST' }); const res = await fetch(`${API}/api/profiles/${id}/connect`); const { data } = await res.json(); const browser = await puppeteer.connect({ browserWSEndpoint: data.wsEndpoint });
Pay for profiles. Nothing else.
Flat plans by profile count. The API on every plan, free included. Pay by card or crypto. Cancel any time, refund within 7 days.
Frequently asked questions
Bans, legality, the free plan, price and automation.
Will my accounts get banned?
We don’t promise they won’t. Nobody can; read the reviews of anyone who says otherwise. What we promise is that every value a profile sets comes from one real device model, that we list what it can’t change yet, that every build is published with its hash, and that when we find a leak we say so in the changelog as soon as we know. What you do with the accounts is your responsibility, and our acceptable-use policy says what we won’t support.
Is this legal?
Running multiple accounts is legal in general. Some platforms’ terms restrict it, and some uses — fraud, evading sanctions, anything the acceptable-use policy names — are illegal everywhere and we don’t support them. Read the policy before you buy.
Is the free plan really free forever?
Yes. Ten profiles, the full fingerprint engine, unmetered proxies, the local API and MCP. No card, no trial timer.
Why does it cost so much less?
Profiles run on your computer instead of a rented cloud VM, and we don’t resell proxy traffic. Remove those two costs and this is what’s left.
Can I automate it?
Yes, on every plan. A local REST API and a CDP endpoint per profile, from Node, Python or bash, or from an AI agent over MCP.
Ten profiles, ten devices, no card.
The builds aren’t code-signed, so Windows warns you once and macOS needs one command. Check the SHA-256 we publish for every build.