—— Benchmarking Report 2026 ——
Voice AI Platform Performance Analysis
Voice is fundamentally different from chat. In text interfaces, delays of several seconds are often tolerated. In live conversation, they are not.
—— Key Findings ——
Key Findings
Two Architectures, One Pipeline
Application-Layer (LiveKit, Vapi)
A Python async event loop orchestrates the pipeline from outside the media path
Audio goes to an external STT service, text streams to LLM, LLM output streams to an external TTS service, audio routes back to the caller
STT and TTS are separate network services. LLM-to-TTS streaming overlaps, but STT-to-LLM and TTS-to-caller are sequential hops
Barge-in is detected via VAD in the agent process, not at the raw audio level inside the media layer
Endpointing, turn detection, and tool execution all run in the same async loop as the pipeline orchestration
Getting it to work takes a weekend. Getting it to feel like a conversation takes months.
Latency variance comes from coordinating multiple external services, each with its own queue and network path
AI Kernel (SignalWire)
A purpose-built engine orchestrates the pipeline from inside the media processing layer, not from an application-layer script
The AI kernel calls the same external STT, LLM, and TTS services, but from a position with direct access to the audio stream, timing, and call state
The result is not fewer external calls. It is lower variance and faster coordination, because the orchestration layer was built for real-time audio from the start
Provider differences (latency profiles, streaming behavior, error modes) are normalized by the kernel so they perform consistently regardless of which vendor you choose
Barge-in and endpointing are detected at the audio level inside the media engine, before any external service is involved
Platform Comparison
Metric
SignalWire
LiveKit (tuned)
Vapi
Scaling Risk by Platform
Platform
Avg Latency / Spread
Primary Failure Mode at Scale
Human Conversational Thresholds
<2s
Responsive
Slight mechanical feel, but conversation flows naturally.
2-3
Noticeable delay
Callers begin losing confidence in the system.
>3s
Frequent interruption
Users frequently interrupt or assume the system has failed.
>4s
Conversation breakdown
Callers often hang up or request a human.
Operational analytics at scale
The call_timeline feed provides every event from every call in a flat, queryable format. Export to Snowflake, BigQuery, Redshift, or any warehouse for operational analytics at scale.
Try it now
Sigmond Runs on SignalWire
A voice and video AI agent built on the SignalWire SDK, wired to a live knowledge base, able to see what you show him. Build the same thing on voice, phone, WhatsApp, or SIP, or an entire white-label platform with SignalWire as the network underneath.
Trusted by 2,000+ Companies