Receipts
Receipts,
not vibes.
Every claim on this site has an artifact behind it, or is marked as still to come. Nothing here is claimed before it is measured. Where a receipt doesn't exist yet, this page says so — that honesty is itself part of the offer.
Published evidence
What can be audited today
The competitive scan
Before proposing the third door, we checked whether it already existed. Some thirty providers — GPU clouds, uncensored inference services, confidential-computing clouds, the labs' own private tiers — read at the pricing page and at the terms. The finding: refusal-free access exists only as shared, revocable API access; dedicated control exists only as empty iron; no provider combines dedicated single-tenant tenancy, a preloaded uncensored stack, published trust artifacts, and producer positioning. The scan is the evidence base for the founding document.
The founding document
“The Third Door — An Open Proposal to Sam Altman” states the company's position in public, including its honest limits: a small shop, building in the open, staging first, making no product claims it has not receipted. A position you can hold us to is a receipt of its own kind.
The model-license manifest
Every model in the stack is named, versioned, and pinned, with its license read and on file — because open weights are a legal artifact, not a vibe. Versions are pinned by hash; every version bump is a fresh license review before the model enters the stack. The manifest is compiled and maintained as part of the build.
Benchmark results
Every node ships with its benchmark results published, and every model in the stack is tested against the work our customers actually do before it enters. The staged pretest runs first; results will be published here as they land. Until then this line stays marked — forthcoming, not claimed.
The tenancy artifacts
What every tenancy carries
These are terms of the offer, stated in advance so a tenant can hold us to them — the trust artifacts that ship with every node.
A ledger you can read
A billing and activity ledger the tenant can read line by line. No summarized invoices that hide the meter; the record of what ran, when, and what it cost is the tenant's document, not our summary of it.
A meter you can cap
Set the ceiling before the work runs. The meter the tenant reads is the meter the tenant controls — spend is bounded by the tenant's number, not discovered on an invoice.
Keys the tenant holds
Encrypted storage whose keys belong to the tenant. Privacy that is architectural — a fact about the machine — rather than a promise in a terms document. There are no prompt logs on someone else's server, because there is no someone else's server: one customer per physical machine.
A certified wipe
When a tenancy ends, the node is wiped and the tenant receives a signed wipe receipt — the exit is a door, not a maze, and the leaving is documented like the arriving.
The floor, in plain language
Our guardrails, stated once, in public
- Nothing involving minors, ever. No exceptions, no interpretation.
- No real person's intimate likeness without documented consent.
- Election-law disclaimers ride on political advertising work, as the law requires.
- Above that floor, taste belongs to the operator. The same floor appears in the tenant terms: the floor is the law, never taste.
Still to come — marked, not hidden
The honest remainder
This page will grow the way the build does: benchmark results when the pretest produces them, the full license manifest at launch, per-tenant artifacts as the first tenancies run. If a claim anywhere on this site lacks its artifact, the correct reading is that we haven't earned it yet — and the correct move is to ask us about it: contact@inferencedevices.com.