Requirements

Voxagent is a composable platform. Each service runs in its own container, so you can scale components independently. Before deploying, size your infrastructure according to expected concurrent sessions — everything else (backbone services) stays roughly constant.

Software dependencies

• Docker 24+ and Docker Compose v2.24+
• 64-bit Linux host (Ubuntu 22.04 LTS or equivalent). macOS works for local dev.
• Outbound internet access (registry, LLM/STT/TTS providers, STUN/TURN)
• Ports accessible from your users' browsers: frontend, backend API, Keycloak, LiveKit WebRTC (TCP 7881, UDP 50000–60000).

Per-service resource baselines

The table below shows combined CPU / RAM / Disk requirements for each service at typical concurrent session loads. Values are empirical baselines from production.

How to read this:

• Session-bound services (livekit-server, python-worker, egress, websocket-media-bridge) scale linearly with the number of active calls. They are what you need to plan for.
• Backbone services (Postgres, Kafka, Keycloak, Redis, MinIO, etc.) have a largely fixed footprint — you can host them once and reuse across tenants.
• Disk mostly grows in Postgres (transcripts, invoices), Kafka (event retention) and MinIO (call recordings). Plan storage with retention in mind.

Resource calculator

Use the calculator to estimate the total footprint of the application stack at your expected peak concurrency:

Notes

• Numbers are for the application layer only. CPU/RAM/disk for LLM, STT and TTS providers (or self-hosted models) are billed separately by those vendors and are not included here. We'll cover model cost planning in a dedicated page.
• Add a safety margin of 20–30% on top of the calculator output for headroom, spikes and OS overhead.
• For high-availability production deployments you should double the backbone figures (Postgres replica, Kafka with replication factor ≥ 2, etc.).

Minimum machine sizing (at a glance)

For everything above 50 concurrent sessions we recommend splitting livekit-server + python-worker onto their own hosts, so that media and agent CPU load doesn't starve the backbone.