Your OpenAI, Anthropic, or Gemini key. Your invoice. Your DPA.

On any plan, Kelu can call the model on your provider account with your key. You keep the model choice, the usage bill, and the data-processing agreement you already have with OpenAI / Anthropic / Google. Kelu is the platform layer; the LLM traffic runs on you.

How BYOK works

Per-workspace credentials — every customer-facing answer runs on the account you configured

01
OpenAI, Anthropic, Gemini, Bedrock, and more

Bring Your Provider Credential

  • Configure a provider credential per workspace
  • Applies to every knowledge base in the workspace
  • Credentials encrypted at rest with AES-256-GCM
  • Rotate or revoke in the dashboard; no re-deploy required
  • Fallback to the deployment provider when a credential is missing
02
Everywhere the model is called

Coverage Across the Answer Path

  • Streaming widget and portal answers — on your credential
  • Multi-knowledge-base answers — on your credential
  • Slack and Microsoft Teams bots (AnswerForBot) — on your credential
  • Form deflector, including grounding verification — on your credential
  • Reranking on the LLM grader fallback — on your credential
03
Honest about the gaps

What Still Runs on Deployment Provider

  • Kelu's internal diagnostic tooling
  • Conversation title generation (small fixed-cost call)
  • Image-to-text (DescribeImage) for chat attachments
  • Embeddings, unless you use an OpenAI key on the OpenAI API
  • Hosted cross-encoder rerankers (Cohere/Voyage/Jina — not LLM providers)
Why BYOK exists

The two questions Enterprise buyers actually ask

'Whose account is charged for the tokens?' and 'Whose DPA covers the data?' — the two questions every enterprise procurement conversation lands on. BYOK answers both with 'yours'. Traffic runs on your OpenAI / Anthropic / Gemini account under the terms you already negotiated. Kelu is the platform above the model, not the LLM vendor.

  • Volume LLM contracts you already negotiated apply directly
  • Model choice is yours — no vendor lock-in via the platform
  • Data-processing terms are yours — no additional third-party review
  • Rotate the credential without re-deploying anything
  • Revert to default switches back to Kelu's models at any time
Why teams trust it

Private content stays private, and secrets stay sealed

Credentials are encrypted

Connection secrets are sealed with AES-256-GCM. If one can't be opened, the sync stops instead of running without it.

Private stays private

Internal knowledge bases have no public surface at all. To keep past tickets private, add them to an internal knowledge base.

Every answer from your docs shows its sources

Numbered links point to the page and section each part of the answer came from, so anyone can check it in one click.

Got questions?

Frequently Asked Questions

Common questions about Bring Your Own Model (BYOK)

Run the platform, keep the LLM contract

BYOK is on every plan. Talk to us about Enterprise if you also need SSO and a countersigned DPA.

Free to start · No credit card required