pragma.vision Your technology observatory

Verification register Security & Identity

Readiness verdict

Tinfoil Private Inference

A dated reading of what is claimed, reported, and independently verified in the current evidence.

As of
2026-06-28
Revision
1
Method
v1.0.0

Current reading

The readiness gap, in one scan

AI-assisted assembly · derived results

Claimed
75

Public ambition and stated capability

Reported
68

Observed practitioner reporting

Verified
61

Independently supported evidence

Gap
+14

Claimed minus verified

Evidence strength Growing

Decision

What the current evidence supports

Human editorial judgment · 2026-06-28

Proceed with caution

Why
Strong cryptographic-verification story and a genuine differentiator (multi-GPU CC, open-source verifier, Red Hat OSS partnership) fit pv's privacy posture, but it is a startup with no published independent audit of its own stack and unquantified overhead on its own site — verify the attestation chain and cost ourselves before relying on it.
Next
Run Tinfoil's client-side attestation verifier against a live enclave for a target model, independently confirm the Sigstore transparency-log match, and benchmark token latency/throughput vs a non-confidential baseline on our actual prompt sizes (small + large batch); test specifically for attestation freshness/nonce and patch-level cert validation per the Trail of Bits findings.

Constraints

Blockers

No named blocker is present in the current public projection.

Evidence summary

Derived counts

AI-assisted assembly

Total
7
Tier 1
0
Tier 2
3
Tier 3
4
Supports
3
Contradicts
2
Context
2
Latest observed
2026-04-07

Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.

Publication record

Revisions

Initial public reading

This is the initial public reading. No earlier readiness change is recorded.

Your opinion

Tell us anything.

What works, what doesn't, what's missing — especially about our watches, lenses, and the register itself. Anonymous is fine; leave an email if you'd like a reply.