Every account in its own browser.
All of them on your PC.
Ward runs many browser profiles on one PC. Each gets its own browser directory, its own proxy and its own coherent device identity - created, launched and stored on your own machine.
Where it stands onWindowsmacOSLinux
For agencies, sellers, QA and research teamsOn your PC, not a rented cloud browser
Free account, and your profiles stay on your PCWindows 10 or newer, 64-bitFree tier, and nothing to buy today
Folders
Tags
| Profile | Proxy | Identity | Browser | |
|---|---|---|---|---|
| Storefront · US EastClient work | us-east.relaySOCKS5 | Windows 11 · 1920×1080 | Chrome | Running |
| Storefront · UKClient work | uk-lon.relaySOCKS5 | Windows 11 · 2560×1440 | Brave | Running |
| Marketplace seller 04Marketplaces | de-fra.relayHTTPS | Windows 10 · 1536×864 | Firefox | Idle |
| Ads review · sandboxResearch | DirectNo proxy | Windows 11 · 1920×1200 | Edge | Idle |
| Support desk · APACClient work | sg-sin.relayHTTP | Windows 11 · 1920×1080 | Chromium | Running |
5
browsers it will launch
Chrome, Edge, Brave, Chromium, Firefox
14
surfaces you set one at a time
Masked, real, perturbed, or typed
5
proxy protocols, one pasted string
HTTP, HTTPS, SOCKS4, SOCKS4a, SOCKS5
0
credentials stored in the cloud
Sharing uploads a description, never a password
What it does
One machine, many identities that stay apart
Six things the software does on your own hardware, with nothing in between.
Real isolation, not tabs
Every profile is its own browser profile directory on your disk, with its own cookies, local storage, IndexedDB, service workers, cache and extensions. Nothing a site stores in one profile can be read from another. One thing that directory does not separate is Chromium’s network state, which is keyed by site rather than by profile - no flag splits it, and you should hear that from us rather than find it out later.
What the profile directory does not separateA proxy per profile
Paste the string your provider gave you, in whatever shape they wrote it: a scheme URL, host:port:user:pass, the inverted form some providers sell, or any of those separated by commas, semicolons, spaces or tabs. Ward speaks HTTP, HTTPS, SOCKS4, SOCKS4a and SOCKS5, and tells you which reading it took when a string is genuinely ambiguous.
An identity set surface by surface
User agent, screen, timezone, locale, fonts, WebGL and ten more are generated as one coherent set that matches a real device class. Then you decide, per surface, whether it is masked, left real, perturbed, or a value you typed.
Folders, tags and notes
Five profiles fit in your head. Two hundred do not. Ward gives them nested folders, tags you define, a notes field per profile, and search and filtering over all of it, so the list stays something you work rather than something you scroll.
Five browsers, one launcher
Chrome, Edge, Brave, Chromium and Firefox, whichever you already have. Ward will also fetch portable builds - Camoufox, Ungoogled Chromium, Brave - from inside the app, against a pinned checksum, so you are not trusting a download page.
Warm-up on a schedule
A profile with no history is its own signal. Ward can drive a profile through ordinary browsing on a schedule you set - scrolling, clicking, collecting cookies - with advertisements and signed-in accounts kept out of the site catalogue by design.
The proxy, done properly
Your provider’s password never reaches the browser
Chrome cannot authenticate to a SOCKS5 proxy at all - a long-standing Chromium limitation with no fix on the way. The usual workaround is a proxy extension, which is worse than the problem it solves: an installed extension is itself a distinguishing signal, and its traffic is observable.
Ward starts a small forwarding relay on 127.0.0.1 for each running profile instead. The browser talks to that with no credentials at all; the relay talks upstream and supplies them. WebRTC is pinned so a peer connection cannot hand out your real address behind the proxy’s back - non-proxied UDP disabled on Chromium, and the equivalent host-candidate restrictions written into the generated Firefox preferences.
The browser
--proxy-server=
127.0.0.1:54118
no credentials
Ward’s relay
one per running
profile
holds the password
Your provider
your endpoint,
your credentials
probed first
The username and password never reach the browser and never appear in a command line.
- WebRTCProxy candidates onlyMasked
- TimezoneAmerica/New_YorkMasked
- Geolocation accessPrompt suppressedMasked
- Geolocation data40.71, −74.01Custom
- LanguagesThis machine’sReal
- Screen1920×1080 · dpr 1Masked
- Fonts112 of the catalogueMasked
- Media devices1 camera, 2 microphonesMasked
- NavigatorThis machine’sReal
- WebGL metadataIntel · UHD 770Masked
- WebGL graphicsSeeded per profileNoise
- CanvasSeeded per profileNoise
- Audio contextSeeded per profileNoise
- Port scan protection127.0.0.1 probes refusedMasked
The identity, per surface
Fourteen decisions, not one switch
Most products give you a generated device and a toggle. Ward generates the device as one coherent set - a user agent that agrees with the platform, a timezone taken from the proxy’s exit address so it cannot contradict the IP - and then hands you each surface separately.
Masked reports the profile’s value. Real reports this machine’s. Noise perturbs a measurement - a canvas render, an audio buffer, a WebGL image - so repeated reads inside one profile agree and reads across profiles do not. Custom is a value you typed.
And real means real: a surface set to real produces no command and no script block at all, rather than an override that sets a value to what it already was. An override like that is still an override, and it is still findable.
What each surface actually doesFour decisions the others made differently
Where Ward is not like the rest of the category
Not a feature-count comparison. These are four places where the obvious implementation is the one that hurts you later, and Ward took the other one.
Signing in uploads nothing
A free account gets you in; it does not move your work. Every profile, folder, proxy and device identity lives in a database on your PC, and there is no server here that could hold one. No licence key, no activation call, no card.
It refuses rather than leaks
Ward probes the proxy exit before it starts the browser. If the probe does not answer, the launch is refused. The alternative - a window that quietly falls back to your own address while the row still says São Paulo - is invisible from inside the application, and it is the worst thing a product like this can do to you.
It never deletes a profile directory
That directory is the profile: the cookies, the logged-in sessions, the trusted-device tokens. Stop closes a browser and touches nothing on disk, and a test asserts it after a clean stop and after a failed launch. There is no undo for getting this wrong, so there is no code path that can.
The phone is on your desk, not on a meter
Mobile profiles are Android emulators from your own SDK, running on your own machine: free, unmetered, and limited only by the laptop. Where something genuinely needs somebody else’s hardware - a real baseband, a carrier IP, hardware-attested integrity - the screen says so instead of implying otherwise.
The claim we will not make
Ward is not undetectable, and neither is anything else you launch in a stock browser
A browser that has not been patched at the source level cannot be made genuinely undetectable from JavaScript. That is not a limitation of our implementation; it is a property of how the checks work. Overrides applied from script are visible through property-descriptor and prototype inspection, and the vendors whose products do defeat those checks do it by shipping a forked browser binary - Multilogin has Mimic and Stealthfox, GoLogin has Orbita, AdsPower has SunBrowser.
Ward launches the browser you already have. So it gets to make a smaller claim, and it gets to keep it.
Sentences you will not find here
- Undetectable
- 100% anonymous
- Bypasses any anti-fraud system
- You will never get banned
- Your profiles cannot be linked
What Ward will stand behind
- Each profile is internally consistent
- Each profile is plausible for a real device class
- Each profile is different from your others
- A surface left real sends no override at all
- A profile that cannot reach its proxy does not open
A vendor who overstates the one thing you can check is a vendor whose other claims you now have to check yourself.
That is the whole argument. The value of a product holding your logged-in sessions is not in what its landing page promises; it is in whether the sentence beside a control is true when you go and test it. Ward writes the ceiling down, in the application and here, and the documentation shows you how to measure it for yourself rather than asking you to take any of this on trust.
Who it is for
People who legitimately hold more accounts than one browser can carry
Agencies holding client logins
One folder per client, one profile per login, and no chance of a session from one account turning up in another one’s tab.
Operators running several storefronts
Separate shops, separate support desks, separate marketplaces - each with its own residential exit, its own device, and a browser that was never signed into any of the others.
QA and web teams
Check a site the way it looks from eleven countries, on eleven device classes, without eleven laptops. Two profiles differing in exactly one surface is a controlled experiment you can actually run.
Researchers and analysts
Sessions that do not contaminate each other, and a per-surface record of what each one reported - so a result you cannot explain has somewhere to be looked up.
One thing Ward is not, and cannot be: a ruling on what any platform allows. It keeps sessions apart on your own machine and it reports what it did. Whether a given site permits you to hold several accounts is between you and their terms, and no software - this one included - can promise you an outcome on somebody else’s service.
Install it and make the first profile in about two minutes
One file, no licence key to paste. The download page opens with all three operating systems, each with its size and its SHA-256 beside the button, and what to do about the warning an unsigned build produces on Windows.
The free tier is the working product. Paid tiers are on the pricing page and cannot be bought yet - there is no checkout to walk into.