Skip to main content
Traversal’s AI SRE agent uses large language models (LLMs) from third-party AI providers to reason over your telemetry, code, and incident context during an investigation. By default, Traversal’s SaaS offering routes these calls through its own managed relationships with its LLM providers, under zero-data-retention agreements. Nothing you don’t already send Traversal today changes with this default — it’s covered under Traversal’s own data privacy commitments. For customers who want more direct control over that inference path, Traversal supports bring your own key (BYOK).

​
What BYOK gives you

With BYOK, LLM calls made on your behalf are authenticated with your own key or cloud account instead of Traversal’s. That’s a small configuration change with a few concrete benefits:

Inference region / geo control

Your key, your account — inference runs wherever your provider agreement places it. This matters if you’ve negotiated regional processing, or if you route calls through your own cloud account’s region for in-region processing.

Your retention terms apply

Requests are governed by the data processing agreement and retention policy you’ve already negotiated directly with the provider — zero-retention, custom log windows, whatever your contract specifies — rather than Traversal’s default terms.

Cost transparency

Usage bills directly to your provider account at your negotiated rate, visible in your own dashboard, instead of being metered through Traversal.

Simplified compliance surface

Since Traversal calls your provider directly with your credentials, you’re not adding Traversal as an additional data processor in the LLM call path for audits or vendor risk reviews — your existing provider relationship covers it.
BYOK controls the LLM inference path specifically. It’s independent of — and composable with — Traversal’s BYOC deployment option, which controls where the rest of the Traversal platform runs. You can use BYOK on Traversal’s SaaS offering (multi-tenant or single-tenant), inside a BYOC deployment, or not at all — Traversal’s managed defaults work the same either way.

​
Supported providers

Traversal supports BYOK across the LLM providers it integrates with, whether that’s a direct API key or bringing your own cloud account. See the LLM Providers section in the sidebar for the current list of supported providers and setup instructions for each.

​
Setup

BYOK is configured per provider under Company Knowledge → Integrations. See each provider’s page (in the sidebar) for exact steps, but in general:
1

Pick a provider

Choose the provider that matches your existing enterprise agreement or region requirements.
2

Connect your key or account

Enter your API key, or work with the Traversal team to connect your own cloud account, depending on the provider.
3

Traversal routes inference through your account

From that point on, LLM calls for your organization’s investigations flow through your own provider account and are subject to your agreement with them.
Need a provider that isn’t listed, or a private/self-hosted inference endpoint? Reach out to the Traversal team — the same BYOK model extends to custom gateway and private endpoint configurations.