Concurrency

Concurrency is the number of avatar sessions or conversations a system can run at the same time, including media streams, agent loops, speech services, and backend resources without slowing the experience for users.

How concurrency works

Concurrency describes how many live avatar sessions can run at the same time. It is not just a traffic number; every session may involve audio capture, video streaming, speech recognition, an LLM or agent workflow, text-to-speech, rendering, and networking.

In a real-time avatar system, concurrency matters because quality has to hold when many users arrive at once. A system that feels fast in a single demo can still struggle if simultaneous sessions compete for the same compute or speech services.

A concrete example: a customer service team launches an avatar on a help page and 200 users open sessions during a product outage. Concurrency planning decides whether those conversations stay responsive.

Good concurrency design covers autoscaling, queueing, session limits, monitoring, and graceful fallback. The goal is to keep each user experience live even when total demand rises.

What Anam ships

Anam's Cara-4 model delivers expressive real-time avatars with around 150 ms server-side avatar-generation latency once a session is running, across 70+ languages. Builders use JavaScript and Python SDKs or integrations for LiveKit, Pipecat, ElevenLabs Agents, Agora, and VideoSDK. Bring any AI stack including OpenAI, Claude, Gemini, Mistral, Groq, Deepgram, Cartesia, or custom providers. The platform supports WebRTC delivery, SOC 2 Type II, HIPAA, zero data retention, and regional data residency. Sessions stream low-latency audio and video to browsers and native apps.

Explore the real-time avatar API →

Related terms

WebRTC

WebRTC is the browser standard for low-latency live audio and video streaming, commonly used to carry microphone input and avatar output during real-time interactive sessions.

Streaming inference

Streaming inference is the practice of producing model output incrementally as it is generated, so an avatar can start responding sooner instead of waiting for a full answer to finish.

Sub-second latency

Sub-second latency is the end-to-end response time under one second between a user speaking and an avatar replying, covering speech recognition, model reasoning, speech synthesis, animation, and network streaming.

Avatar API

An avatar API is a developer interface for creating, configuring, and streaming interactive digital characters inside an application, so products can start live avatar sessions, pass user input to an agent, and return spoken video responses in real time.

Frequently asked questions

What does concurrency mean for avatar APIs?

Concurrency is the number of live avatar sessions the platform can handle at once while keeping media, speech, agent reasoning, and streaming responsive for every user.

Why does concurrency matter for real-time avatars?

Each avatar session consumes real-time resources. If concurrency is not planned well, response time, video quality, connection stability, or agent performance can degrade during busy periods.

Is concurrency the same as total monthly usage?

No. Monthly usage measures volume over time. Concurrency measures how many sessions are active at the same moment, which is what drives peak infrastructure demand.

What should teams ask about avatar concurrency?

Ask about session limits, autoscaling, regional capacity, burst handling, queueing, monitoring, and what happens when traffic exceeds the expected number of simultaneous users.

Last updated: 17th July 2026 · Reviewed quarterly.

← Back to glossary

Try the real-time avatar API trusted by 8,000 builders

Read the docs

HIPAA & SOC 2 Certified