BYOK: Bring Your Own Key
BYOK (Bring Your Own Key) means a tenant brings the upstream keys it obtained from the official platforms of OpenAI, Anthropic, Google, DeepSeek and other providers. XSI Control gives every tenant its own key pool, routing configuration, pricing and account tree. The tenant keeps ownership of its upstream keys and its model bills; XSI Control encrypts the keys, routes requests and governs access.
Two kinds of credentials
| Credential | Source | Purpose |
|---|---|---|
| Upstream key (provider key) | Obtained by the tenant from the provider's official platform | Stored encrypted in the tenant's key pool and used only to forward requests from the tenant's accounts |
XSI API key (starts with sk-Xvs) | Issued by XSI Control for each account | The caller's identity; carries quotas, allowlists, rate limits and usage records |
Applications hold only an XSI API key and never see an upstream key. When a member leaves or an application is retired, disable its XSI API key; the upstream keys do not need rotating.
Why BYOK
- You keep ownership: upstream keys are issued, rotated and revoked on the provider's platform, and can be replaced or removed in the admin console at any time.
- Direct billing: providers bill the tenant directly for model usage, and the original bills can be checked in the provider's dashboard. See Pricing for XSI Control plans.
- One entry point: keys from many providers come together behind one endpoint, grouped by level, with sticky sessions, automatic retries and failover.
- Allocation and audit: the account tree allocates credit, models and permissions to teams, projects or customers, with usage visible per account and per model.
- No lock-in: callers use the official protocols and SDKs and change only
base_url. To move away, pointbase_urlback at the provider or at a self-hosted XSI.
Security model
- Each tenant has a randomly generated tenant key. Upstream keys are encrypted with it using XChaCha20-Poly1305 before they are stored.
- The tenant key is in turn encrypted with each account's own API key and kept in the account record. The server stores nothing that can decrypt the tenant key directly, so a stolen database alone does not reveal upstream keys.
- Key pools are isolated between tenants and serve only requests from the tenant's own accounts.
- Caller credentials are stripped before forwarding; the upstream sees only the tenant's own key.
- IP, endpoint and model allowlists, quotas and rate limits control who can call and how much.
See the encryption model section of Architecture.
Getting started
- Sign up at a.xsicontrol.com and activate the account to get the tenant owner's API key.
- Sign in to the admin console and add your upstream keys under Model Services, assigning each a level.
- Configure model mapping, level mapping and pricing as needed.
- In the manage console (m.xsicontrol.com), create sub-accounts and credit for members, applications or customers.
- Point the application's
base_urlathttps://api.xsicontrol.comand call with a sub-account's XSI API key.
See Quick start for the full walkthrough.
FAQ
Does XSI Control use or resell my upstream keys?
No. Upstream keys are used only to forward requests made by the tenant's own accounts. XSI Control has no shared key pool and never uses one tenant's keys for another tenant.
Why do I still need an XSI API key?
An upstream key says which provider to call; an XSI API key says who is calling. It decides which account a request belongs to, which key pool it uses and which quotas and allowlists apply, and it records usage. Members and applications can then get fine-grained permissions while each upstream key exists once, managed in one place.
What if I want to migrate later?
Your upstream keys stay on the provider's platform and work anywhere; applications only change base_url and their key. If you need a private deployment, you can self-host XSI with the same integration.