Universal local runtime for STT and TTS models
Project description
Vox
The local voice layer for realtime speech agents. Vox is a self-hosted runtime that gives speech-to-text and text-to-speech models one operational surface: you pull a model like Ollama and serve one OpenAI-compatible API. On top of that it adds a full realtime conversation stack: VAD, streaming STT, end-of-utterance turn detection, TTS, and true barge-in over WebRTC. You bring the LLM; Vox is the ears and the mouth.
Why Vox
- Realtime voice, self-hosted. A local, OpenAI-Realtime-style conversation API over WebRTC, WebSocket, or gRPC, covering VAD, streaming transcription, semantic turn-taking, and real barge-in, with any LLM in the middle. Vox owns the audio; you own the text generation.
- One runtime for STT and TTS.
pulla model,serveone API, no per-model Python wiring. - Many backends, one interface. ONNX, CTranslate2, Torch, NeMo, and vLLM model families behind the same API.
- OpenAI-compatible. Drop-in
/v1/audio/speechand/v1/audio/transcriptions, plus REST, WebSocket, and gRPC. - Pull-on-demand. Models and their adapters install on first pull, from a community registry.
- Custom voices. Store cloned voices for clone-capable TTS models, shared across HTTP and gRPC.
- Local-first and lean. Docker images start empty and install only what you use; a torch-free lean image runs the CT2/ONNX and streaming paths without the ~2GB torch stack.
Quickstart
pip install vox-runtime
vox pull kokoro-tts:v1.0
vox pull whisper-stt:large-v3
vox serve
Then hit the local API:
curl -X POST http://localhost:11435/v1/audio/speech \
-H "Content-Type: application/json" \
-d '{"model":"kokoro-tts:v1.0","input":"Hello from Vox"}' \
-o output.wav
gRPC starts with vox serve too and listens on :9090 by default.
Realtime voice conversations
Vox ships a self-hosted realtime voice stack, the local answer to the OpenAI Realtime API. Vox owns VAD, streaming STT, end-of-utterance (EOU) turn detection, TTS, and interruption handling; you own the LLM. User speech comes in, transcripts come out, you generate a reply with any LLM, stream the text back, and Vox speaks it with real barge-in.
Three transports carry a conversation session:
- WebRTC: Vox hosts the browser media connection (mic in, assistant audio
out) while your backend drives a control stream. A dependency-free client is in
examples/rtc-browser-client.html. - WebSocket (PondSocket) and gRPC: you own microphone capture and playback, and audio is PCM16 over the stream.
What Vox handles for you:
- VAD: Silero on onnxruntime (no torch, no runtime model download).
- Turn-taking: a semantic EOU detector shortens the endpointing delay when the user clearly finished and waits when they didn't.
- Barge-in: two-stage interruption with self-echo and backchannel rejection, so the assistant doesn't cancel itself on its own audio or a stray "mhm".
- Turn profiles:
headset,browser_default,speakerphone, andnoisy_roomacoustic presets. - Browser-native events: captions, turn state, and barge-in signals forwarded straight to a WebRTC data channel, with no backend relay required.
Full protocol and event reference: docs/conversation-events.md.
What it does
Vox manages STT and TTS models through a consistent runtime API. Models are downloaded from Hugging Face, and each model family is handled by an adapter that installs automatically on first pull. Docker images start without any models or adapters; pulling a model installs the matching adapter on demand.
Install
pip install vox-runtime
# or
uv pip install vox-runtime
Usage
Server
vox serve --port 11435 --device auto
Pull a model
vox pull kokoro-tts:v1.0
vox pull parakeet-stt:tdt-0.6b-v3
vox list
Transcribe (STT)
# CLI
vox run parakeet-stt:tdt-0.6b-v3 recording.wav
vox stream-transcribe parakeet-stt:tdt-0.6b-v3 meeting.mp3
# OpenAI-compatible: thin response (just {"text": ...})
curl -F file=@recording.wav http://localhost:11435/v1/audio/transcriptions
# Rich response with segments, word timestamps, entities, topics
curl -F file=@recording.wav -F response_format=verbose_json \
http://localhost:11435/v1/audio/transcriptions
Synthesize (TTS)
# CLI
vox run kokoro-tts:v1.0 "Hello, how are you?" -o output.wav
vox stream-synthesize kokoro-tts:v1.0 "Hello, how are you?" -o output.wav
# OpenAI-compatible
curl -X POST http://localhost:11435/v1/audio/speech \
-H "Content-Type: application/json" \
-d '{"model":"kokoro-tts:v1.0","input":"Hello"}' \
-o output.wav
Create and use custom voices
Vox can store cloned voices and reuse them across HTTP and gRPC. This is only available for TTS adapters that declare voice-cloning support. Preset-only models still list their built-in voices, but they will reject stored cloned voices at synthesis time.
# create a cloned voice from a reference sample
curl -X POST http://localhost:11435/v1/audio/voices \
-F audio_sample=@sample.wav \
-F name="Roy" \
-F language=en \
-F reference_text="Hello there from my custom voice"
# list voices, including cloned voices for clone-capable models
curl "http://localhost:11435/v1/audio/voices?model=openvoice-tts:v1"
# download the stored reference audio
curl -o reference.wav http://localhost:11435/v1/audio/voices/voice1234/reference
# synthesize with the stored voice id returned at creation time
curl -X POST http://localhost:11435/v1/audio/speech \
-H "Content-Type: application/json" \
-d '{"model":"openvoice-tts:v1","input":"Hello from Vox","voice":"voice1234"}' \
-o output.wav
# delete a stored cloned voice
curl -X DELETE http://localhost:11435/v1/audio/voices/voice1234
Search available models
vox search
vox search --type tts
vox search --type stt
Other commands
vox list # downloaded models
vox ps # loaded models
vox show kokoro-tts:v1.0
vox rm kokoro-tts:v1.0
vox voices kokoro-tts:v1.0
Streaming APIs
Use the unary HTTP endpoints for short bounded requests.
Use the WebSocket APIs for:
- long recordings
- browser or pipeline streaming
- live uploads where the client stays connected until the final result arrives
These streaming sessions are intentionally short-lived:
- no job store
- no durable result retention
- disconnect cancels the session
Long-form STT over WebSocket
Endpoint:
ws://localhost:11435/v1/audio/transcriptions/stream
Protocol:
- Client sends a JSON config message.
- Client sends binary audio chunks.
- Client sends
{"type":"end"}. - Server emits progress events and one final
doneevent with the full transcript.
Example config:
{
"type": "config",
"model": "parakeet-stt:tdt-0.6b-v3",
"input_format": "pcm16",
"sample_rate": 16000,
"language": "en",
"word_timestamps": true,
"chunk_ms": 30000,
"overlap_ms": 1000
}
Server events:
{"type":"ready","model":"parakeet-stt:tdt-0.6b-v3","input_format":"pcm16","sample_rate":16000}
{"type":"progress","uploaded_ms":60000,"processed_ms":30000,"chunks_completed":1}
{"type":"done","text":"full transcript","duration_ms":120000,"processing_ms":8420,"segments":[]}
Notes:
pcm16is the simplest long-form transport. The CLI helper uses it by default.wav,flac,mp3,ogg, andwebmare also accepted asinput_format, but each binary frame must be a self-contained decodable blob, such as aMediaRecorderchunk. Arbitrary byte slices of one compressed file are not supported.
Long-form TTS over WebSocket
Endpoint:
ws://localhost:11435/v1/audio/speech/stream
Protocol:
- Client sends a JSON config message.
- Client sends one or more
{"type":"text","text":"..."}messages. - Client sends
{"type":"end"}. - Server emits:
readyaudio_startprogress- binary audio chunks
- final
done
Example config:
{
"type": "config",
"model": "kokoro-tts:v1.0",
"voice": "af_heart",
"speed": 1.0,
"response_format": "pcm16"
}
Server events:
{"type":"ready","model":"kokoro-tts:v1.0","response_format":"pcm16"}
{"type":"audio_start","sample_rate":24000,"response_format":"pcm16"}
{"type":"progress","completed_chars":120,"total_chars":480,"chunks_completed":1,"chunks_total":4}
{"type":"done","response_format":"pcm16","audio_duration_ms":2450,"processing_ms":891}
Binary frames between audio_start and done carry the synthesized audio payload. pcm16 and opus are currently supported for the raw stream; the CLI helper writes pcm16 into a WAV file.
Streaming CLI helpers
These commands sit on top of the WebSocket APIs:
vox stream-transcribe parakeet-stt:tdt-0.6b-v3 meeting.mp3
vox stream-transcribe parakeet-stt:tdt-0.6b-v3 meeting.wav --json-output
vox stream-synthesize kokoro-tts:v1.0 script.txt -o script.wav
vox stream-transcribe transcodes the local input to streamed mono pcm16 on the client side, then uploads chunk-by-chunk over the WebSocket session. For compressed inputs this uses ffmpeg; install it if you want the helper to handle formats that soundfile cannot stream directly.
Docker
# GPU (default)
docker compose up -d
vox pull kokoro-tts:v1.0 # auto-installs adapter inside container
# CPU (lean, torch-free)
docker compose --profile cpu up -d
Models and dynamically installed adapters persist in a Docker volume across restarts, so no image rebuild is needed to add new models.
Four image variants are published: :latest (amd64 CUDA), :lean and :cpu
(multi-arch CPU), and :spark (arm64 NVIDIA). The :lean image drops the ~2GB
torch stack and still runs the CT2/ONNX and streaming paths; vox pull then
refuses torch-based models up front instead of failing at load time. See
docs/docker.md for the full matrix and build options.
Representative models
Vox pulls models from the vox-registry community catalog: ~20 model families across 5 backends (ONNX, CTranslate2, Torch, NeMo, and vLLM). A representative slice:
| Model | Type | Description |
|---|---|---|
parakeet-stt:tdt-0.6b-v3 |
STT | NVIDIA Parakeet TDT 0.6B v3 (ONNX on CPU, NeMo on CUDA) |
whisper-stt:large-v3 |
STT | OpenAI Whisper Large V3 via CTranslate2 |
whisper-stt:base.en |
STT | Whisper Base English |
qwen3-stt:0.6b |
STT | Qwen3 ASR 0.6B |
voxtral-stt:mini-3b |
STT | Voxtral Mini 3B speech-to-text |
kokoro-tts:v1.0 |
TTS | Kokoro 82M (ONNX on CPU, Torch on CUDA) |
qwen3-tts:0.6b |
TTS | Qwen3 TTS 0.6B |
voxtral-tts:4b |
TTS | Voxtral 4B TTS via vLLM-Omni |
openvoice-tts:v1 |
TTS | OpenVoice voice-cloning backend |
piper-tts:en-us-lessac-medium |
TTS | Piper English US Lessac |
dia-tts:1.6b |
TTS | Dia 1.6B multi-speaker dialogue |
sesame-tts:csm-1b |
TTS | Sesame CSM 1B conversational speech |
More models at vox-registry. Add a model by submitting a PR with a JSON file.
Security
Vox is local-first and runs open by default. For deployments that expose the port beyond localhost, set these environment variables:
VOX_API_KEY: when set, every HTTP route, audio websocket, and gRPC call requires the key (sent asAuthorization: Bearer <key>, anx-api-keyheader, or anapi_keyquery param). Health/probe paths and gRPC health and reflection stay open so orchestrator liveness checks keep working. When unset, the server is fully open (unchanged behavior).VOX_ALLOW_UNVERIFIED_ADAPTERS=1: pulling a model installs its adapter as a pip package; by default only the registry'svox-*packages are allowed. Set this only if you intentionally pull adapters outside that set.
gRPC still uses an insecure port and reflection; terminate TLS at a proxy for untrusted networks.
API
All HTTP endpoints live under /v1/. STT/TTS endpoints are OpenAI-compatible by default; pass response_format=verbose_json on /v1/audio/transcriptions for the rich payload (segments, word timestamps, entities, topics).
| Endpoint | Method | Purpose |
|---|---|---|
/v1/health |
GET | Health check |
/v1/models |
GET | List downloaded models |
/v1/models/{name} |
GET | Model details |
/v1/models/{name} |
DELETE | Remove a model |
/v1/models/pull |
POST | Download a model |
/v1/models/loaded |
GET | Currently loaded models |
/v1/audio/transcriptions |
POST | Transcribe audio (OpenAI-compatible; verbose_json for rich payload) |
/v1/audio/speech |
POST | Synthesize speech (OpenAI-compatible; supports stream) |
/v1/audio/voices |
GET | List voices for a TTS model |
/v1/audio/voices |
POST | Create a stored cloned voice |
/v1/audio/voices/{id} |
DELETE | Delete a stored cloned voice |
/v1/audio/voices/{id}/reference |
GET | Download the stored reference audio |
/v1/audio/transcriptions/stream |
WS | Long-form streaming STT |
/v1/audio/speech/stream |
WS | Long-form streaming TTS |
/v1/rtc/sessions |
POST | Create a realtime WebRTC voice session |
/v1/rtc/sessions/{id}/offer |
POST | Submit the browser SDP offer, get the answer |
/v1/rtc/sessions/{id}/candidates |
POST | Trickle browser ICE candidates |
/v1/rtc/sessions/{id}/events |
GET (SSE) | Vox-side ICE / connection-state events |
The realtime conversation control stream runs over PondSocket
(/v1/socket channel /conversation/{id} or /rtc/{id}) or gRPC; see
docs/conversation-events.md.
gRPC
vox serve starts the gRPC server automatically unless you disable it with --grpc-port 0.
- default gRPC port:
9090 - health and model lifecycle:
HealthService.HealthHealthService.ListLoadedModelService.PullModelService.ListModelService.ShowModelService.Delete
- speech:
TranscriptionService.TranscribeSynthesisService.SynthesizeSynthesisService.ListVoicesSynthesisService.CreateVoiceSynthesisService.DeleteVoiceStreamingService.StreamTranscribe
- realtime conversation (bidi streams):
ConversationService.ConverseRtcService.Control
The gRPC voice APIs use the same stored voice data as HTTP. Creating or deleting a cloned voice over one transport is immediately visible through the other.
Adding a model
Write an adapter package that implements STTAdapter or TTSAdapter:
from vox.core.adapter import TTSAdapter
class MyAdapter(TTSAdapter):
def info(self): ...
def load(self, model_path, device, **kwargs): ...
def unload(self): ...
@property
def is_loaded(self): ...
async def synthesize(self, text, *, voice=None, speed=1.0, **kwargs):
yield SynthesizeChunk(audio=audio_bytes, sample_rate=24000)
Register it via entry point:
[project.entry-points."vox.adapters"]
my-model = "my_package.adapter:MyAdapter"
Add a JSON file to vox-registry so vox pull can find it.
For the package/runtime boundary, see the adapter contract.
Project structure
src/vox/
core/ # types, adapter ABCs, scheduler, store, registry
audio/ # codec, resampling, pipeline
server/ # FastAPI routes
cli.py # Click CLI
adapters/
vox-parakeet/ # NVIDIA Parakeet STT
vox-kokoro/ # Kokoro TTS
License
Apache-2.0
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file vox_runtime-0.2.93.tar.gz.
File metadata
- Download URL: vox_runtime-0.2.93.tar.gz
- Upload date:
- Size: 2.7 MB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.13.0
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
2efbc2bf2463983f7dff14355af81069d2635e58c7bd42e1330c63f73352673b
|
|
| MD5 |
c5827dccb3ff85f2a32bb3ddcd2a966f
|
|
| BLAKE2b-256 |
28ded6059ab8a5f24b801597da356e667c2bfe738df3423fdb8bfe0c6168ccac
|
File details
Details for the file vox_runtime-0.2.93-py3-none-any.whl.
File metadata
- Download URL: vox_runtime-0.2.93-py3-none-any.whl
- Upload date:
- Size: 2.2 MB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.13.0
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
d80bd8d8b9589876613f05039f2e1936288a5b79b014c29244e35f3aedda27c6
|
|
| MD5 |
c299887410ca0858491dfc1ca7e400d5
|
|
| BLAKE2b-256 |
dc00722cfdf81206fda6947024385380292dc2d2463a87052b2a724dee23732b
|