BYOK is available exclusively on the Business plan. It is not available during a trial period, as it involves a credential-bearing configuration that persists beyond the trial. Contact sales@knoq.one to upgrade or to discuss Business plan pricing.
How BYOK works
When you configure a BYOK key, Knoq loads it from its encrypted credential store at the start of each model call and passes it directly to the AI provider. The key is:- Encrypted at rest — stored using the same AES-256-GCM encryption used for all integration credentials.
- Never stored in plaintext beyond the in-memory lifetime of a single model call.
- Never logged or returned via API — no endpoint exists to read back a saved BYOK key.
- Write-only from the moment it is saved — Knoq confirms the key is saved but cannot display it again.
Prerequisites
Before setting up BYOK, confirm the following:- Your organization is on an active Business subscription (not a trial).
- You have an Admin role in your Knoq organization.
- You have an API key from a supported AI provider — Anthropic (Claude models) and other supported providers are available. Obtain an Anthropic key from console.anthropic.com.
- You have stored a copy of the API key in your own secure secret store before proceeding.
Setting up BYOK
Open AI Provider settings
Sign in to Knoq and navigate to Admin → Settings → AI Provider. You must have the Admin role to access this section.
Add your API key
Click Add Key. Select your provider from the dropdown, then paste your API key into the field provided.
Save and confirm
Click Save. Knoq will encrypt the key and store it. The field will display a masked placeholder (e.g.
sk-ant-••••••••••••xxxx) to confirm the key is saved. The plaintext key is not stored and cannot be retrieved.Key rotation
To rotate your BYOK key — for example, after a credential rotation policy cycle or a suspected exposure:- Generate a new API key from your AI provider’s console.
- Store the new key in your secret manager.
- Navigate to Admin → Settings → AI Provider in Knoq.
- Click Update Key, paste your new key, and save.
What BYOK covers
When BYOK is active, all AI model calls made by Knoq for your organization use your key. This includes every stage of query processing — from planning which tools to invoke, through the reasoning steps that gather information from your connected tools, to the final answer synthesis. BYOK does not cover third-party tool calls made over MCP (those are authenticated with your OAuth tokens to each source tool), nor does it affect usage by other Knoq organizations — BYOK is scoped strictly to your organization.Cost implications
With BYOK active, model costs appear on your AI provider’s invoice, not on your Knoq subscription. Knoq’s per-org monthly query quota and cost cap are bypassed entirely for BYOK-enabled organizations. You are responsible for monitoring your usage and setting appropriate spending limits in your AI provider’s console. Knoq does not impose its own cost cap when BYOK is configured, because the costs are billed directly between your organization and your AI provider.| Without BYOK | With BYOK |
|---|---|
| Model costs included in Knoq subscription | Model costs billed by your AI provider |
| Subject to monthly query quota | Query quota bypassed |
| Subject to Knoq’s per-org cost cap | Cost cap bypassed |
| Knoq-managed API keys | Your organization’s API key |