Named device
The reference class of machine is part of the result, not a footnote.
BENCHMARKS
How we measured the numbers we publish.
Resource and latency figures are tied to a named reference device, workload, duration, instrument, and signed result.
Trust version 2026.11.3 · generated 2026-11-14T09:12:04Z
Proof
What this page is for
Resource and latency figures are tied to a named reference device, workload, duration, instrument, and signed result. A number without that apparatus is marketing.
Until a signed field-measurement artefact records a pass, published figures are labelled design targets in the same sentence.
On this page
What you get from this
Signed result
The method and the result hash are published together.
No unquantified adjectives
We do not call the client light, fast, or negligible without a figure and a method.
Collection boundary
The boundary
We observe here
Byte and packet counts, protocol, an encryption indicator, destination country, network operator, registrable domain, the app or browser that opened the connection, timestamps, and direction.
We never collect here
Communication content, URLs, paths, query strings, DNS names beyond the registrable domain, headers, cookies, tokens, files, screenshots, form data, keystrokes, usernames, email addresses, hardware serial numbers, or precise location.
Coverage is not complete. Some traffic paths are not observable from the interfaces we use, and geolocation is advisory rather than authoritative.
Availability across plans
Personal
Included
Pro
Included
Team
Included
Enterprise
Included