MikhbarMIKHBAR
Artificial Intelligence

Building Ultra-Low-Latency Voice AI on AWS

Cartesia and AWS are enabling developers to build real-time voice applications using purpose-built State Space Models.

Building Ultra-Low-Latency Voice AI on AWS

The Challenge of Real-Time Voice Latency

Conversational AI continues to transform how humans interact with technology across virtual assistants, real-time translation, and accessibility tools. Yet, delivering a natural voice experience remains a core challenge in AI infrastructure. Users expect human-like responsiveness, and excess latency can disrupt conversational flow and erode trust. To feel truly natural, AI-generated speech must match the temporal window of human turn-taking.

The demand for real-time voice AI spans contact centers, telehealth, gaming, virtual worlds, accessibility tools, and sales platforms. Traditional transformer-based text-to-speech models often struggle with streaming latency because they process entire sequences before producing output, creating a fundamental trade-off between higher quality and higher latency. To explore broader architectural insights, developers can consult resources provided on the Artificial Intelligence.

AWS Marketplace search results listing the Cartesia Sonic 3.6 SageMaker model package
Image related to the report from AWS Machine Learning Blog · Source: AWS Machine Learning Blog

Advantages of State Space Models

To resolve the trade-off between latency and quality, State Space Models (SSMs) offer a fundamentally different approach compared to traditional transformers. While transformers utilize attention mechanisms with quadratic computational growth relative to sequence length, SSMs treat sequences as continuously evolving systems. They process data step by step while carrying a compact internal state forward, making them exceptionally well-suited for real-time streaming audio.

Key advantages of SSMs for audio processing include high-quality long-range dependencies, a constant memory footprint, and native streaming support. Unlike transformers that cache all previous tokens, SSMs maintain a fixed-size hidden state. Their recurrent structure processes input token-by-token to support true streaming without requiring architectural modifications.

The Cartesia Sonic 3.6 SageMaker product listing page in AWS Marketplace
Image related to the report from AWS Machine Learning Blog · Source: AWS Machine Learning Blog

Sonic and Ink Production Models

Cartesia leverages these SSM advantages within its production voice models. Founded by researchers who pioneered SSM advances, the real-time multimodal intelligence company has built solutions optimized for streaming inference at the edge of human perception. More details about their offerings can be found through Cartesia.

Sonic serves as Cartesia's flagship streaming text-to-speech model, delivering ultra-realistic speech synthesis with first audio bytes arriving in approximately 90 milliseconds. It supports over 44 languages and voice cloning from brief audio samples. Meanwhile, Ink handles streaming speech-to-text with native turn detection, context-aware end pointing, and robust noise handling.

SageMaker Create model page using the Sonic 3.6 AWS Marketplace subscription
Image related to the report from AWS Machine Learning Blog · Source: AWS Machine Learning Blog

Deployment Patterns on AWS

Organizations prioritizing data sovereignty, latency control, and compliance can deploy Cartesia models directly into their private cloud environments. Sonic is delivered as an Amazon SageMaker AI model package through AWS Marketplace, ensuring inference data remains secure within a virtual private cloud.

Teams can implement solutions by following the official Cartesia get-started guide or reviewing operational resources such as the Cartesia Voice AI Platform listing in AWS Marketplace. Additional implementation details and community contributions are accessible via the Cartesia GitHub repository.

SageMaker endpoint for the Cartesia Sonic 3.6 model showing InService status
Image related to the report from AWS Machine Learning Blog · Source: AWS Machine Learning Blog

Sources

Continue chronologically

Related entity coverage