BYOK: When It Makes Sense to Bring Your Own AI Key
Bring-your-own-key isn't just 'we support other providers' — it's a specific fee structure that only charges for the savings it creates, and it's worth understanding before deciding whether to use it.
Most "we support multiple AI models" marketing stops at the fact of multi-provider support and never explains the economics underneath it. That's the more interesting part. Piskes lets you bring your own API key for the AI providers it routes to, and the fee model behind that — a percentage of what you saved, not a flat markup — is worth understanding on its own terms before deciding whether BYOK is worth setting up.
What BYOK actually is
Every AI call in Piskes — from any of the 17 apps, or from a Go-backend workflow — goes through one gateway. By default, that gateway uses Piskes's own provider keys, and usage is metered against your credit balance. BYOK lets you swap that: instead of the request running against Piskes's OpenAI or Anthropic key, it runs against your own.
The key is stored per provider, not per model. One OpenAI key covers every OpenAI model the gateway routes to; one Anthropic key covers every Anthropic model. You're not managing a key per model, which matters in practice — model lineups change more often than provider relationships do, and re-keying every time a new model ships would be exactly the kind of maintenance tax BYOK is supposed to remove.
The fee structure is the actual story
The part worth paying attention to: BYOK doesn't eliminate Piskes's fee, but it changes what the fee is calculated against. Instead of paying the platform's standard markup on every token, you pay a percentage of what the request would have cost you on the platform's own key. If your own provider pricing is meaningfully cheaper than what you'd pay through platform credits — which is common at higher volume, where providers offer negotiated or committed-use rates — BYOK's fee is a cut of the delta, not a tax on top of your already-lower cost.
That's a materially different pitch than "connect your key for free." A flat "no fee for BYOK" model would be generous but also unsustainable for a platform that still has to operate the gateway, handle routing, retries, and observability regardless of whose key is being called. A fee proportional to savings is the more honest version: Piskes only makes money on BYOK when BYOK is actually saving you money, and the incentive stays aligned — there's no reason for the platform to discourage you from using cheaper provider pricing you've negotiated yourself.
Where the key actually lives
The gateway won't write a BYOK key to storage in plaintext under any circumstance. If the encryption key the platform needs to store your provider key isn't configured, key storage fails outright rather than falling back to writing it unencrypted. That's a deliberate refusal, not a missing feature — a platform that silently degrades to plaintext storage under a misconfiguration is a worse outcome than one that just stops working until the misconfiguration is fixed. If you're evaluating whether to trust a platform with your own provider credentials, "it refuses to store your key insecurely" is a more concrete signal than "we take security seriously."
When BYOK is worth setting up
BYOK makes the most sense once your AI usage is large enough that your own negotiated provider rate, or simply your own provider account's volume discounts, is meaningfully below what platform credits cost per token. Below that volume, the operational overhead of managing your own key — rotating it, monitoring your own provider-side spend, handling your own rate limits — usually isn't worth it relative to just using platform credits and letting Piskes absorb that complexity.
It's also worth considering if you already have a provider relationship for reasons outside Piskes — an enterprise agreement with OpenAI or Anthropic, say — and want your Piskes usage to count against volume commitments you're already paying for regardless. In that case BYOK isn't about the per-token savings at all; it's about not paying twice for the same commitment.
The bottom line: BYOK is a real lever, not a checkbox feature, and it's built around an economic structure — fee on savings, not fee on top — that rewards using it exactly when it makes sense to, and doesn't punish you for using platform credits the rest of the time.