Brisvox FAQ
Short answers about what Brisvox is, how it performs, how it handles conversation and how to run it. Every number carries its conditions, and the facts come from the repository.
Last updated:
The project
What is Brisvox?
Brisvox is an open-source real-time voice agent engine written in Rust. One brisvox-server process runs many isolated phone or browser calls: the caller talks, speech-to-text listens, an LLM with tools answers, text-to-speech speaks, and the caller can interrupt at any moment.
The agent is one TOML or YAML file. Your own tools run in your application through the Python or TypeScript SDK, or in Rust inside the server binary.
What license is Brisvox under, and what does it cost?
Brisvox is dual-licensed under MIT or Apache-2.0, at your option. The software is free and there is no hosted cloud, so you pay only the STT, LLM, TTS and telephony providers you choose.
Each call reports what providers bill by (LLM input, cached and output tokens, STT audio seconds, TTS characters) as a session.usage event and as Prometheus totals per provider and model. The speech test fixtures in the repository are under CC BY-SA 4.0 rather than the code license.
Does Brisvox have a hosted cloud?
No. Brisvox is self-hosted only: a prebuilt binary, a container image or a build from source, on your own machines.
Is Brisvox production-ready?
Brisvox is a 0.x project, first released on 15 October 2026. It follows Semantic Versioning, and its library API still changes between releases; the changelog lists each change.
For running it, the server has health and readiness endpoints, Prometheus metrics, optional OpenTelemetry traces, admission control that refuses new calls instead of degrading running ones, graceful drain and per-stage provider failover. No external security audit is claimed. Measure it on your own calls and hardware before you rely on it.
Who makes Brisvox?
Brisvox is made by Bilal and developed in the open on GitHub at github.com/bilal07karadeniz/brisvox. Issues and pull requests are welcome there.
Latency and capacity
How many concurrent calls can one server handle?
In the cloud capacity runs of 16 and 17 October 2026 (Linux containers on AMD EPYC 9655P), one 4 vCPU / 4 GB container held 250 concurrent calls within a p95 voice-to-voice limit of 1110 ms, and 430 with no failed call or lost turn at any latency. An 8 vCPU / 8 GB container held 470 within the same limit and 780 at any latency (p95 about 3.7 s at 780).
These runs used fake providers that speak the real Deepgram and OpenAI-compatible protocols over TLS with fixed latencies, and the real Silero VAD and Smart Turn models on every call. They measure the engine and its provider clients, not the providers. At the 4 vCPU maximum Brisvox used about 1.8 MB of memory and 0.007 cores per call.
How low is the latency?
On real providers (Deepgram nova-3, OpenRouter openai/gpt-6-luna pinned to one upstream, Deepgram Aura voice), with 5 concurrent calls and 100 turns per system, the median voice-to-voice time was 1.85 s for Brisvox and 1.97 s for Pipecat 1.12.0, and the p95 was 2.88 s against 4.35 s. The run was on one Windows machine over the public internet, and the median gap is within the LLM provider's own variance.
The engine's own added time is 0.089 ms at p95 from the end of turn to the LLM request, against a budget of 3 ms, measured over mock providers.
Has Brisvox been measured against LiveKit Agents?
No. LiveKit Agents was not part of the capacity or latency runs, so this site makes no speed, latency or density claim against it. The LiveKit facts on the comparison pages come from LiveKit's own documentation.
What does it cost to run a call?
Brisvox does not set provider prices. Each call reports the units providers bill for: LLM tokens (input, cached, output), STT audio seconds and TTS characters, with duration, turns and latencies. They arrive as a session.usage event, in the transcript, in the log and as Prometheus totals per provider and model. Units, not money.
Conversation
How does Brisvox handle interruptions (barge-in)?
Every user turn is a numbered epoch, and frames from a stale epoch are dropped at every stage, so audio from an answer the caller already cut off does not play. A Clear goes straight to the transport, and the LLM round, the segmenter and the open TTS contexts are cancelled.
After the barge-in the LLM context holds only the text that was actually played, so the model does not believe it said words the caller never heard.
What about a cough, a door or a "mm-hmm"?
The interruption policy judges every candidate: a minimum number of words, backchannel lists per language such as "yeah" and "uh-huh", an echo guard that recognises the agent's own words coming back, and a level gate against a quieter second voice.
In 0.1.4 (November 2026), pause-then-decide is on by default: at a barge-in candidate the agent pauses its audio and, within a decision window of 1500 ms by default, either interrupts or resumes the same response from the paused point. Any recognised word from the caller interrupts at once.
How does Brisvox decide that the caller has finished speaking?
When the Silero voice activity detector sees the caller fall silent, two things start at once: the speech-to-text Finalize and Smart Turn v3.2, an on-device end-of-turn model that runs on a dedicated inference pool. If the model says the utterance is complete, the turn ends as soon as the STT final arrives; if not, the turn waits, with a fallback silence deadline. A fixed-silence policy is also available.
Can a tool with side effects run twice?
Tools are marked read_only or side_effect. A side-effect tool never runs speculatively and never runs twice for one call id, and an identical repeat in the same turn is refused. A later turn or another call is not covered: for a rule such as one refund per order, ever, add your own idempotency key. The exact scope is in docs/TOOLS.md.
Can an agent use MCP tools?
Yes. An agent file can name MCP (Model Context Protocol) servers, as a program the server starts or a streamable HTTP endpoint. The tools on a server's allowlist are offered to the LLM with the same guarantees as the server's own tools. The cargo feature is mcp, and it is in the prebuilt binaries and the container image.
Which languages does Brisvox support? Does it support Turkish?
English and Turkish are supported. Turkish is a first-class language: the TTS stage rewrites written forms such as amounts, dates and times into the words a person says, and the interruption policy has Turkish backchannel and command lists. An agent can list several languages and follow the caller from one to the other in the middle of a call.
Providers, telephony and deployment
Which providers does Brisvox support?
Speech-to-text: Deepgram, AssemblyAI, Gladia, sherpa-onnx on your own machine, and servers that speak the OpenAI Realtime transcription protocol. Language models: OpenAI, Anthropic, Gemini and any OpenAI-compatible endpoint such as Groq, Together, Fireworks, vLLM, Ollama and OpenRouter.
Text-to-speech: Cartesia, ElevenLabs, Deepgram Aura and local servers of the OpenAI /v1/audio/speech shape such as Kokoro-FastAPI and Chatterbox. Speech-to-speech: OpenAI Realtime and Gemini Live.
Does Brisvox need a LiveKit or other media server?
No. The generic WebSocket, Twilio Media Streams and Telnyx media streaming transports are built in, and WebRTC and a SIP trunk listener are optional cargo features. Callers connect to brisvox-server directly.
Does Brisvox work with Twilio, Telnyx and SIP trunks?
Yes. Twilio Media Streams and Telnyx media streaming are built in, and DTMF, call transfer and hang-up come from the call-control feature, which the prebuilt binaries include. A SIP trunk listener (UDP, TCP or TLS, with SRTP) is the separate cargo feature sip, which is not in the prebuilt binaries, so you build with it added. Phone audio is G.711 mu-law or A-law.
How do I put a voice agent on a website?
Use @brisvox/web, one dependency-free ES module for a talk button: WebRTC first, with an automatic WebSocket fallback on the same port when WebRTC media cannot get through, plus microphone, playback, barge-in and a clean hang-up. Build the server with the webrtc feature.
Can I run a voice agent with no API keys?
Yes. docker compose -f deploy/local/compose.yaml up runs speech recognition (sherpa-onnx), a language model (Ollama) and a voice (Kokoro) on your CPU, and you talk to it in the browser. It needs Docker, 4 or more cores and 8 GB of memory, and the first start downloads about 6.5 GB. Nothing leaves the machine.
Can I self-host Brisvox with Docker?
Yes. A multi-architecture image (linux/amd64 and linux/arm64) with the Smart Turn model inside is at ghcr.io/bilal07karadeniz/brisvox-server. Prebuilt binaries cover Linux x86_64 and aarch64 (glibc 2.39 or newer), macOS aarch64 and Windows x86_64, each release with a SHA256SUMS file. Listeners fail closed: off loopback the server refuses to start without authentication (a session secret or a static token).
Which SDKs are available?
Python: pip install brisvox (Python 3.11 or newer). TypeScript: npm i brisvox (Node 20 or newer), which includes the agent SDK and @brisvox/web, the browser client. The SDK runs your tools in your own process, and the server connects out to it over the agent protocol. Tools can also be written in Rust inside your own server binary with cargo add brisvox.
Is Brisvox a Pipecat alternative? Can I keep my Pipecat clients?
Yes, for phone and browser voice agents that you want to self-host as one process. Brisvox accepts RTVI, the protocol of Pipecat's client SDKs, so those clients can connect to a Brisvox server. The comparison page lists what Pipecat documents that Brisvox does not have.
Where it is published
| Where | What | Install |
|---|---|---|
| GitHub | Source, issues, releases with prebuilt binaries | git clone https://github.com/bilal07karadeniz/brisvox |
| crates.io | The server and the library crates | cargo install brisvox-server --locked --features all-providers,call-control,smart-turn-ort,mcp,webrtc |
| PyPI | Python agent SDK | pip install brisvox |
| npm | TypeScript agent SDK and browser client | npm i brisvox |
| GHCR | Container image, linux/amd64 and linux/arm64 | docker run --rm ghcr.io/bilal07karadeniz/brisvox-server:latest --version |
| The book | Documentation | Read online |
Did not find your question? Open an issue on GitHub.