Torrix

Security and trust

Make the guard the only way in.

Torrix holds the credentials. With signed calls on Enterprise, it signs every call it forwards and your servers can refuse anything that did not come through it. Everything runs on your servers.

Read SECURITY.md

Self-hosted · Source available under FSL-1.1, Apache 2.0 after two years

Verified against

  • OpenAI Agents SDK
  • Remote OpenAI MCP
  • MCP reference server
  • Dex OIDC
  • Postgres 16
  • 420+ automated tests

Enforcement

Three layers, so the gateway is the only way in.

  • Torrix only

    Credentials

    Agents hold only Torrix credentials. The real downstream keys stay in Torrix, encrypted with AES-256-GCM. Pro and Enterprise.

  • ES256 · 60 s

    Attestation

    Every forwarded call carries a 60-second ES256 token bound to the agent, tool, arguments digest and decision, with replay protection. Enterprise.

  • Torrix only

    Network

    Helm network policies let protected servers accept traffic only from Torrix, on clusters that enforce network policies.

  • Self-hosted

    Privacy

    Self-hosted. PII masking covers proxy, SDK and OpenTelemetry traffic. Trace data stays on your servers unless you configure an external model or judge.

  • OIDC · PKCE

    Identity

    OIDC single sign-on with PKCE (Enterprise). Agent credentials are hashed, scoped and revocable. Audit log export (Enterprise).

Verify · Enterprise

Your servers can refuse anything that did not come through Torrix.

Talk to us

Security review coming up?

We will walk your team through the architecture, the threat model and a deployment in your own network.