Platform
Platform
Media plane, control plane, API and worker — the whole stack, on your own machines
Book a demoWhat it is
Four processes and a database, and you can point at every one of them
A media server routing packets on a box you rent. A control plane that mints the join token and dispatches the agent. An API holding call history, statistics and enrolment. A worker that sits in the room and writes down what happened. Nothing between them is somebody else’s service.
Why it is shaped this way
The control plane never carries media, so the media plane can be yours
Tokens, dispatch and the MCP surface are small, stateless and cheap to run anywhere. Audio and video are neither. Splitting them is what lets the expensive half sit in a region you chose, under a key pair you hold, while the cheap half stays boring.
- Media plane
- livekit-server, one per region, independent
- Control plane
- tokens, dispatch, MCP — never media
- API
- history, statistics, enrolment, webhooks
What it is not
It is not running for you until you stand it up
There is no account here that holds your calls, because there is no platform here holding them. That is the trade: sovereignty and unit economics, at the price of operating a box. If you need one agent occasionally and never want to think about a firewall rule, a hosted platform is the better trade and we would rather say so.