Comparison · checked 22 October 2026

Xebit vs LiveKit: framework you build on, or the platform underneath

LiveKit suits teams that want an open source realtime framework, large rooms and the freedom to assemble every part of a voice agent themselves. Xebit suits teams that want the voice platform already assembled, with campaigns, observability and people on live calls built in, run in Xebit VoiceCloud or on their own infrastructure, including air gapped.

Updated

Xebit logoXebitVoice AI platform, cloud or on prem
vs
LiveKit logoLiveKitOpen source realtime media framework
Xebit and LiveKit at a glance
At a glanceLiveKit logoLiveKit
Deployment optionsXebit VoiceCloud, managed by Xebit; or Xebit VoiceKit on Docker or Kubernetes in your data centre, your cloud account or air gapped.LiveKit Cloud, or self hosted as a single binary, on Docker, or on Kubernetes with Helm charts. Agents run on LiveKit Cloud or your own servers.
Open sourceNo. Xebit is proprietary software; Xebit VoiceKit is an annual licence.Yes. Server and Agents are Apache 2.0; the turn detection models use a separate LiveKit model licence.
TelephonyNot provided. You bring your own carrier and numbers over SIP or WebSocket.Sells US local and toll free numbers in LiveKit Cloud, or you bring your own SIP trunk.
Pricing modelXebit VoiceCloud about $0.052 per connected minute, models included, from $258 a month. Xebit VoiceKit is a flat annual licence by band, regardless of volume.Open source self hosting has no licence fee. LiveKit Cloud has a free tier and paid plans billed on agent minutes, participant minutes, bandwidth and telephony.
The short answer

Which should you choose?

Both are good at different jobs. Here is when each one is the better fit.

Choose Xebit if

  • You want a finished voice platform, with campaigns, scheduling, transcripts and outcomes, rather than a framework to assemble.
  • You need to run the whole stack on your own infrastructure or fully air gapped, with support and updates from the vendor.
  • You want people to whisper, join or take over a live AI call from a browser, plus live transfer.
  • You want an SRE agent that opens incidents, writes the root cause analysis and proposes a fix for an engineer to approve.
  • One to one call density per node matters most: in Xebit's benchmark on identical hardware, Xebit held 3.3x the concurrent sessions.

Choose LiveKit if

  • You want open source code under Apache 2.0 that your team can read, fork and run without a licence fee.
  • You need large rooms: in Xebit's own benchmark, LiveKit held 780 participants in a single room to Xebit's 82.
  • You want video, livestreaming and multiparticipant apps as well as voice agents, on one media layer.
  • You want to buy US phone numbers from the same provider that hosts your agents.
  • You want client SDKs for web, mobile and desktop apps from the same open source project.
Side by side

Xebit and LiveKit, feature by feature.

LiveKit is an open source realtime media server written in Go, built around a WebRTC selective forwarding unit, with an open source Agents framework for building voice and multimodal agents in Python and Node. LiveKit Cloud is its managed service, adding hosted agents, phone numbers, model inference and agent observability on usage based plans.
Xebit compared with LiveKit
XebitLiveKit
What it isA voice AI platform: agent SDK, audio bridge, speech pipeline, orchestration, campaigns and observability, run as Xebit VoiceCloud or licensed as Xebit VoiceKit.An open source WebRTC media server and Agents framework, plus LiveKit Cloud as a managed service.
Deployment optionsXebit VoiceCloud, managed by Xebit; or Xebit VoiceKit on Docker or Kubernetes in your data centre, your cloud account or air gapped.LiveKit Cloud, or self hosted as a single binary, on Docker, or on Kubernetes with Helm charts. Agents run on LiveKit Cloud or your own servers.
Runs on your own infrastructureYes, with Xebit VoiceKit: the same platform that runs Xebit VoiceCloud.Yes, the open source server and Agents framework can be self hosted. Agent observability needs LiveKit Cloud media servers.
Air gappedYes, Xebit VoiceKit air gapped: models run locally on GPUs you provide and nothing leaves the network.Not documented.
Open sourceNo. Xebit is proprietary software; Xebit VoiceKit is an annual licence.Yes. Server and Agents are Apache 2.0; the turn detection models use a separate LiveKit model licence.
TelephonyNot provided. You bring your own carrier and numbers over SIP or WebSocket.Sells US local and toll free numbers in LiveKit Cloud, or you bring your own SIP trunk.
Pricing modelXebit VoiceCloud about $0.052 per connected minute, models included, from $258 a month. Xebit VoiceKit is a flat annual licence by band, regardless of volume.Open source self hosting has no licence fee. LiveKit Cloud has a free tier and paid plans billed on agent minutes, participant minutes, bandwidth and telephony.
Published concurrency9,200 concurrent one to one sessions per node in Xebit's benchmark against LiveKit on identical hardware (2,800 for LiveKit). See /benchmark.LiveKit's own benchmark shows one audio room of 10 publishers and 3,000 subscribers on a 16 core instance. Cloud plans list concurrency limits.
Speech pipelineSpeech to speech by default on the Gemini ecosystem, or cascade with the speech components you choose.Cascade speech to text, LLM and text to speech through plugins, or realtime speech to speech models, with its own turn detection model.
People on live callsWhisper, join or take over from a browser through the audio bridge, plus live transfer.Cold transfer over SIP REFER and agent assisted warm transfer are documented, plus handoff between agents.
Observability and incidentsPer call and per node metrics, transcripts, event logs and replay. An SRE agent opens incidents, writes the RCA and proposes a fix an engineer approves.Agent insights in LiveKit Cloud: transcripts, traces, logs and audio per session on one timeline, with OpenTelemetry export. Incident automation not documented.
ProtocolsWebRTC, WebSocket, RTP over SIP and gRPC in production.WebRTC over UDP, TCP or TURN, WebSocket signalling, and SIP over UDP, TCP or TLS.
IntegrationsZoho and Salesforce connector, REST API and webhooks.Server APIs, webhooks, client SDKs for many platforms, model provider plugins and MCP tools for agents.
Compliance statusSOC 2, ISO 27001 and VAPT in progress, none certified.States SOC 2 Type II, GDPR alignment, CCPA and HIPAA BAAs on Scale and Enterprise plans. PCI DSS and ISO 27001 listed as in progress.
Measured, not claimed

The benchmark, including the row we lose.

We ran Xebit and LiveKit on identical hardware across nine measurements and published the method. LiveKit holds far more participants in a single room, because it is built for large rooms; Xebit is built for thousands of separate two party calls.
Xebit against LiveKit (open source), identical hardware
MetricXebitLiveKitDifference
Concurrent one to one sessions per node9,2002,8003.3x
Participants per node, all one to one18,4005,6003.3x
Agent Server sessions, dedicated node10,50018see note
Median join to audio, cold join191 ms247 ms−23%
P95 mouth to ear, two party call118 ms142 ms−17%
SIP call setup, PSTN ingress430 ms580 ms−26%
Reconnect after forced node kill1.3 s2.2 s−41%
Audio MOS at 8% packet loss3.93.6higher is better
Participants in a single room82780we are lower
Methodology and how to reproduce it
What actually differs

The differences that matter in production.

01

Framework or platform

LiveKit gives you the media layer and an agent framework, and your team builds the rest: campaigns, outcomes, CRM updates and the operating model. Xebit ships those parts already built. If you want full control over every line, LiveKit's approach fits; if you want to start from a running platform, Xebit's does.

02

Call density against room size

Xebit ran its benchmark against LiveKit on identical hardware: 9,200 concurrent one to one sessions per node against 2,800, P95 mouth to ear of 118 ms against 142 ms, and SIP call setup of 430 ms against 580 ms. LiveKit held 780 participants in a single room to Xebit's 82. The full method is at /benchmark.

03

Where it can run

Both can run on your own servers. Xebit VoiceKit documents an air gapped configuration where models run locally and nothing leaves the network. LiveKit documents self hosting on VMs and Kubernetes; we found no air gapped guide, and its agent observability requires LiveKit Cloud media servers.

04

Telephony and pricing

LiveKit Cloud can sell you US numbers and bills by usage across several meters, with models billed separately. Xebit never sells telephony: you keep your carrier, and Xebit VoiceCloud's per minute rate includes the models, while Xebit VoiceKit is a flat annual licence that does not change with volume.

05

People and incidents

LiveKit documents cold and warm transfer. Xebit adds browser whisper, join and take over on the same recorded call, and an SRE agent that writes the root cause analysis and waits for an engineer to approve the fix.

Switching

Moving from LiveKit to Xebit.

  1. 01

    Map each LiveKit agent's prompts, tools and handoff logic to a Xebit agent definition, keeping your business rules in the orchestration layer.

  2. 02

    Point your existing SIP trunks at Xebit's SIP gateway, or move numbers bought from LiveKit to a carrier of your choice first.

  3. 03

    Choose speech to speech or a cascade with the same speech components you use today, and bring your own model licences on Xebit VoiceKit.

  4. 04

    Recreate webhooks and CRM writes with Xebit's REST API, webhooks or the Zoho and Salesforce connector.

  5. 05

    Run a pilot list in parallel, compare outcomes and response times on your own numbers, then move traffic over.

Xebit vs LiveKit questions

Why does Xebit benchmark against LiveKit?

LiveKit is a widely used open source framework for realtime voice, so it is a fair reference point. Xebit's own stack has a separate bridge, agent server and SIP gateway, and it is not open source. We ran both on identical hardware and publish the method at /benchmark so you can reproduce it on yours.

How does Xebit compare with LiveKit on performance?

In Xebit's benchmark on identical hardware, Xebit held 9,200 concurrent one to one sessions per node against 2,800 for LiveKit, with lower P95 mouth to ear latency and faster SIP setup. LiveKit held far more participants in a single room, 780 against 82. If your use case is large rooms, that row matters most.

Is LiveKit cheaper because it is open source?

The LiveKit server has no licence fee, but you pay for the servers, the models, telephony and the engineering time to build and run everything around it. Xebit charges per connected minute in Xebit VoiceCloud with models included, or a flat annual Xebit VoiceKit licence. Which costs less depends on volume and on how much you would otherwise build.

Can a person join a live AI call on either?

LiveKit documents cold transfer over SIP REFER and agent assisted warm transfer. Xebit supports live transfer and also lets a person open the call in a browser to whisper to one side, join as a third party, or take over from the agent, with one recording and transcript of the whole call.

Facts about LiveKit come from its own public pages, checked on 22 October 2026: LiveKit server on GitHub, LiveKit Agents on GitHub, LiveKit pricing, LiveKit security and compliance, LiveKit telephony docs, LiveKit self hosting deployment docs, LiveKit benchmark docs, LiveKit agent observability docs. Products change quickly; if something here is out of date, tell us and we will correct it. LiveKit is a trademark of its owner, used here only to identify the product.
DECIDE ON EVIDENCE

Set a pass mark, then test us against it.

Tell us the concurrency, cost ceiling and response time you need. We will run Xebit against them on our cloud or your hardware, so you can compare on your own numbers.