Această pagină nu este încă în limba dumneavoastră. Citiți textul în engleză.
Glossary
Virtual machine
A virtual machine is a whole computer in software, running its own system and reporting one set of device readings inside.
What it is
A guest system runs on your computer with its own kernel, its own disk and its own network stack. The wall around it is thicker than the one around a browser profile.
If your work needs that wall, use one. Nothing on this page argues against it.
A profile and a guest answer different questions. One separates work places inside a system, the other separates systems.
One guest is one set of readings
Everything inside a guest reads the same device, so a second account that must not be linked to the first needs a second guest.
That is where the price shows: a system to keep patched, memory reserved, tens of gigabytes of disk and a boot before the first click.
Two browser windows inside one guest read the same machine as well. Keeping accounts apart in there means running a separate browser for each of them.
Your machine right now
These four values are read in the browser you are reading this in. If it runs inside a virtual machine, the renderer line is usually where that shows.
A machine with a card of its own names that card here. A guest usually names a rasterizer instead, and the words in the line are the whole tell.
Dispozitivul dumneavoastră, chiar acum
- Graphics vendor
- se măsoară pe dispozitivul dumneavoastră
- Graphics renderer
- se măsoară pe dispozitivul dumneavoastră
- Cores reported
- se măsoară pe dispozitivul dumneavoastră
- Memory reported
- se măsoară pe dispozitivul dumneavoastră
Citit în browserul dumneavoastră și afișat aici. Nu se trimite nimic nicăieri.
The renderer line gives it away
A guest with no graphics card passed through draws in software, and the renderer names the software rasterizer doing the work. A page reads that line without asking permission.
A browser can be told to report a different line. The drawing itself stays with the machine underneath, because pixels follow whatever draws them.
A rented server tells the same story. Whatever the provider gave that machine is what draws its pictures.
What a profile declares instead
A profile takes its graphics pair from machines that are really sold, and the cores and memory that come with it follow that card.
So a profile does not declare a software rasterizer. What it does not do either is change what draws the picture on the machine you are sitting at.
Cores and memory come from the class of that card. A laptop chip does not arrive with a desktop core count, because the pair is what a check reads first.
A value that no machine of that kind reports is refused rather than applied. A field left alone stays as the profile generated it.
Often confused with
Each of the three separates something different, and choosing by the word alone is how people end up paying twice.
A browser profile
Separate storage, exit and readings inside one system, rather than a second system.
A device farm
Real hardware instead of software, with the same one identity per unit.
A remote desktop
Another machine shown on your screen: a place to work rather than a way to keep accounts apart.
What this does not do
- It does not hide that a machine is virtual. The line a page reads can be set, the drawing under it is still done by the guest, and our engine does not change that.
- A profile is not a virtual machine. Profiles are processes on your own kernel and share it with each other and with you.
- One guest is not many identities. Everything inside it reads one machine, whatever a browser inside it reports.
- We do not build or manage virtual machines. The app runs inside yours, and how many profiles open at once follows that guest's memory.
Check it
Each claim here is one place in the code and one stand.
- The graphics pair and the cores that follow it come from machines really sold
- packages/shared/src/index.js
- The parts of a fingerprint are judged against each other rather than one by one
- apps/desktop/test/fingerprint-consistency.js
- What a profile answers is measured in a real browser window
- apps/desktop/src/lib/fpAudit.js · apps/desktop/test/fp-audit.js
- The four values above are read in your own browser and sent nowhere
- apps/web/components/site/LiveReadout.tsx
Questions
- Can a site tell that I am in a virtual machine?
- Often it can, and the graphics line is the cheapest place to look. Working from one does not erase that line, here or in any other browser.
- Does a profile declare a software renderer?
- No. The pair comes from machines that are really sold, and the cores and memory follow the card, because a pair that never shipped is visible in one call.
- Is a virtual machine safer than a profile?
- Its wall is thicker and its cost is a machine per account. The choice is depth against number, and both answers are reasonable.
- Can I run this app inside one?
- Yes. How many profiles open at once is computed from that guest's memory, so a small guest holds few of them.
- Does a virtual machine change my exit address?
- No. Traffic leaves through whatever the host uses, unless a proxy is set for the profile inside.
See what your own browser answers
The check reads 12 values in your browser, with nothing sent anywhere.