AudioMuse AI is shipping like the team has a deadline, not a roadmap. ToolVitals shows 8 release events in 30 days, 19 releases in 90 days, a shipping score of 100, and 1,662 GitHub stars. The catch is simple: the GitHub Pages URL in the payload currently returns a 404, so the repo is the real product surface right now.

The repository README still makes the positioning clear. AudioMuse AI is a self-hosted, Dockerized playlist generator for Jellyfin, Navidrome, LMS, Lyrion, and Emby. It does sonic analysis locally, avoids external APIs, and pushes features like clustering, instant playlists, Music Map, similar-song playlists, song paths, Sonic Fingerprint, Song Alchemy, and text search.

What the recent releases say

The release history points to a team that is sanding down deployment friction. v1.0.0 moved most configuration into a setup wizard, so users stopped wiring every knob through environment variables. v1.0.2 added provider migration, multi-user support, and a dashboard, which is a clear bet on operators who will manage more than one library or one account. v1.0.3 tightened the dashboard, aligned CLAP search with index-based search, and improved backup and restore. v1.0.4 rebuilt the Nvidia image after a GPU dependency issue.

That is a useful signal. This is not just another recommendation toy. The maintainer is treating installation, upgrades, GPU images, account separation, and migration as first-class work. The repo README also says the project is independent and not affiliated with audiomuse.ai, which matters because the live GitHub Pages site is currently not a working homepage.

What the data does not tell you

ToolVitals can see release cadence, stars, and repo activity. It cannot tell you whether the recommendations are actually good, whether the scans are fast on a 200,000-track library, whether the Docker stack is painless on your hardware, or whether users keep the app past the first weekend. It also cannot tell you revenue, retention, or how often the UI gets in the way.

The 69 data confidence score fits that limit. The signal is strong enough to write about, but not strong enough to pretend we have product-market proof.

Peer context

Compared with nearby tools, AudioMuse AI is smaller but still active. Jitsu shows 37 release events in 30 days and 4,702 stars. Onyx shows 27 release events in 30 days and 28,893 stars. AudioMuse AI sits at 8 release events in 30 days and 1,662 stars. That reads like a focused niche project, not a category giant.

Recommendation

If your team runs a self-hosted music stack and you care about local analysis over cloud APIs, evaluate AudioMuse AI now. The release cadence says the core workflow is still moving, and the recent releases show real attention to setup and migration. If you need a polished public landing page, stable docs, and proof that the recommendation engine beats manual curation, wait and test it hard before committing.

Sources used: project website, GitHub repo, v1.0.0 release, v1.0.2 release, v1.0.3 release, v1.0.4 release.

Sources