Bring Your Own Key (BYOK)

Use your own provider keys through Concentrate

Store your provider credentials in Concentrate. Keep calling our unified API, and burn through your existing credits or committed spend.

BYOK key

Provider, masked preview, owner scope, and which requests ran on your key.

Integration

Same API

Credit spend on BYOK

None

Fallback

Automatic

New capabilities

What your team gains with Concentrate

Your keys first, Concentrate as backup

Among equal provider candidates, Concentrate tries providers you hold a BYOK key for first. If every stored key fails, the request falls back to Concentrate, then to the next provider in the chain.

Provider

OpenAI

Request tries your stored OpenAI key first.

Billing

Direct

Provider bills you. Concentrate balance is untouched.

Fallback

Concentrate

If your key fails, Concentrate is automatically tried as a fallback.

No Concentrate rate limits or credit spend

Attempts on your keys skip Concentrate rate limits and do not debit your Concentrate balance. Only your provider's own limits apply, and the provider bills you directly.

Built to be secure

Every key is encrypted with AES-256-GCM. Once you save a key you can never see it again, only a short masked preview to tell your keys apart.

Who Concentrate is designed for

Teams that already hold provider contracts and still want one gateway

BYOK keeps your existing provider billing relationships while Concentrate still handles routing, logs, spend attribution, and fallbacks.

Teams with committed provider spend

Route GPT-5.5, Claude Opus 4.8, and Gemini traffic through keys you already own, without giving up Concentrate routing and logs.

Security and procurement

Keep provider secrets out of your app repos and CI pipelines. Each key lives in one place, encrypted and out of reach, instead of copied across your stack.

Platform engineering

Add a key once in the dashboard. Every request that routes to that provider uses it automatically. No request-body or header changes.

Finance and ops

Provider bills you directly for BYOK traffic. Concentrate still records usage per key so you can see which stored credential served each request.

Bring Your Own Key (BYOK) basics

Frequently asked questions

What is Bring Your Own Key (BYOK)?

BYOK lets you store your own provider API keys in Concentrate. Requests routed to those providers run on your keys. You keep provider billing. Concentrate still provides routing, logs, and usage tracking.

Which providers support BYOK?

OpenAI, Anthropic, Azure, AWS Bedrock, Google Vertex, Alibaba, xAI, Google AI Studio, Cohere, Mistral, Cloudflare, Z.ai, MiniMax, DeepSeek, DeepInfra, and Novita. Most take a single API key. Azure, Vertex, and Bedrock need richer credentials such as a resource name, service-account JSON, or IAM access keys.

Does BYOK change how my app calls Concentrate?

No. Configure keys in the dashboard under BYOK. Apps keep calling Concentrate with a Universal API key. Routing picks your stored provider key automatically when that provider is selected.

What happens if my BYOK key fails?

Your stored keys for that provider are tried first, then Concentrate steps in as a backup, then the next provider in your fallback chain is tried. A bad BYOK key does not fail the request on its own.

How is BYOK billed and tracked?

BYOK requests are not debited from your Concentrate balance. Usage is still recorded and attributed to the stored key that served the request. Responses mark BYOK traffic with cost.byok set to true.

One API for every major LLM provider — routing, spend, logs, and controls in one place.

New York

130 E 59th St, 17th floor

New York, NY 10022

Wilmington

1201 N. Market Street, Suite 200

Wilmington, DE 19801

Offices