Skip to content
Palanor is in early release, with our founding customers.Become a founding customer →
PalanorPalanor
← Billing & Plans

BYOLLM Explained

Bring your own LLM API key — when, why, and how it works.

Updated 2026-10-05

BYOLLM lets you point Palanor at your own LLM provider keys (Anthropic, OpenAI, Azure OpenAI) instead of routing through Palanor's managed credentials. Two reasons to use it: compliance and cost predictability.

Compliance

Some enterprises require that prompts and completions live entirely within their own provider account — typically because the LLM provider has a signed BAA or DPA with them but not with Palanor. BYOLLM keeps the entire LLM I/O on your account.

Cost predictability

If you have negotiated discounted token rates with a provider, BYOLLM lets Palanor inherit those rates. You pay Palanor Enterprise plus your own LLM bill.

Credits

Language-model work on your key uses no credits from your organization's pool. Images and audio still do. See Credits Explained.

How it works

Go to Settings → Connections and add your API key. Palanor encrypts it at rest. You can flip a single switch to route all future LLM calls through your key. Switching back is also one click.

What does not change

Math, ranking, scenario compute, prompt structure — all of these are Palanor's IP and are unchanged by BYOLLM. Only the token I/O moves to your provider account.

Still stuck?

Email support@palanor.com or check the status page.

Cookies

We only use essential cookies to keep you signed in and remember your theme. No analytics, no tracking, no ads. See the Privacy Policy for the full read.