The short version of how Umbra tries to make private inference verifiable.
The console stays operational. This page is the opt-in explainer: what gets verified, where the hard proof lives, and which pieces are still alpha.
Apple provider attestation
Secure Enclave identity, Managed Device Attestation, signed freshness, and prompt-key binding at provider registration.
Threat model
What Umbra is designed to protect, what remains operator-trusted, and what is explicitly out of scope during alpha.
Network stats
Real current model/provider/request counts from the coordinator. No fabricated supply or traffic.
Request path at a glance
The API request reaches the coordinator through the OpenAI/Anthropic-compatible surface.
The confidential coordinator path uses the SEV-SNP verifier.
Mac trust is established on the WebSocket register frame with MDA material and freshness.
Server-signed response receipts are not live yet; the console labels this honestly.