neuphonic/neutts

On-device TTS model by Neuphonic

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 36 minutes ago
Added to GitGenius on September 10th, 2026
Created on October 2nd, 2025
Open Issues & Pull Requests: 37 (+0)
GitHub issues: Enabled
Number of forks: 657
Total Stargazers: 6,278 (+1)
Total Subscribers: 58 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.3 hours
Mean response time: 10.0 days
90th percentile: 18.4 days
Tracked items: 61

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 8% of issues opened in the past year have been closed. Three people close 73% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 30
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 232 days
Stale 30+ days: 30
Stale 90+ days: 25

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Neutts is an on-device text-to-speech model that runs locally without requiring external API calls or cloud infrastructure. The tool addresses the need for privacy-preserving speech synthesis by executing the entire TTS pipeline on the user's machine, eliminating data transmission to remote servers and reducing latency compared to cloud-based alternatives.

Developers adopting Neutts should understand that it is designed for scenarios where local inference is a priority, such as applications handling sensitive audio content, offline environments, or systems with strict data residency requirements. The on-device approach trades off some flexibility for privacy and control, making it suitable for embedded systems, edge devices, and applications where network dependency is undesirable.

The project shows active development with regular commits and ongoing refinement of the core model and inference pipeline. The codebase demonstrates attention to implementation details through iterative improvements and bug fixes. Community engagement appears present through issue tracking and response patterns, indicating the maintainers are responsive to user feedback and technical questions.