A conversation crosses systems.
Understand them together.

VoiceGateway is an open-source profiler for LiveKit voice agents. It connects call events, turn timing and infrastructure evidence so you can see what happened along the way.

Cloud is $9 a month for 2,000 profiled call minutes. Cancel any time. Open source and free to self-host.

US EASTThe callerTorontoPhone bridgeTelephony / SIPLiveKit SFUMedia serverAgent workerSTT · LLM · TTSProvider API calls · region variesVoiceGatewayObserves the systemObservations assemble here

VoiceGatewayReceives telemetry outside the audio path

  1. Phone · SIP · G.711
  2. Media server · SFU
  3. Agent worker · STT / LLM / TTS calls
Conversation pathTelemetry to VoiceGateway
Connection
Agent pipeline
Media: US East · Worker: US East

1 of 4

One conversation. Several systems.

SIP connects phone calls; WebRTC connects browsers. LiveKit’s media server (SFU) carries the audio. The agent worker coordinates turns, tools and model API calls.

Did the caller connect? Did the agent join? Did a reply reach playback?

Connection setup and conversation timing are different parts of the call.

Illustrated regions. Co-locating the media server and agent worker avoids a cross-region media hop. The worker calls model APIs; provider inference may run elsewhere.

Start with one response.
Read what was measured.

In this captured turn, the model’s first token is only part of the wait. Select a measurement to understand what it tells you.

One captured turnHello.

Reported response2,665 ms

Compare the reported durationsSelect a measurement

Durations overlap; do not add them.

Has the caller finished?

The agent must decide when to answer. Here, end-of-turn handling is the longest reported duration, even though the model starts generating quickly.

Start by inspecting the turn decision.

Captured October 12, 2026. Caller-network and carrier transit are not measured here. No audio was recorded.

View the source

Then follow the call
across its systems.

Inspect the phone connection, media server, agent and models. Each layer contributes evidence. Missing measurements stay visible as gaps.

Call path
Captured example · vg-capture
Loading call path…

Scroll across to follow the call

2.30 sMedian answer

From the caller stopping to the agent speaking, across 11 measured turns. One of the three captured calls arrived by phone.

One call works.
What about many?

Compare response times and missed joins as calls increase. Check the load generator too: a stressed test runner cannot prove the agent’s limit.

Captured feasibility run. Run the same capacity test against your own agent from the console.

Loading capacity chart…

Your calls.
Your choice.

Keep control with self-hosting.
Get a hosted workspace with Cloud.

Self-hosted

Free

Collect call evidence and inspect it on your infrastructure.

  • Your data stays with you
  • Source you can inspect and contribute to
  • Your team, one view of every call
Get the source

Open-source V1 preview: calls, recordings, issues, alerts and capacity tests, on your servers.

VoiceGateway Cloud

$9 / month

Spend your time improving your agents. Give your team a shared place to understand every call.

  • 2,000 profiled call minutes every month
  • A hosted workspace for your team, invited by email
  • No automatic overage charges
Try now for $9 a month

Billed monthly through Stripe. Cancel any time. Four quick questions, then checkout and your workspace. Need more minutes? Ask about Custom.

Before you dive in.