September 2026 Summaries

LiveKit’s non-production deployments allow voice-agent teams to run the same container image, project, and shared secrets as production under separate named environments, reducing the need to maintain duplicate agents while enabling testing of models, prompts, and integrations on real infrastructure. These deployments can be created and managed through the CLI using a `--deployment` flag, sleep when idle to avoid compute costs, and can be targeted for calls through tokens or dispatch APIs, although they require recent Python or Node SDK versions. Unlike production, non-production deployments cold-start on demand, immediately terminate active sessions during redeployment, and do not support rollback, making them appropriate for iterative testing rather than interrupt-sensitive traffic. Deployment-specific behavior or credentials can be selected at runtime through the `LIVEKIT_AGENT_DEPLOYMENT` environment variable, while CI workflows can route branches to staging or production and optionally require approval before production releases. The feature is available on Ship and higher plans, with limits of two non-production deployments per agent on Ship and five on Scale; logs can be used for inspection, while deployment-specific observability metrics are planned for the future.

LiveKit has launched Connectors on LiveKit Cloud, enabling AI agents to handle calls directly through Twilio Programmable Voice and WhatsApp Business Calling without requiring SIP trunks, gateways, or redesigned telephony systems. Each call enters a LiveKit room as a connector participant, allowing agents to use existing capabilities such as turn detection, noise cancellation, observability, DTMF handling, and session analytics while retaining platform-specific context like Twilio call IDs or WhatsApp caller metadata. WhatsApp calls use native WebRTC without transcoding, while Twilio Media Streams audio is bridged from WebSockets, and processing follows regional settings. The service is designed for organizations that want to preserve Twilio workflows, phone numbers, call routing, and compliance arrangements, or serve WhatsApp-first markets through a unified agent platform. Connectors support agent dispatch at connection time, avoid connecting callers to silence, use customers’ own platform accounts and numbers, and do not store credentials or record media. LiveKit positions SIP as its preferred option for new Twilio deployments because of broader routing and latency advantages, while Connectors offer a simpler integration path for established Twilio and WhatsApp systems; pricing matches SIP usage, and additional platform integrations are planned.