I need to prove something about hardware I own.
Devices you already own, checked against the root of trust inside them, with a signed record for each and a written statement of what it does and does not establish.
What this costsBuilding a network for attested compute, with clear policies, signed verification records and stable pricing.
Android and AWS Nitro verified on real hardware.
TPM 2.0 appraised first-hand; GPU support in research.
Anchored — chains to a pinned rootNot enabled — proof verified, not yet accepted
You own hardware. Somebody wants proof of what it is.
An auditor, a customer, a franchisor, a contract. The phones, laptops and servers you already own produce evidence about themselves, signed by the chip inside them. We check that evidence against the manufacturer’s own root of trust and issue a signed record of what was true, and when.
We did not make the evidence and we cannot forge it. That is the whole point — and it is why every record we issue also states what the evidence does not prove.
Three reasons people are on this page.
Devices you already own, checked against the root of trust inside them, with a signed record for each and a written statement of what it does and does not establish.
What this costsCompute priced per node-hour on machines that proved themselves in hardware before they were listed. Every job returns a signed evidence bundle.
How compute worksLaptops, phones, workstations. Not passive income, and we will not describe it as such: we publish what a device actually earns before you decide.
Becoming an operatorJust looking? Start with what we cannot do. It is the shortest honest summary of this company.
Nothing on this site is for sale yet. There is no checkout and no onboarding — this page tells you what exists, and what does not.
What each hardware root proves, what it cannot, and where the boundary sits.

Inspect a signed example and understand verification boundaries.

Physical-device observations and the lessons behind our policies.

The boundary of every claim here, stated by us rather than found by you.

Requirements in. A reasoned placement out.

A fresh challenge lets the coordinator check device evidence before considering it for placement.

Customer requirements determine eligibility. When qualifying capacity is unavailable, the job waits.

A signed bundle captures the verification and placement decision, with its limitations attached.
Private workload execution and public compute rental remain in development. A placement record does not prove job completion.