The data we expose

DoesItARM’s product is the data: one current compatibility verdict per title, with the evidence and the freshness attached. This page is the plain-language tour; the exact shape is the Verdict object.

What a verdict contains

• The answer — status (one of native / rosetta2 / translation / unsupported / unknown) and, when it runs through a layer, which layer (translationLayer).
• How sure we are — confidence, and the basis (binary inspection, automated test, crowd reports, vendor statement, curator note).
• The scope — the macosVersion and chip the answer applies to.
• The caveats — human-readable qualifiers like “no online play” or “low FPS”.
• The Rosetta clock — breaksAtRosettaEol, true when the title only survives via Rosetta 2 and will break at macOS 28.
• The freshness — lastVerified and stale.
• The receipts — signals (the contributing reports and tests) and alternatives (native equivalents when a title is unsupported).

Where it comes from

The hybrid engine blends crowdsourced reports, an automated test harness on a cloud Apple Silicon fleet (Preview), and known facts (vendor word, binary architecture, Homebrew metadata). DoesItARM tests copies it acquires cheaply and publishes only the facts — never the software.

How you can use it

Verdict facts are published under Creative Commons Attribution 4.0 (CC BY). You can reuse them — in an app, a comparison, an AI answer — with attribution to DoesItARM.

This is the give-vs-gate line: the facts are free (that’s what makes DoesItARM the citable default), and you pay only for capability the free lookup can’t provide — bulk export, the change feed, a freshness SLA, a redistribution license, or enterprise reports. See Agents & citation for the citable unit and the JSON-LD payload.