Security
What is logged, what is not logged, and where prompt traffic belongs.
What touches your prompt is the part you can verify.
Metadata rows are limited to generation ID, workspace, key hash, model, provider, token counts, cost, usage type, speed, finish reason, status, and region.
TrustedRouter never logs or stores prompt or output content. A workspace may explicitly send content through the attested gateway to its own configured Broadcast destination; that customer-directed export is not a TrustedRouter log.
The router can prove the hosted gateway code path and transport boundary. Provider compute policy is listed separately on provider pages.
api.trustedrouter.com
The FastAPI control plane does not register production chat, messages, responses, or embeddings routes.
Attestation failure stops the API path.
If the gateway cannot satisfy the attestation boundary, production prompt traffic should stop rather than fall back to a weaker path.
Trust page first.
The trust page publishes source commit, image reference, and image digest.
Open trust pageDemand routers you can inspect.
AI routers sit between your application and the model provider. Developers should be able to inspect how routing, billing, fallback, content handling, and provider selection work before sending production prompts.
Read the thinking behind this — “Attestation is All You Need” →
TrustedRouter can verify the hosted gateway path and reduce what the control plane can see. It cannot make every upstream model provider confidential. Provider retention and training claims remain provider specific.