Every profile is its own device.
Proteus is an open-source browser built on Chromium. Each profile has its own cookies and its own device identity — screen, graphics card, fonts, time zone, fingerprints — and looks like the same device every time it starts.
What a profile controls
The values are changed inside the browser engine, where Chromium computes them. Nothing is injected into pages, so the page, its frames and its workers all agree, and the browser's functions still look like the browser's own.
Identity
User agent, platform and vendor, with client hints in script and in request headers built the way that Chrome version builds them.
Hardware
Screen and available area, processor count, device memory, the battery, and which cameras, microphones and speakers exist and what they are called.
Graphics
WebGL vendor and renderer, with that card's limits, extensions and shader precision; WebGPU adapter information.
Fingerprints
Canvas, WebGL and audio carry a small noise derived from the profile's seed: stable for a profile, different between profiles.
Fonts and voices
An allow-list of installed fonts with stand-ins for claimed ones the machine lacks, and the list of speech voices.
Place and language
Languages, time zone and the position reported to sites — optionally matched to the proxy's exit automatically.
Network
A proxy per profile, and WebRTC that never reveals the machine's own address — it shows the one you choose.
Phones
Android (Chrome) and iPhone (Safari) profiles: phone screen and page area, touch, pixel ratio and mobile layout.
Noise that survives being checked
The usual way to defeat fingerprinting is to add random noise to everything a page reads back. The usual way to catch that is simple: draw a known colour and read it. Proteus is built around not failing that test.
- Only what already differs. Noise goes on text, curves and gradients — content that varies between real devices — never on flat fills or on pixels the page wrote itself.
- The same answer twice. Reading a canvas again, reading part of it, copying it or exporting it all agree.
- No dependence on position. The same drawing moved across the canvas is the same drawing.
- Real cost. A spoofed graphics card name takes as long to ask for as a real one; sites time that.
See it for yourself
The test page runs the checks detection scripts commonly use, in your browser, and sends nothing. Try it in an ordinary browser, then in a Proteus profile, then in two.
Run the testHow it works
Two parts: a patched Chromium that takes its identity from a file, and a small manager that writes that file.
Create a profile
The manager generates a coherent device — or uses a reading taken from a real one — and stores it as a plain JSON file.
Start it
The manager launches the kernel with that profile's configuration, proxy and its own data directory.
Browse or automate
Use the window, or drive it with Puppeteer, Playwright or Selenium through the DevTools endpoint each profile exposes.
Identities from real devices
A collector page reads how a real device's browser describes itself, and Proteus makes profiles from the reading: same model of device, each with a noise seed of its own.
- Reads the browser and system version, phone model, screen, processor count, memory class, graphics card and its limits, font names from a fixed list, speech voices, which kinds of media device are listed (not their names).
- Does not read the IP address, location, language, time zone, cookies or history.
- One self-contained file. Nothing leaves the page until you press a button.
# Start the manager, then open http://127.0.0.1:5310 cd manager node src/main.ts
What it does not do
Better said here than discovered later.
- It is Chromium underneath. An iPhone profile reports Safari's identity, but a site that probes engine behaviour or looks at the TLS handshake can tell it is not WebKit. There is no Firefox kernel.
- A limit is a claim. A page that really allocates beyond a claimed graphics limit succeeds if the hardware allows it.
- Fonts of another system are stand-ins. A phone or cross-system profile claims that system's fonts and hides the machine's, but draws them with substitutes that careful measurement can tell apart.
- No protection is complete. Sites combine many signals — address reputation, behaviour, account history — that no browser controls.
Proteus is for separating identities you are entitled to have: several accounts of your own, testing, research and privacy. Not for fraud, evading a ban, or impersonating someone else.