#181 — How Gradium is beating Big Tech at audio AI
March 1, 2026·10 min read

Contents
Why it matters: While OpenAI and Google dominate text models, scrappy startups are winning the race for voice AI—and it signals where innovation happens when compute becomes democratized.
The big picture: Gradium, born from non-profit lab Kyutai, shipped the first full-duplex conversational AI with just 4 researchers in 6 months—before OpenAI's Advanced Voice Mode and a year before xAI's demo.
By the numbers:
- Moshi (Kyutai's model): 7B parameters, 2.1T tokens, 160ms latency
- Llama 3.1: 405B parameters, 15T tokens—orders of magnitude more expensive
- Training cost differential: 50x+ cheaper than frontier text models
- Team size: 4 researchers vs. hundreds at major labs
The neglect thesis: Why audio was ripe for disruption
Management considered it "solved": When Neil Zeghidour joined Google Brain in 2019, leadership viewed voice as a finished problem—resources poured into text and vision instead.
The cultural hierarchy: Pre-GPT, audio occupied the bottom tier of ML's coolness hierarchy—CNNs for images topped the list, then tabular data, then text, with audio dead last. Meta's Seamless and Google's speech repos shipped models, published papers, then went dark for years.
The data scarcity myth: Unlike text models requiring massive internet scrapes, audio models train on far less data—Moshi used 7M hours vs. trillions of text tokens. Stack Overflow teaches you something; most phone conversations are filler. This made focused expertise more valuable than raw compute.
The Siri effect: Neural networks crushed images and eventually text, but very few believed audio could achieve realtime conversations with proper turn-taking. Siri's laughably bad voice assistant may have caused the industry to internalize defeat.
The hierarchy flip: Why research engineers won
Pre-deep learning era: Research scientists (the "idea guys" with prestigious academic backgrounds) had higher prestige and better comp than research engineers who implemented ideas in code.
Deep learning inverted everything: Ideas became cheap because neural nets are universal approximators and essentially very dumb. Research became "what can we throw Deep Learning at" while hard problems moved down the stack—training efficiently, managing distributed systems.
The new winning profile: Researchers who thrived—like Noam Shazeer at Google—could both conceive architectural insights AND implement them. As Neil put it: "The biggest scam in big companies is thinking that you can lead a research organization without doing research yourself, just by being an 'idea guy'".
The startup moment for AI: Small teams of research engineers could outclass larger, better-funded competitors without massive compute budgets and teams—getting GPUs in the cloud was now a few clicks.
The Kyutai origin story
The Paris audio mafia: All four Gradium cofounders (Neil Zeghidour, Alex Défossez, Olivier Teboul, Laurent Mazaré) worked at big labs in their underfunded audio divisions. Alex was working on mathematical optimization but DJing on the side—they built an AI synthesizer for fun.
The accidental invention: Neil's first project at Google Brain was building the first neural audio codec, SoundStream. After training the first model that could generate audio by predicting compressed tokens, he passed three seconds of his voice to the model—it kept talking in his voice. They had accidentally invented voice cloning.
The Gemini foundation: Every audio project at Google Brain started using this framework, which became the foundation for Gemini Live.
Kyutai launch (2023): Named for the Japanese word for "sphere," Kyutai became the first and only open audio lab—funded by Eric Schmidt and two French billionaires. Neil and cofounders built it because competitive pressure between labs meant fewer papers were being published.
Major releases:
- Moshi: First realtime voice model, can run on mobile
- Hibiki: Simultaneous speech-to-speech translation in the speaker's voice
- Open source TTS/STT models: Foundation for NVIDIA's PersonaPlex and Qwen3-TTS
- Real-time translation: Running on-device months before Apple's
The productionization play: Kyutai builds research prototypes; Gradium raised $70M to bridge the last mile from research to production-ready models. You can think of it as a pipeline: fundamental Kyutai research → production-grade products via Gradium.
Audio training vs. text: The key differences
Architecture similarities: Most SOTA audio models use Transformer-based architectures—benefiting from all LLM advances (RLHF, distillation, hardware optimizations).
The data problem: No massive treasure trove like the internet corpus for text. What "audio data" even means is a moving target—labeled transcribed conversations? Translations of a single speaker? Multi-participant conversations? Compare typical datasets (Voxpopuli, MADLAD-400, NTREX) to text and the fragmentation is stark.
Model size differential: Moshi has 7B parameters trained on 2.1T tokens—audio models know far less ground information than typical LLMs.
Moshi training pipeline:
- Pretrained on 7M hours of audio with transcripts
- Post-trained on Fisher dataset (2000 hours of phone conversations with separated channels)
- Instruction finetuned on 20k+ hours of synthetic dialogue
Evaluation hell: Good conversations are completely subjective. The team gave up on quantitative measures entirely—only trusted humans, doing tons of blind tests and just listening (supplemented with freelancers). This problem is well-documented in music generation.
The turn-taking problem: Full-duplex vs. turn-based
The hardest challenge in audio AI: How do you trade conversation with an unpredictable user? When is the user done talking vs. thinking? How do you handle interruptions? Should the model ever interrupt, and if so when?
Turn-based models (OpenAI's approach): Train the model to predict when the user is finished talking. Creates weird dynamics—if you're silent for a few seconds thinking, the model talks even though you didn't want it to. Cannot interrupt you (though sometimes it should), and until recently, impossible to interrupt the model. Like talking on a walkie talkie.
Full-duplex models (Kyutai's breakthrough): Like being on the phone—a real conversation where both sides interact dynamically, interrupt each other, and interpret intent intelligently. Proficient at backchanneling ("aha, yes, I see, mhm") making conversations more lively and natural.
The technical breakthroughs
Multi-stream modeling
The simple idea that solved everything: Instead of modeling one audio stream (the user's), model TWO—one for user, one for machine. When the machine isn't speaking, it produces silence or backchanneling. Both can be active simultaneously (or one active, one inactive) unlike turn-based architectures.
Impact: This extremely simple architectural idea mostly solved turn-taking, arguably the most challenging problem in dialogue/audio AI.
Extension to translation: Hibiki uses the same architecture for realtime translation into another language using the speaker's exact voice. Bidirectional audio with multilinguality is incredibly difficult—where do you find data of the same person in the same voice saying the same thing in multiple languages? Gradium's approach is called DSM (Delayed Streams Modeling).
The Mimi codec: Combining semantic and acoustic tokens
Background on codecs: Codec = encoder-decoder, how you compress audio data into something a model can use (like embeddings for audio). Traditional codecs are domain-specific—speech codecs for speech, music codecs for music—with very manual, bespoke rules. You can't swap them, and they output completely different bitrates.
SoundStream (the Google Brain breakthrough): Neil trained a model to do compression—a neural codec that compresses speech, music, and general audio at bitrates normally targeted by speech-only codecs. Worked just as well as domain-specific codecs with ergonomic benefits.
The two token types:
- Semantic tokens: Content of what's being said (words and meaning)
- Acoustic tokens: Acoustic style (how the voice sounds, emotion)
The old hierarchical approach: Previous work modeled these separately, starting with semantic (content) then moving to acoustic (style). Problem: Prevailing open models for semantic tokens are non-causal (like WavLM) and absolutely do not work in realtime—they need future audio to compute current embeddings.
Kyutai's solution: Combine both token types into a single generation process via fancy vector quantization summing. When Moshi generates speech, it produces 8 tokens per timestep: token 1 is semantic, tokens 2-7 are acoustic. The whole causal system processes audio as it arrives, generating all tokens in real-time.
The depth factor: Reading Kyutai papers, you get a frenetic sense of depth. Most Arxiv papers have 1-3 fundamental ideas enabling the new architecture—Kyutai papers have like 13. For Moshi, this summary skips innovations in generation (Temporal+Depth transformers), differing weights on token loss, their Inner Monologue method.
Result: Theoretical latency of 160ms, lower than typical human conversation (200-250ms). Moshi is in some senses even too fast.
The founder playbook: Why small teams win at audio
1. Economics favor focused execution
Audio models are 50x+ cheaper to train than frontier text models. You don't need thousands of people or massive compute clusters—you need a few exceptional people who understand the domain deeply.
Concrete example: Moshi (7B parameters, 2.1T tokens) vs. Llama 3.1 (405B parameters, 15T tokens)—orders of magnitude difference in cost.
2. Domain expertise compounds in ways scale cannot replicate
Text vs. audio tokenization: A text tokenizer is essentially a dictionary—break words into subword tokens and you're done. An audio codec like Mimi relies on deep understanding of human hearing, acoustic psychophysics, how to balance compression against perceptual quality. "The bitter lesson is like…not so bitter here".
The multimodal trap: Training a multimodal model means constant compromise—more coding data means less audio data. Voice is always negotiating with text, video, and image teams for model capacity and training budget. At a focused lab, there's no compromise—everything optimizes for audio.
3. Architectural innovation still beats brute force
The opportunity in audio AI: "Very few people just need to focus on the right questions".
Examples:
- Full-duplex architecture: Simple idea (model both streams simultaneously) that solved years-old turn-taking problems
- Mimi codec: Novel compression technique for combining semantic and acoustic tokens vs. brute force
4. The recruiting heuristic for founders
Kyutai's simple candidate assessment: "If you put them in a data center with a gun to their head and no internet, can they implement their stuff from scratch?"
Look for research engineers who can both conceive architectural insights AND implement them—not idea guys who need implementation teams.
5. Open research as competitive advantage
Kyutai exists because competitive pressure between labs meant fewer papers were being published. By going open, they attracted top talent who believed in open research and could move faster without corporate politics.
Their open models became foundations for others: NVIDIA's PersonaPlex, Qwen3-TTS, running on-device before Apple.
6. The research-to-product pipeline
Research prototypes ≠ production-ready products. Real apps need much more polished models.
The Gradium model: Kyutai handles fundamental research → Gradium bridges the last mile with $70M to build production-grade products. In a few short months, they shipped multilingual models competing with best in class.
Tactical takeaways for founders
Market timing signals:
- Big labs treating your space as "solved" is an opportunity, not a barrier
- Look for domains where management says "we're done here" while underfunded divisions quietly cook
- Cultural hierarchy matters—audio was "uncool" for years, creating whitespace
Organizational dynamics:
- Small teams of research engineers can outclass larger competitors when they move fast, build their own ideas, and avoid big lab politics
- The "idea guy" era is over—deep learning made ideas cheap and implementation hard
- Look for the researcher who accidentally invents voice cloning while testing compression
Data strategy:
- Data scarcity isn't always a moat for incumbents—it can favor focused expertise over scale
- When evaluation is subjective, trust humans over metrics
- Synthetic data generation (20k+ hours of synthetic dialogue for Moshi) can overcome data scarcity
When to go open:
- Closed research is slowing at big labs due to competitive pressure
- Open models can become foundational infrastructure for larger players
- Attracts talent who values transparency and speed over corporate bureaucracy
The production gap is real:
- Research prototypes from non-profits/academia need 70M+ to productionize
- Building a pipeline from fundamental research to production is a viable company-building strategy
Access the models: Chat with Gradium's production models at gradium.ai and review API documentation to see how they've bridged research to product.
Frequently asked questions
How much does it cost to train a competitive audio AI model compared to a text LLM?
Audio models are 50x+ cheaper to train than frontier text models. Moshi (Kyutai's full-duplex audio model) used 7B parameters and 2.1T tokens, while Llama 3.1 required 405B parameters and 15T tokens—orders of magnitude more expensive. A small team of 4 researchers built Moshi from scratch in 6 months with limited non-profit funding, demonstrating that audio AI doesn't require massive compute clusters or thousand-person teams.
What is full-duplex audio AI and why does it matter for product development?
Full-duplex audio AI (like Kyutai's Moshi) models conversations as two simultaneous audio streams—user and machine—enabling natural interruptions, backchanneling ('uh-huh', 'I see'), and 160ms response latency (faster than human conversation at 200-250ms). This contrasts with turn-based models (like OpenAI's early Advanced Voice Mode) that can't handle simultaneous speech and create awkward pauses. For founders, full-duplex enables natural voice interfaces for customer service, therapy apps, language learning, and collaborative tools where conversation flow matters.
How do I hire research engineers who can actually build audio AI, not just theorize?
Kyutai uses a simple assessment: 'If you put them in a data center with a gun to their head and no internet, can they implement their stuff from scratch?' Look for researchers who can both conceive architectural insights AND implement them—not 'idea guys' who need implementation teams. The AI research hierarchy inverted with deep learning: ideas became cheap while implementation became hard. Neil Zeghidour, Alex Défossez, Olivier Teboul, and Laurent Mazaré (Gradium's founding team) all came from underfunded audio divisions at Google Brain, Meta, and Facebook AI Research where they shipped production code, not just papers.
What size audio dataset do I actually need to build a production-ready voice model?
Significantly less than text models. Moshi was pretrained on 7M hours of audio with transcripts, post-trained on 2,000 hours (Fisher dataset), and instruction-finetuned on 20k+ hours of synthetic dialogue. Compare this to text LLMs trained on trillions of tokens scraped from the entire internet. The key difference: a Stack Overflow answer teaches you something; most phone conversations are filler. Kyutai demonstrated that focused, high-quality conversational data plus synthetic dialogue generation can overcome audio data scarcity without massive scraping infrastructure.
Should I use OpenAI's Advanced Voice Mode or build with Gradium's API?
Depends on your latency and customization needs. Gradium offers 160ms theoretical latency with full-duplex architecture (simultaneous speech, natural interruptions), multilingual support, and the ability to fine-tune on your domain. OpenAI's turn-based model can't handle simultaneous speech and historically couldn't be interrupted until recent updates. If you're building conversational AI where natural dialogue flow matters (therapy, language learning, customer service), full-duplex architecture is critical. Gradium also offers production-ready APIs at gradium.ai versus consumer-focused ChatGPT integration.
Why are small teams beating Big Tech at audio AI when they lose at text models?
Three structural reasons: (1) Big labs considered audio 'solved'—when Neil Zeghidour joined Google Brain in 2019, management treated voice as finished while pouring resources into text/vision. Meta's Seamless and Google's speech repos haven't been updated in years. (2) Audio requires deep domain expertise over brute compute—an audio codec needs understanding of acoustic psychophysics and human hearing, not just scaling. A text tokenizer is basically a dictionary; Kyutai's Mimi codec is applied physics. (3) Multimodal tradeoffs—at big labs, voice teams negotiate with text, vision, and code teams for model capacity. Dedicated focus wins.
What technical breakthroughs made real-time conversational AI possible in 2024?
Two key innovations from Kyutai: (1) Multi-stream modeling—instead of modeling one audio stream (the user), model two simultaneously (user + machine). When the machine isn't speaking, it produces silence or backchanneling. This simple architectural shift solved the turn-taking problem that stumped researchers for years. (2) Mimi codec—combines semantic tokens (content/words) and acoustic tokens (voice style/emotion) into a single real-time generation process. Previous approaches used non-causal models like WavLM that needed future audio to process current embeddings, making real-time impossible. Moshi generates 8 tokens per timestep: 1 semantic, 7 acoustic.
How do you evaluate audio AI quality when conversations are completely subjective?
Kyutai completely gave up on quantitative measures and only trusted humans doing blind tests and extensive listening sessions supplemented with freelancers. This evaluation problem is well-documented in music generation—good conversations are subjective and can't be reduced to metrics like BLEU scores or perplexity. For founders building audio products, this means: (1) Budget significant time for human evaluation, (2) Use blind A/B testing with real users, (3) Don't trust automated metrics alone, (4) Accept that 'better' is contextual to your specific use case (customer service needs different qualities than therapy or entertainment).
What's the go-to-market strategy for an audio AI startup competing with OpenAI?
The research-to-product pipeline model: Kyutai (non-profit) handles fundamental research and ships open-source prototypes (Moshi, Hibiki) that become foundational for others (NVIDIA's PersonaPlex, Qwen3-TTS). Gradium raised $70M to bridge the last mile from research prototypes to production-ready models with API access. This approach works because: (1) Open research attracts top talent who value transparency, (2) Research prototypes prove technical feasibility without production polish, (3) Big labs are distracted by multimodal tradeoffs—voice negotiates with text/vision/code teams for resources. In months, Gradium shipped multilingual models competing with best-in-class by focusing exclusively on audio.
When should a founder choose audio-first vs. text-first for their AI product?
Choose audio-first when: (1) Hands-free or eyes-free interaction is critical (driving, cooking, accessibility), (2) Emotional context and tone matter (therapy, customer service, language learning), (3) Real-time collaboration requires natural turn-taking (virtual assistants, meeting facilitation), (4) Your users have literacy barriers or prefer speaking to typing. Many researchers believe audio will become the dominant AI modality—every sci-fi AI (HAL 9000, Jarvis, Her) speaks naturally. The technology finally caught up in 2024 when Kyutai shipped the first full-duplex model before OpenAI's Advanced Voice Mode and a year before xAI's demo.
What are the actual use cases where Gradium's models are being deployed in production?
While Gradium is early-stage (founded from Kyutai in 2024, raised $70M), their technology enables: (1) Multilingual customer service with real-time translation in the speaker's voice (Hibiki demo), (2) Voice assistants with natural interruptions for hands-free workflows, (3) Real-time speech-to-speech translation running on-device (shipped months before Apple's), (4) Text-to-speech and speech-to-text APIs that became foundations for NVIDIA's PersonaPlex and Qwen3-TTS. Founders can access production-ready models at gradium.ai and review API documentation to integrate full-duplex conversational AI without building codec and turn-taking infrastructure from scratch.
How much funding do I realistically need to build a competitive audio AI startup?
Kyutai built Moshi (the first full-duplex conversational AI) with 4 researchers in 6 months on a non-profit budget orders of magnitude smaller than big labs—demonstrating that focused execution beats massive budgets. Gradium then raised $70M to productionize Kyutai's research into API-ready models, suggesting you need: (1) Small exceptional team for R&D phase (under $5M seed/Series A), (2) Larger round ($50-100M) to bridge research-to-production gap with polished models, API infrastructure, and enterprise sales. This is 50x+ cheaper than frontier text model development because audio models are dramatically smaller (7B vs. 405B parameters) and require less training data.
What is Kyutai and how does it differ from OpenAI or Anthropic?
Kyutai is the first and only open audio research lab, named for the Japanese word for 'sphere,' founded in 2023 with funding from Eric Schmidt and two French billionaires. Unlike OpenAI (closed models, text-focused) or Anthropic (safety-focused, multimodal), Kyutai exclusively researches audio AI and publishes all findings open-source. Their major releases include Moshi (first full-duplex voice model) and Hibiki (real-time voice translation). The lab was created because competitive pressure between big labs meant fewer papers were being published. Kyutai builds research prototypes; their commercial spinout Gradium ($70M raised) productionizes them into APIs.
What is a neural audio codec and why does it matter for voice AI?
A neural audio codec is an AI-powered encoder-decoder that compresses audio into tokens a model can process—like embeddings for audio. Traditional codecs (MP3, AAC) use manual, domain-specific rules: speech codecs for speech, music codecs for music, incompatible with each other. SoundStream (Neil Zeghidour's breakthrough at Google Brain) trained a neural network to compress speech, music, and general audio at speech-codec bitrates, working as well as domain-specific codecs. Kyutai's Mimi codec advanced this by combining semantic tokens (content/words) and acoustic tokens (voice style/emotion) into single real-time generation, enabling 160ms latency. Without neural codecs, real-time conversational AI wouldn't be possible.
What are semantic tokens vs acoustic tokens in audio AI models?
Semantic tokens represent the content of speech—the words and their meaning. Acoustic tokens represent the style—how the voice sounds, emotion, prosody, speaker characteristics. Previous audio models (like AudioLM) used hierarchical approaches: generate semantic tokens first (content), then acoustic tokens (style) separately. Problem: prevailing semantic token models (WavLM) are non-causal and need future audio to compute current embeddings—impossible for real-time. Kyutai's Mimi codec combines both into single generation via vector quantization: when Moshi speaks, it produces 8 tokens per timestep (1 semantic, 7 acoustic) causally in real-time. This architecture enables voice cloning, emotion, and natural prosody at 160ms latency.
How does backchanneling work in full-duplex voice AI and why is it important?
Backchanneling is verbal feedback ('uh-huh', 'yes', 'I see', 'mhm') listeners provide during conversations to signal understanding, agreement, or engagement. Full-duplex models like Moshi produce backchanneling naturally because they model two simultaneous audio streams—when the machine isn't speaking full sentences, it can produce backchannels while you talk. Turn-based models (OpenAI's early Advanced Voice Mode) can't backchannel because only one party can speak at a time. Research shows backchanneling makes conversations feel more lively, natural, and engaging—critical for therapy apps, language learning, customer service, and any use case where rapport matters. Japanese conversation norms rely heavily on backchanneling, making it essential for multilingual products.
What is the Fisher dataset and why is it used for training conversational AI?
The Fisher dataset contains 2,000 hours of English phone conversations with separated audio channels for each speaker—making it ideal for training full-duplex conversational models. Unlike most audio datasets that mix speakers into one channel, Fisher's separated streams let researchers model how two people actually converse simultaneously with interruptions, backchanneling, and overlapping speech. Kyutai used Fisher for Moshi's post-training after pre-training on 7M hours of general audio. For founders: Fisher is publicly available through the Linguistic Data Consortium (LDC), but you'll need similar separated-channel conversational data to train full-duplex models for your specific domain.
Can voice AI models run on mobile devices or do they require cloud infrastructure?
Kyutai's Moshi can run entirely on mobile devices, demonstrating that real-time conversational AI doesn't always require cloud infrastructure. At 7B parameters, Moshi is dramatically smaller than multimodal models (Llama 3.1: 405B parameters), making on-device deployment feasible with modern smartphone chips. Kyutai's real-time speech-to-speech translation shipped on-device months before Apple's. On-device audio AI benefits: (1) No latency from network calls, (2) Privacy—no data leaves the device, (3) Works offline, (4) No per-request API costs. Trade-offs: On-device models have less world knowledge and require optimization for mobile inference. For many voice interface use cases (voice assistants, translation, transcription), on-device is preferable.
What is turn-taking in conversational AI and why is it so hard to solve?
Turn-taking is how conversation partners decide when to speak, pause, or interrupt—considered one of the hardest problems in audio AI. Challenges: (1) When is the user done talking vs. just thinking? (2) How do you handle interruptions naturally? (3) Should the AI ever interrupt, and when? (4) How do you distinguish meaningful silence from conversation completion? Turn-based models (OpenAI's approach) predict when users finish talking—but if you pause thinking, the model talks anyway. You can't interrupt it easily. Full-duplex models (Kyutai's architecture) solve this by modeling two simultaneous streams, letting both parties interrupt naturally like phone conversations. This architectural shift mostly solved turn-taking, enabling natural dialogue for customer service, therapy, and collaborative applications.
How does synthetic dialogue generation work for training audio AI models?
Kyutai instruction-finetuned Moshi on 20k+ hours of synthetic dialogue—AI-generated conversations used to supplement scarce real conversational data. Process typically involves: (1) Generate conversation scripts using text LLMs with prompts for realistic dialogue scenarios, (2) Convert scripts to audio using text-to-speech with varied voices, emotions, and speaking styles, (3) Add realistic acoustic properties (room acoustics, background noise, cross-talk), (4) Fine-tune the audio model on synthetic conversations. Benefits: Overcome audio data scarcity, control for specific conversational patterns (interruptions, backchanneling, turn-taking), create domain-specific dialogues (medical consultations, customer service), avoid privacy issues with real conversations. For founders: Synthetic generation is cost-effective for specialized domains where real conversational data doesn't exist at scale.
What are causal vs non-causal models in audio AI and why does it matter?
Causal models process data sequentially—they only use past and present information to make predictions, enabling real-time processing as audio arrives. Non-causal models use future information to compute current outputs—they must see the entire audio sequence before processing, making real-time impossible. Problem: prevailing open models for semantic tokens (like WavLM) are non-causal—they need future audio to compute current embeddings. Kyutai's breakthrough was making the entire Moshi architecture causal by combining semantic and acoustic token generation into one real-time process via Mimi codec. For founders building real-time voice interfaces: causal architectures are mandatory for conversational AI, voice assistants, live translation, or anything requiring immediate response.
How do audio transformers differ from language model transformers like GPT?
Audio transformers are architecturally similar to text transformers (both use attention mechanisms, similar layer structures) but differ in input representations and optimization targets. Key differences: (1) Input tokens—audio uses compressed acoustic tokens from neural codecs (Mimi generates 8 tokens per timestep), text uses subword tokens from tokenizers. (2) Sequence length—audio requires many more tokens per second (Moshi: 12.5 Hz frame rate) than text, making efficiency critical. (3) Evaluation—text has clear metrics (perplexity, accuracy), audio is subjective requiring human evaluation. Benefits of similarity: audio models inherit LLM advances (RLHF, distillation, hardware optimizations). Kyutai's Moshi uses Temporal+Depth transformers, adding architectural innovations beyond standard transformers.
What is the Mimi codec and how does it enable real-time voice generation?
Mimi is Kyutai's state-of-the-art neural audio codec that enables real-time voice generation by combining semantic tokens (content) and acoustic tokens (style) into a single causal generation process. Built on Neil Zeghidour's earlier SoundStream work at Google Brain, Mimi uses vector quantization summing to produce 8 tokens per timestep: 1 semantic (what's being said), 7 acoustic (how it sounds). Previous approaches modeled these separately and hierarchically, requiring non-causal models that couldn't process real-time. Mimi's innovation: everything is causal—the codec processes audio as it arrives, generating all tokens simultaneously with 160ms latency. This architectural breakthrough enabled Moshi's full-duplex conversations. For founders: Mimi is open-source and can be adapted for custom voice AI applications.
How does Kyutai's Hibiki real-time translation work and what makes it different?
Hibiki translates speech into another language in real-time using the speaker's original voice—not a synthetic voice. Unlike traditional translation (speech→text→translate→new voice), Hibiki uses speech-to-speech translation with full-duplex architecture, preserving prosody, emotion, and speaker characteristics across languages. Technical approach: DSM (Delayed Streams Modeling) extends Kyutai's multi-stream architecture for bidirectional audio translation. Challenge: where do you find data of the same person in the same voice saying the same thing in multiple languages? Kyutai's solution uses architectural innovations and training techniques to transfer voice characteristics across languages. Hibiki ran on-device months before Apple's real-time translation. Use cases: International calls, multilingual customer service, global meetings, language learning.
What is SoundStream and why was it important for audio AI development?
SoundStream (2021) was the first neural audio codec, created by Neil Zeghidour at Google Brain, that could compress speech, music, and general audio at bitrates normally targeted by speech-only codecs. Before SoundStream, audio codecs were domain-specific with manual rules: speech codecs for speech (Opus, AMR), music codecs for music (MP3, AAC)—incompatible and requiring different engineering. SoundStream trained an encoder-decoder neural network to learn compression end-to-end, working as well as domain-specific codecs with ergonomic benefits. Impact: (1) Unified approach for all audio types, (2) Enabled neural audio generation by providing trainable compression, (3) Led to voice cloning discovery when Neil tested generation, (4) Became foundation for Gemini Live. SoundStream evolved into Kyutai's Mimi codec, enabling real-time conversational AI.
What is AudioLM and how did it contribute to modern voice AI?
AudioLM (Google research by Olivier Teboul and Neil Zeghidour) introduced the concept of separating audio into semantic tokens (content/words) and acoustic tokens (voice style/emotion), using hierarchical generation: first semantic, then acoustic. This architecture enabled high-quality audio generation with controllable voice characteristics—a major advancement for voice cloning and synthesis. Problem: AudioLM's hierarchical approach required non-causal models for semantic tokens (like WavLM) that need future audio to compute current embeddings—making real-time impossible. Kyutai's contribution: Mimi codec combines both token types into single causal generation, solving the real-time problem. AudioLM's semantic/acoustic separation insight remains foundational—nearly all modern voice AI uses this concept, including Gradium's production models.
How do I build a voice AI product without a PhD in audio research?
Use production-ready APIs from specialized audio AI companies rather than building from scratch. Gradium offers full-duplex conversational AI APIs with 160ms latency, multilingual support, and natural turn-taking—no need to build codecs, implement multi-stream architectures, or solve turn-taking yourself. Alternative approaches: (1) OpenAI's Advanced Voice Mode (turn-based, consumer-focused), (2) Open-source models—Kyutai's Moshi is open-source but requires productionization work, (3) Specialized APIs—Deepgram (transcription), ElevenLabs (TTS), AssemblyAI (STT) for component-based architectures. For founders: Start with APIs to validate product-market fit, consider custom models only when differentiation requires it. The $70M Gradium raised to productionize Kyutai's research shows the research-to-product gap is real.
Why is audio considered the future dominant modality for AI interfaces?
Many AI researchers believe audio will dominate because: (1) Every sci-fi AI speaks naturally—HAL 9000, Jarvis, Samantha in Her—suggesting cultural intuition that voice is the ultimate interface. (2) Hands-free, eyes-free interaction is superior for most contexts (driving, cooking, walking, accessibility). (3) Natural for humans—we've evolved to communicate verbally for hundreds of thousands of years; reading/writing is only ~5,000 years old. (4) Emotional context—tone, prosody, and emotion are inherent to audio, making it superior for customer service, therapy, and social applications. (5) Lower barrier—speaking requires no literacy, typing skills, or screen access. Technology finally caught up in 2024 when Kyutai shipped full-duplex conversational AI with natural turn-taking, making this vision practically feasible.
What are the technical requirements to run Moshi or similar full-duplex models?
Moshi's 7B parameters make it deployable on modern GPUs, edge devices, and even mobile phones—dramatically more accessible than massive multimodal models (Llama 3.1: 405B parameters). Minimum requirements for inference: (1) GPU memory: ~14GB for FP16, ~7GB for INT8 quantization, (2) Compute: Modern GPU (NVIDIA RTX 3090/4090, A100, H100) or Apple Silicon (M1/M2/M3 with sufficient RAM), (3) Mobile: Flagship smartphones with neural accelerators (iPhone 12+, high-end Android). For training from scratch: (1) Compute cluster for pre-training (though 50x+ cheaper than text models), (2) 7M hours audio + transcripts, (3) Post-training on 2k-20k hours conversational data. For founders: Inference is accessible; training from scratch requires expertise but fine-tuning Moshi on domain data is feasible.
What is Amplify Partners' thesis on investing in audio AI startups?
Amplify Partners invested in Gradium (disclosed in article) based on the thesis that small specialized teams can outcompete Big Tech in audio AI despite losing in text models. Key investment criteria: (1) Domain expertise over scale—audio requires deep understanding of acoustics, psychophysics, and compression theory that can't be solved by throwing compute at the problem. (2) Economics favor startups—audio models are 50x+ cheaper to train than frontier text models, removing Big Tech's capital advantage. (3) Organizational advantages—focused audio labs avoid multimodal tradeoffs where voice teams negotiate with text/vision teams for resources. (4) Research-to-product pipeline—Kyutai handles fundamental research, Gradium productionizes into APIs. For founders pitching audio AI: emphasize technical depth, team's audio research pedigree, and specific use cases where your approach beats general-purpose models.
How does voice AI latency compare to human conversation speeds?
Typical human conversation has 200-250ms turn-taking latency—the pause between one person finishing and another starting to speak. Kyutai's Moshi achieves 160ms theoretical latency, faster than human conversation, making it imperceptibly responsive. Neil notes Moshi is 'in some senses even too fast' for natural conversation. For comparison: (1) Traditional voice assistants (Siri, Alexa): 1-3 seconds including network latency, (2) OpenAI Advanced Voice Mode: ~500-800ms (estimates), (3) xAI's voice demo: Higher latency than Moshi (2024-2025). Technical contributors to latency: codec compression/decompression, model inference, network transmission (for cloud models), turn-taking prediction (for turn-based models). For founders: sub-200ms latency is critical for natural conversation; anything above feels robotic and forces users to wait awkwardly.
What does it mean that audio research had 'significantly lower acceptance rates' at AI conferences?
Before 2020, audio papers submitted to top ML conferences (NeurIPS, ICML, ICLR) had lower acceptance rates than vision or text papers—not because of quality, but because audio was culturally considered less important and 'uncool.' This created a self-reinforcing cycle: (1) Fewer audio researchers meant fewer reviewers comfortable evaluating audio papers, (2) Lower acceptance rates discouraged researchers from entering audio, (3) Less funding and prestige flowed to audio divisions at big labs, (4) Top PhD students chose vision or NLP over audio. Impact: This neglect created opportunity—audio became underexplored whitespace where small teams with domain expertise could make disproportionate breakthroughs. Kyutai's founders all came from underfunded audio divisions that were 'cooking in relative obscurity.' For founders: Look for domains with similar dynamics—culturally dismissed but technically promising.
How does the non-profit to for-profit pipeline work for AI research labs?
Research-to-product pipeline model: Non-profit labs (Kyutai) conduct fundamental research and publish open-source, while for-profit spinouts (Gradium) productionize into commercial APIs. Benefits: (1) Non-profit attracts research talent who value open publication over equity, (2) Funding sources—non-profits access philanthropic capital (Eric Schmidt, French billionaires), for-profits raise VC ($70M Series A), (3) Division of labor—researchers focus on breakthroughs, engineers focus on production polish, (4) Faster iteration—Kyutai ships prototypes proving feasibility, Gradium makes them enterprise-ready in months. Examples: OpenAI started non-profit then added for-profit arm (different structure), DeepMind (acquired by Google), Anthropic (PBC structure). For founders: This model works when fundamental research is expensive/risky but productionization has clear commercial path.
What open-source audio AI models and datasets should founders know about?
Key open-source models: (1) Moshi (Kyutai)—first full-duplex conversational AI, 7B parameters, runs on mobile. (2) Hibiki (Kyutai)—real-time speech-to-speech translation preserving speaker voice. (3) SoundStream (Google)—neural audio codec. (4) AudioLM (Google)—semantic/acoustic token separation. (5) Seamless (Meta)—multilingual translation (unmaintained). Datasets: (1) Fisher (LDC)—2,000 hours phone conversations with separated channels for full-duplex training. (2) Voxpopuli—400k hours multilingual speech. (3) MADLAD-400—machine translation across 400+ languages. (4) LibriSpeech—1,000 hours English audiobooks for ASR. For founders: Start with Moshi for conversational AI, Fisher for training full-duplex models, consider fine-tuning open models on domain data before training from scratch.
Keep reading

#182 — WebMCP: Towards an internet built for AI agents
Google unveiled WebMCP, a protocol designed to help websites communicate with AI agents to complete tasks.

#183 — How to deploy AI agents in Slack & Microsoft Teams
A step-by-step guide to building and deploying AI agents that operate natively within both Slack and Microsoft Teams.

#184 — How Agentic AI works
Every major AI agent runs the same core loop. The production-hardened version—with context compaction, loop detection, cost budgets, and graceful termination—is where things get interesting.