Feature
Bring your own keys
Run Niyra on your Anthropic or OpenAI account. Encrypted at rest, never logged, fully under your control.
Niyra ships with our managed LLM access (you pay in credits, we pay the providers). With BYOK, you plug in your own Anthropic or OpenAI key and she runs on your vendor budget.
Why use it
- Cost control at scale: heavy users may find their vendor bill is lower than credit equivalents.
- Enterprise terms: some employers require all LLM use to go through their account. BYOK respects that.
- Apex mode access: Apex / Fable 5 (Claude Opus 4) is BYOK-only.
- No vendor lock-in: your data, your contract with the provider.
Security
Your key is AES-256-GCM encrypted at rest. The encryption key lives in Fly secrets, separate from the database. Decrypted only inside the request handler. Never logged, never returned over the API, never used for anyone else.
If you rotate your key with your provider, just paste the new one in Settings. Old one is overwritten.
What still costs credits
BYOK covers LLM calls. Other things still cost credits:
- Embeddings (memory search): ~$0.0002 per memory operation
- Composio tool calls (Gmail, Slack, etc.): per-call charge
- Voice (TTS / STT): ~6 credits/minute
- Apollo enrichment: ~30 credits per reveal
- Outbound phone calls: telephony charges + processing
- Image generation: ~50 credits per image
LLM is the dominant component. BYOK still saves most of the cost.
Setup
Settings → BYOK → paste your key. Niyra validates it (one test call), and starts routing through it on the next message.
FAQ
- How is my key stored?
- AES-256-GCM at rest. The encryption key lives in Fly secrets, separate from the database. Decrypted only inside the request handler. Never logged, never returned over the API.
- Do credits still apply with BYOK?
- Credits cover non-LLM costs (memory embeddings, Composio actions, voice, telephony). LLM calls run on your vendor account.
- Why BYOK?
- Cost control at scale, enterprise compliance, access to Apex (Fable 5), no vendor lock-in.