OpenAI explains how it runs low-latency voice AI with WebRTC

Start here

In everyday words

WebRTC calls use encrypted audio plus connectivity checks. OpenAI routes packets through a thin relay that reads an ICE identifier, then forwards each session to the right transceiver process.

Need a meaning?

Quick Sip

What you need to know

Who is affected: developers, operators, product teams
What changed: On May 4, 2026, OpenAI described how it re-architected its WebRTC stack for voice AI, splitting packet forwarding (“relay”) from session termination (“transceiver”).
Why it matters: Voice assistants feel natural only when latency and jitter stay low. This design is a practical blueprint for scaling real-time media without opening thousands of public UDP ports.
What to watch next: Watch whether relay patterns like this become common for real-time AI APIs, and how they affect reliability for mobile networks and multi-region deployments.

Four useful details

A lightweight UDP relay forwards packets while the transceiver owns ICE/DTLS/SRTP state.
Routing uses the ICE username fragment (ufrag) so even the first packet can be steered deterministically.
The approach keeps a small public UDP surface while letting pods scale in Kubernetes.

OpenAI · Official AnnouncementOffering Zero Data Retention for frontier models

Adds source-backed context on ai safety from OpenAI.