Voice AI BYOK
Voice AI BYOK: bring your own keys, keep your provider economics.
PeachDesk runs every stage of a voice agent on the sourcing mode you choose: PeachDesk-managed providers, your own provider keys, or self-hosted inference. Bring your own keys and your agents run on your provider accounts while PeachDesk handles orchestration, telephony, and tooling.
How BYOK works in PeachDesk
A voice agent is a pipeline: speech-to-text, a language model, and text-to-speech. PeachDesk routes each stage independently, per agent. Point a stage at your own provider account and the call runs on your keys, your rate limits, and your provider relationship. The same controls exist in the dashboard and through the voice agent API, so your platform team can manage sourcing in code.
Overrides apply per agent, not per node, which keeps the model simple: one agent, one sourcing decision per stage.
Mix sourcing modes inside one agent
Frontier mode, Local mode, mix and match. An agent can transcribe on your own keys, reason on a PeachDesk-managed model, and speak through self-hosted inference on your GPUs. You change the sourcing mode per stage, per agent, without rebuilding anything.
That is how teams adopt BYOK gradually: start fully managed, then move the stages where you already have provider accounts or volume.
{
"name": "Front desk agent",
"pipeline": {
"speech_to_text": { "sourcing_mode": "byok" },
"language_model": { "sourcing_mode": "byok" },
"text_to_speech": { "sourcing_mode": "peachdesk_hosted" }
}
}Your keys never touch PeachDesk billing
BYOK calls never consume PeachDesk credits and are never gated by PeachDesk billing. If your PeachDesk balance runs out, agents on your own keys keep running; your providers bill you directly, on your own accounts. Frontier mode, where PeachDesk manages the providers, is always metered. See how the two fit together on PeachDesk pricing.
Keys are encrypted at rest
Provider credentials are scoped to your organisation and encrypted at rest before they are written to storage. Agents reference the stored credential instead of embedding the key, so secrets stay out of agent definitions. Manage credentials from the dashboard or through the API.
Pair BYOK with Local mode
Per-stage mixing extends to self-hosted inference. Local mode runs leading open models on your own GPUs with zero per-minute inference cost from providers: there is no per-minute provider charge, and you pay for GPU capacity instead. Your speech data stays in your environment.
BYOK questions, answered
Do BYOK calls consume PeachDesk credits?
No. Calls that run on your own provider keys never consume PeachDesk credits and are never gated by PeachDesk billing. PeachDesk orchestrates the agent, the call, and the tooling; your providers bill you directly on your own accounts. Only usage on PeachDesk-managed providers, which is Frontier mode, is metered.
Which pipeline stages can run on my own keys?
Every stage of the voice pipeline: speech-to-text, the language model, and text-to-speech. You choose the sourcing mode per stage and per agent, so one agent can transcribe on your keys, think on a PeachDesk-managed model, and speak through self-hosted inference. Overrides apply per agent, not per individual node.
How does PeachDesk store my provider keys?
Provider credentials are scoped to your organisation and encrypted at rest before they are written to storage. Agents reference the stored credential rather than embedding the key itself, so secrets stay out of your agent definitions. You manage credentials from the dashboard or through the API.
Can I mix my own keys with PeachDesk-managed providers?
Yes. Mixing is the point. Each stage of each agent independently runs on PeachDesk-managed providers, your own keys, or self-hosted inference. Teams often start fully managed for speed, then move their highest-volume stages to their own keys once usage grows and provider accounts are in place.
New to the term? Read the BYOK definition in the glossary, or set up your first key with the credential documentation.
Run your next call on your own keys
Create an account, add a provider credential, and point one pipeline stage at it.