ORGN Scanner
Public attestation and audit explorer for ORGN Gateway inference receipts and confidential compute sandboxes.
ORGN Scanner is not Studio Code Security (Shannon). Scanner audits Gateway inference attestation and confidential compute sandboxes — it does not scan your repository for CWE vulnerabilities. For code security assessments, see Code Security.
ORGN Scanner is the public attestation and audit explorer for the ORGN stack. It answers:
"Was this inference request executed in a verified Trust Domain?"
Scanner surfaces request metadata and cryptographic evidence from Gateway spend logs and the attestation pipeline. It never displays prompt contents or model outputs.
| Environment | URL |
|---|---|
| Production | scanner.orgn.com |
| Development | dev.scanner.orgn.com |
Scanner is public — no sign-in is required to browse the Explorer, Messages feed, request details, or sandbox attestation. Optional id-orgn SSO unlocks scoped filters (for example, "my requests only") but is not a prerequisite for verification.
Scanner vs Gateway console vs Studio
ORGN splits observability and administration across three surfaces:
| Surface | URL | Purpose |
|---|---|---|
| Scanner | scanner.orgn.com | Attestation audit — inference receipts, sandbox TDX evidence |
| Gateway console | gateway.orgn.com | API keys, model catalog, playground, team admin |
| Gateway API | api.gateway.orgn.com/v1 | Production inference |
Attestation verification lives in Scanner, not the Gateway console. The console helps you configure access and send requests; Scanner lets anyone independently inspect that TEE inference ran inside genuine hardware.
What Scanner covers
Scanner monitors two related but distinct attestation systems:
- Inference attestation receipts — per-request cryptographic proof that a TEE model call (
near_*,phala_*) executed inside a verified environment. Inspect at/request/:requestId. - Sandbox TDX attestation — environment-level proof that a confidential compute sandbox (provisioned via Daytona) is running on genuine Intel TDX hardware. Inspect at
/sandboxesand/sandboxes/:sandboxId.
ZDR models routed through Vercel (vercel_*) appear in Scanner for observability but do not produce hardware attestation receipts.
Navigation map
| Section | URL | What you get |
|---|---|---|
| Explorer | / (homepage) | Visual grid of recent inference activity, aggregate stats |
| Messages | /messages | Searchable, filterable list of all inference requests |
| Request detail | /request/:requestId | Full metadata + attestation receipt for one request |
| Sandboxes | /sandboxes | Running TDX sandboxes and environment attestation |
| Models | /models | Per-model usage stats and recent request history |
There is no /explorer route — the Explorer is the homepage at /.
Data boundaries
Scanner is designed for audit and compliance workflows:
- Shown: request IDs, model IDs, token counts, latency, cost, provider, application tag, attestation status, signing addresses, Intel/NVIDIA evidence artifacts
- Never shown: prompts, completions, API keys, or other plaintext inference content
This boundary is intentional. Cryptographic attestation proves where and how inference ran — not what was inferred.
Getting started
New to Scanner? Start with the Scanner Quickstart — open the Explorer, find a TEE request in Messages, and inspect its attestation receipt in under five minutes.
Documentation
- Explorer — homepage grid, stats, and live activity view
- Messages — searchable request feed with filters
- Request details — fields on the
/request/:requestIdpage - Verify a request — independent cryptographic verification
- Attestation reference — inference receipts vs sandbox TDX
- Sandboxes — confidential compute environment attestation
Related
- Gateway quickstart — send a TEE request that produces an attestation receipt
- Platform trust model — TEE vs ZDR and the verifiability frame
- Verifiable privacy — how attestation works end to end