What is BYOK for CRM AI?
Skip the question and your AI usage bills through the vendor's credits, under the vendor's contract with the model provider.
Want to see it first? Book a demo
BYOK — BYOK (bring your own key) for CRM AI means the customer gives the CRM their own API key from an AI model provider, so every AI draft, summary or score runs on the customer's account. The provider bills the customer directly, and the customer's own agreement with that provider governs the data sent to the model.
Also known as: bring your own key
Why BYOK changes the bill and the contract
Most CRMs sell AI as credits or a monthly allowance. The vendor holds the model key, pays the provider and resells the usage to you. With BYOK you open your own account with the provider, create a key and hand it to the CRM. Your account pays for exactly what the CRM uses.
The contract moves too. Under a vendor key, the vendor's terms with the provider cover your prompts and records. Under BYOK, your own terms do. That matters if your legal team has already signed data-handling terms with a provider and wants every AI call under them.
The key itself becomes something you own. It needs a safe home, a usage limit on the provider side and a plan for rotating it. Where the CRM stores it is the first question to ask, which is why BYOK and an API key vault go together.
Managed AI vs BYOK in a CRM
| Question | Managed AI (vendor key) | BYOK (your key) |
|---|---|---|
| Who pays the model provider? | The CRM vendor, then bills you | You, directly |
| What limits usage? | The plan's allowance or credits | Your provider account's limits |
| Whose contract covers the data? | The vendor's | Yours |
| Who rotates the key? | The vendor | You, then update it in the CRM |
How BYOK is set up in a CRM
- 1
Open a provider account
In your company's name, with the model provider.
- 2
Create an API key
From the provider's dashboard, with a spend limit.
- 3
Paste it into the CRM once
Into a vault field, never a plain settings row.
- 4
Switch AI to your key
Drafts, summaries and scores now bill to you.
- 5
Watch and rotate
Use the provider's dashboard; replace the key if it leaks.
The mistake to watch for
BYOK in practice: one key, one vault, your database
SalesCrew runs its AI on Anthropic's Claude. With BYOK, your own Anthropic key sits in Supabase Vault inside your instance's own database, and it's never shown again after you save it. AI calls then run on your account and don't draw down the plan's AI allowance. BYOK is a $99 a month add-on, listed on the pricing page.
Questions
- How is BYOK different from AI credits?
- AI credits are a unit the vendor sells, and the vendor pays the model provider behind the scenes. With BYOK your own provider account pays for each call. Credits cap usage at the plan's allowance; BYOK usage follows the limits you set with the provider.
- Is BYOK more secure than a vendor-managed key?
- BYOK changes whose contract covers the data, which is a governance gain. Security then rests on storage: the key should sit in an encrypted vault and never be shown after entry. A BYOK key in a plain settings field is weaker than a vendor key kept properly.
- Which AI provider keys can a CRM accept?
- Only providers the CRM's AI layer calls. A CRM built on one model family accepts that provider's key, because prompts and features are tuned to it. Check the provider before you sign its data terms.
- Can I switch between BYOK and managed AI later?
- In most CRMs, yes. Both run the same features, and switching changes which account pays for model calls.