Many accounts. No crossovers.
ARMANOS is a private browser with isolated profiles. Run dozens of work environments on one computer, each with its own identity, cookies and proxy. No mixing and no extra tracking.
Apple Silicon. A free plan forever, no card required.
- No card required
- macOS and Windows
- Free profile forever
Facts you can check
- Chromium 153
- The engine is built from source: the substitution happens inside the engine, not on top of the page.
- 2,233 automated checks
- Each one is proved: the defect is put back into the code to see the check go red.
- 25 fingerprint readings
- The app opens a test page itself and shows where the profile differs from what it claims.
- 22 languages
- The same wording in the app and on the site, not machine text in a menu.
A familiar problem
Platforms link your accounts and ban them in batches
One fingerprint, shared cookies and a single IP reveal that different profiles belong to the same person. A single ban is enough to put every linked account at risk.
How it works
What a digital fingerprint is
Sites recognize you by more than your login. The browser hands over dozens of parameters: version, language, screen resolution, core count, fonts, graphics. Together they form a fingerprint that identifies you even without cookies.
ARMANOS gives each profile its own stable set of parameters and isolates its storage. Profiles look like different users and do not reveal any link between them.
Honest about the limits: the ARMANOS Browser substitutes the fingerprint inside the engine itself, before the first script on the page runs, and it ships with the app on both macOS and Windows. The built-in engine stays as a fallback and substitutes at the script level. Neither makes you anonymous: they stop sites from linking your profiles to each other.
- Platform
- macOS
- User-Agent
- Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/
- Language
- en-US, en
- Screen
- 1680 × 1050
- CPU cores
- 10
- Memory
- 8 GB
- WebGL
- ANGLE (Apple, ANGLE Metal Renderer: Apple M1, Unspecified Version)
Our own browser
The fingerprint is substituted inside the engine, not by a script
ARMANOS Browser is our own build of Chromium. The device a site sees is assembled in C++ before the page is handed anything, so the very first script a site runs already reads the substituted values. A script can only correct what the browser has already created, and the gap between the two is what fingerprinting looks for.
Before the first script
The seed reaches the engine on the command line, so navigator, screen, WebGL, canvas, audio, fonts, timezone and client hints are already the profile's own when the page starts.
Ten surfaces, one device
Every value comes from the same seed, so they agree with each other. A mismatch between the claimed browser version and how the engine actually behaves is the cheapest thing to detect.
Protection travels with it
Tracker blocking, link cleaning, telemetry suppression, RPA Plus and the Synchronizer all work on this engine. Choosing it costs you nothing.
Every launch
A profile opens on its own summary
Before you go anywhere, you see the identity this profile is wearing: the exit IP with its country and city, the proxy, the engine and its version, and the full fingerprint. Links to BrowserScan, BrowserLeaks, CreepJS and Pixelscan are one click away.
The IP a site will actually see
Looked up through the profile's own proxy, with country and city, so a misrouted profile is obvious before you sign in anywhere.
The whole fingerprint, up front
User agent, platform, screen, languages, timezone, cores, memory, WebGL vendor and renderer, font count.
Generated on your computer
The page is built and served by ARMANOS on your own machine. Nothing about the profile leaves it. Competing products serve this page from their servers, which tells them about every launch you make.
Running many accounts
The work that comes with fifty accounts, not one
None of this matters with a single profile and all of it matters with fifty. Each one removes an afternoon of repetition rather than adding a checkbox.
A proxy library, not fifty copies
Paste the seller's list once, in whatever shape it arrived: host:port, host:port:user:pass, user:pass@host, an explicit socks5:// scheme, an optional label. Profiles link to an entry, so rotating a password touches one row instead of fifty. Lines that cannot be read are named rather than guessed at, because a mis-parsed proxy is a browser going out on your real address.
Import your accounts from a spreadsheet
They already live in one. ARMANOS reads it with Excel's byte order mark, its semicolons and its quoted fields intact, matches the column names in your own language, and shows which column became which field before it creates anything. Groups and proxies from the file join the library on the way in.
One-time codes where the account is
Paste the key the site gave you, or the whole otpauth:// line behind the QR code. The profile produces its own six-digit code with the seconds remaining, so twenty accounts with two-factor no longer mean reaching for a phone twenty times.
Fingerprint values you can choose
Screen, cores, memory, pixel ratio, time zone, languages and the GPU strings can be set per profile, picked from values a real machine of that platform reports. Deliberately not a text box: seven CPU cores, or an NVIDIA card on a Mac, is a stronger signal than the generated value ever was.
A profile that has been used
A brand new profile with an empty cookie jar and no history is itself a signal. The cookie robot browses ordinary public sites inside the profile first, with a different selection and order for every profile, so a batch of ten does not produce ten identical histories.
Groups that mean one thing
A group is a real record with a name and a colour, chosen when the profile is created and shown everywhere the profile appears. Labels typed under the old behaviour are converted on first launch, matched without regard to case, so nothing splits into two groups that read the same.
Scenarios
Built for your task, not one button for everything
When you create a profile you choose a scenario. It configures protection, tracker lists and safe limits for a specific type of work.
Work / LinkedIn
Recruiting, outreach, sales
Suppress LinkedIn tracking, clean links, safe action limits, session isolation.
Works in the current version.
Privacy
Everyday browsing without tracking
Tracker blocking, tracking-parameter cleaning, zero telemetry, isolation.
Works in the current version.
E-commerce
Sellers and store operators
A separate profile per marketplace and store account, isolated sessions, proxy and payment identity.
Works in the current version.
Social media
SMM, agencies, creators
Run many social accounts in sealed profiles, each isolated so platforms do not link them.
Works in the current version.
Ad accounts
Media buyers
Isolate each ad account (fingerprint, proxy, payment) so a ban on one does not cascade to the rest.
Works in the current version.
Freelance
Freelancers, agencies
Keep separate freelance profiles per platform or region, each in its own isolated session.
Works in the current version.
Features
Everything for clean multi-account work
Isolated profiles
Each profile is a separate environment with its own cookies, storage and cache. Accounts never cross over, even when open at the same time.
Fingerprint setup
Every profile gets its own set of parameters: User-Agent, language, resolution, cores, memory. The values are stable and do not jump between sessions.
Proxy per profile
Attach a separate HTTP or SOCKS5 proxy to each profile. A profile's traffic follows its own route and does not mix with the others.
Link and tracker cleaning
Tracking parameters are stripped from addresses on every navigation, and known trackers are blocked by lists. Less tracking, a cleaner session.
Safe action limits
Work scenarios include soft daily limits and warnings so that activity looks natural and accounts last longer.
Account sync
Profiles and settings are tied to your ARMANOS account. The license and quotas are checked on the server, and work continues offline within a grace window.
Your session on two computers
Point ARMANOS at a folder your own cloud already syncs. When a profile closes its session goes there encrypted, and on the second computer it arrives before the profile opens. An open profile is never touched, and if the session changed on both machines nothing is overwritten: you are asked which one to keep.
One profile, one place
When a teammate has a profile open, the same profile refuses to open elsewhere: otherwise the site sees two sessions of one account from two places, and that is what accounts get blocked for. Taking it over is possible, but only on purpose.
Runs on a schedule
A scenario can run every day, on chosen days, or every few hours, across the profiles you pick. Runs missed while the computer was off are not made up in a burst: a burst is exactly what sites read as a robot. The schedule runs while ARMANOS is open on your computer: it is the program that opens the profiles, not a server.
Extensions in two clicks
Install an extension from the catalogue straight into the program: no downloading files by hand, no putting them into folders. Only third-generation extensions are accepted, because Chromium no longer runs the older ones.
Privacy by default
Session isolation, tracker blocking and link cleaning work out of the box in every profile.
Transparent limits
We are honest about what already works and what is planned. No promises of absolute anonymity.
Grows with you
Start with a free profile and expand your quota as the number of accounts and your team grow.
The product is young and evolving in the open. Join at an early stage.
Trust and security
Built to keep your work separated
Isolation is the whole point. Each profile keeps its own cookies, storage and cache, so one account never sees another. We are also clear about what protection is and is not doing today.
Substitution happens inside the engine, before the first script on the page; the built-in engine remains a fallback and substitutes at the script level. We do not promise absolute anonymity, and we do not claim to hide your IP address.
Isolated sessions
Every profile has its own cookies, storage and cache. Sessions never share data, even open side by side.
No hidden telemetry
Privacy scenarios run with tracker blocking and tracking-parameter cleaning. We do not add tracking of our own.
Your license, your account
Entitlements are checked against your account. Work continues offline within a grace window.
Open about limits
We say what works now and what is planned for the dedicated engine. No absolute-anonymity promises.
Questions
Frequently asked questions
Set up your first profile in a minute
A free plan forever: 1 profile, basic protection, one scenario. No card required.