Our browser engine

ARMANOS Browser 153.0.7978.0 is compiled from Chromium sources by us. It is not a plugin, not an extension and not a launch flag, it is the browser itself.

A page asks the browser, and the browser answers it with your profile's values rather than your computer's. The version a profile claims is the one that actually renders it and no other.

An installer with no engine in it never reaches you.

A site's script does not get there first. By the time it asks for navigator.platform, the browser is already answering with your profile's value.

All of a profile's values hold together and follow from its template, its id and its proxy exit country. So the same profile is still the same machine tomorrow and on another computer.

1. 1

   What goes into a profile's device

   Screen, GPU strings, fonts, timezone, languages, device counts and network numbers.

2. 2

   The values travel over once

   They go to the browser at launch, beside the profile's folder, its proxy and its language list.

3. 3

   A tab opened later is no different

   A page opened ten minutes on sees the same machine the first one saw.

4. 4

   The page has nothing to override

   It runs afterwards and finds not one replaced prototype.

Patches cover 39 files of the Chromium sources plus 10 new ones of our own. Every row in the table below is read by a site from your profile, not from your machine.

Two rules hold across the whole table. The same drawing reads back the same way for a profile rather than anew on every call, and numbers are rounded the way ordinary Chrome rounds them.

Not everything has moved into the browser yet. What it does not close, the app closes from the page, and that too happens before any script of the site runs.

Two layers on one value would get in each other's way: one drawing would read back two ways, and that stands out more than either layer alone. So wherever the browser takes the work, the page steps back from it.

The list below is not typed by hand, it is read off the build itself. A build that does not carry a capability will not claim it either.

• webgl-readpixels

  noise on WebGL pixel reads inside the engine

• intl

  timezone, locale, calendar and number separators

• fonts

  the profile's font list rather than the machine's

• devices

  counts of input and output devices

• voices

  speech voices filtered to the declared language

• net

  speed, latency and connection kind

• memory

  heap limit in line with the declared memory

• webgpu

  noise on image snapshots taken through WebGPU

• net-mobile-fields

  the three Android connection fields: type, downlinkMax, ontypechange

A checker does not only read values. It compares what the browser declares against what it can measure, and page level spoofing is what creates the distance between the two.

So the app ships a second engine, Built-in engine on the Engine screen, and says which is which: Chromium through Electron, milestone 130, with protection injected as JavaScript. A profile falls back to it when ARMANOS Browser cannot start.

It will not happen silently. The profile opens anyway, and you get a notification naming the profile and the reason.

Tracker blocking, link cleaning and the rest of the protections work on ARMANOS Browser too. A small extension brings them into the profile, built by the app at launch, and there is nothing for you to switch on.

A page sees no trace of that blocking and never waits on us for a request. So a hiccup in the app cannot stall the site you are on.

• Tracker blocking

  A blocklist, first party telemetry on known platforms, and tracking parameters.

• Link cleaning

  40 tracking parameters leave the link before the request leaves your machine.

• WebRTC through the proxy

  In the default WebRTC mode your real address does not leak past the proxy over UDP. Real shows it on purpose, and an extension with the privacy permission can too.

• All traffic on the proxy

  No request goes around the proxy, and an unknown proxy type gets a refusal instead of a quiet direct exit.

• Proxy passwords off the command line

  Your password never appears in the process command line.

• Automation without the tell

  The debugging port is reachable only from this machine, and a page does not see the automation bit.

A build with a failed check never reaches you. A check that could not be started counts as failed, never as skipped.

What is measured is the finished binary, the one inside the installer, compared against that same binary with no profile on it. The clean reference is not somebody else's browser but the engine itself.

Accepted with a caveat means nothing failed but something could not be checked in full, and we call such a build that out loud.

1. 1

   The profile's values really do arrive

   The engine is launched with an exit country, what a page sees is read back, and the same engine with no profile is compared against it.

2. 2

   Four profiles, not one

   A canvas defect can show on some profiles and not others, and one lucky profile would pass a broken build.

3. 3

   Our browser and stock Chrome, compared whole

   An unexplained extra property is a refusal, not a detail.

4. 4

   A declared capability is backed up

   No placeholders in the applied patch list, and no capability claimed for nothing.

Every profile opens on a start page listing the checkers this audience already uses: BrowserScan, BrowserLeaks, CreepJS, Pixelscan and an address lookup. That page lives on your own computer, so opening a profile is announced to nobody.

Inside the app the Fingerprint self-test (profile menu > Test fingerprint) reads up to 37 values from a live page and shows you whether each one matches what you set on the profile. It will refuse to score a window without protection rather than mark it red for nothing.