Portkey Alternative — Routing Without Logging Every Prompt
A Portkey alternative for teams that can't store prompt content. Usage metering without content logs, verifiable in source.
Portkey logs every request. TrustedRouter logs none of them — and proves it.
Portkey is built around observability: it captures every request, response, and trace so you can monitor and govern AI usage. That's exactly what you want for some workloads — and exactly what you can't have for sensitive ones.
TrustedRouter takes the opposite stance. Prompt and output bodies are never persisted, the gateway is hardware-attested, and the whole thing is open source. You get routing, fallback, and usage metering without a copy of every prompt sitting in a logging backend.
{
"model_id": "anthropic/claude-sonnet-4.6",
"input_tokens": 12,
"output_tokens": 84,
"cost_microdollars": 218,
"provider": "anthropic",
"region": "us-central1"
}
# No prompt body. No response body. No content.
# Verify the schema in the open-source code.Metering without content.
Token counts, cost, latency, model, region — everything you need for billing and capacity, none of the prompt content.
By construction, not config.
The attested binary never writes request or response bodies. It isn't a toggle you can forget to set; it's a property of the code you can verify.
The gateway features you came for.
30+ providers, automatic rollover on failure, BYOK, prepaid credits — the control-plane conveniences, minus the surveillance.
Pick by what you're allowed to store.
If you need to replay and inspect every request, an observability-first gateway is the right tool. If a stored copy of a prompt is a liability — PHI, privileged material, proprietary code — you need the opposite: a path that provably keeps nothing.
Why we built around proof: “Attestation is All You Need”.