OpenAI compatible API. Attested gateway. Public status.

TrustedRouter And LiteLLM

Use LiteLLM when you want to run the router yourself. Use TrustedRouter when you want hosted attestation.

Verify gateway

1 URLbase_url migration

100smodels and routes

0prompt logs by default

LiteLLM for your own infraRun the router in your environment.

TrustedRouter for hosted attestationUse a managed service with a verifiable prompt path.

Apache licensedRun it yourself or build another service.

Hosted or owned

Use the shape that matches your team.

LiteLLM is a good fit when you want to own and operate the routing layer. TrustedRouter is a fit when you want a hosted router, public status, billing, BYOK, and a gateway trust record.

The TrustedRouter code is open source, so you can still run it yourself if hosted does not match your security model.

Hosted routeOpenAI SDK

base_url="https://api.trustedrouter.com/v1"
model="trustedrouter/auto"

# same client shape
# verifiable hosted path

Own infra

Own every part.

Use a router you operate directly when customization and internal control matter more than managed service speed.

Hosted

Use attested routing now.

Create a key, add credits or BYOK, and route requests through the attested gateway.

Open source

Fork the router.

The control plane and gateway are public so teams can inspect, fork, or operate their own service.

Why open source matters

Router infrastructure should be inspectable.

Developers should be able to see how model routing, fallback, billing, prompt handling, and provider selection actually work. Open source makes that possible, whether you use the hosted service or run the code yourself.