Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for local-first developers, AI app developers, voice-clone-resistant TTS users, edge-AI developers, AI-curious readers tracking on-device TTS releases, accessibility engineers, podcast / voiceover creators, and any developer wiring an AI coding agent to a local TTS pipeline -- and who can pair kyutai-labs/pocket-tts with PyTorch 2.5+ (CPU-only PyTorch is sufficient) for the inference surfac
Who should use it
Who should skip it
Consider kyutai-labs/pocket-tts lower priority if you already have a working solution in this category.
About this signal
kyutai-labs/pocket-tts is tracked by RepoRadar as a mit lightweight cpu-only text-to in the Kyutai CPU-Only 100M TTS (~200ms Latency) section. It was first seen on 2026-07-07 and last updated on 2026-07-07. The current verdict is 'try now' with a Silver tier and easy setup difficulty. The standout signals for kyutai-labs/pocket-tts are practical usefulness (9.0) and workflow potential (9.0), while maturity (5.8) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned kyutai-labs/pocket-tts a composite score of 7.9 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The 200+ star repo is at active maintenance (last commit recent) but 100M parameters means the consumer SHOULD benchmark the consumer's specific use case against the paper's MOS + WER numbers before relying on pocket-tts in production; CPU-only inference means the consumer SHOULD verify the consumer's CPU host can sustain ~6x real-time on the consumer's target hardware -- the ~200ms latency to first audio chunk is the canonical number on the MacBook Air M4 CPU; other CPUs may differ; PyTorch 2.5+ is required and the consumer SHOULD verify the consumer's PyTorch version is 2.5+ before relying on pocket-tts.