Bring Your Own AI Key
NOT YET AVAILABLE Future BYOK architecture.
🔑 BYOK means your provider account, your key and your responsibility. We have not enabled this connection in the current MVP because credential handling needs to be designed and tested with exceptional care.
What BYOK would mean
You would create and control an API key with your chosen AI provider. CRM Intelligence would use that credential to request AI analysis without us owning a shared provider key.
- Your API key should never be hard-coded into our public GitHub code.
- Your key should never be sent to CRM Intelligence servers unless a future architecture explicitly requires it and is designed for secure secret handling.
- Business information sent to a cloud provider would leave your computer, so the data flow would need to be explicit.
- Provider-specific key restrictions, usage limits, billing controls and revocation procedures would need to be part of the design.
Why isn't BYOK enabled yet?
A secure BYOK implementation is more than adding an API-key input box. It requires careful decisions around browser storage, credential exposure, provider APIs, content sent to the provider, error handling, abuse prevention and user education.
We would rather keep this disabled than expose your credentials or business data through an incomplete integration.
Possible future providers
OpenAIFuture API integration — not enabled.
Google GeminiFuture API integration — not enabled.
Hugging Face / other providersFuture provider support subject to security review.
Interested in BYOK?
We can discuss your security requirements, provider preference and the right architecture before this capability is enabled.