# Two products named NSMusicS, and only one of them lives in this repository

> NSMusicS is an open-source music client for local libraries, private cloud music and self-hosted servers such as Navidrome, Jellyfin and Emby. Its Electron and Web build is called a transition edition by the project itself, while the paid Windows package on Microsoft Store is a closed-source Flutter codebase that is not published here.

**Super-Badmen-Viper/NSMusicS** — NSMusicS NineSong: a cloud-native music server and full-platform client, supporting Navidrome, Jellyfin and Emby.

- Repository: https://github.com/Super-Badmen-Viper/NSMusicS
- Stars: 2,247 · Forks: 97
- Language: Vue
- License: AGPL-3.0
- Published: 2026-10-14 · Updated: 2026-10-14 · Language: en
- Canonical page: https://hysenlabs.com/projects/super-badmen-viper-nsmusics

## Two product lines answer to one repository name

NSMusicS is a cross-platform music client for local folders, private cloud music and self-hosted streaming setups, and its repository lists Vue as the primary language. Two different products carry that name. The Windows package currently shown on Microsoft Store is NSMusicS-Flutter, built on a closed-source private codebase that is not published in this tree, sold for money, and carrying a 15-day trial on Windows. What you can read here is the Electron and Web line, which the project calls a transition edition kept in place only until a refactored client wave lands. The README draws the split as a table: open source in the repository, closed source in the Store, and the Store package following what it calls its own private delivery rhythm.

That distinction matters more than the shared logo. A reader who downloads the app from the Store is not running the code in this repository, and a reader who expects the source tree to match the installed program will find a different framework underneath.

## The Electron client is a bridge, not a destination

The published desktop client covers Windows, macOS and Linux, plus Docker-oriented desktop and web-adjacent scenarios. Its stated focus areas are music library management, compatibility with NineSong, Navidrome, Jellyfin and Emby, local library playback, professional playback workflows, internationalization, and background and tray playback. Every item in that list describes a client meant to be replaced.

The project keeps the Electron line in place as a bridge until React, React Native, Vue and Angular clients arrive, and it states that wave was targeted for roughly mid-May 2026. This repository is published under an AGPL-3.0 licence, and its last push is recorded on 2026-07-01. The newest version string on record, NSMusicS-v2.3.1, carries the date 2026-04-09. The one before it, NSMusicS-v2.3.0, is dated 2024-11-29, and a third entry named NSMusicS-Win-Update is dated 2024-09-03. Consecutive version numbers separated by roughly sixteen months, with no newer build recorded after 2026-04-09, leave an adopter weighing a codebase its own authors have labelled temporary.

## Three servers it connects to and does not ship

The client is designed to sit in front of servers other people run. Navidrome, Jellyfin and Emby are named as supported backends, and NineSong, the paired project in a separate repository, is the fourth target.

Compatibility is stated as a goal rather than configured. There is no host field, no port, no API key, no environment variable and no config file anywhere in the documentation for reaching any of them. For a Navidrome owner the missing piece is the whole handshake, because a self-hosted server connection depends on a URL plus a token, and neither string appears in the published text or in the entry list at the top of the repository. Whether a given backend combination works is something a reader has to establish by reading client code, not by reading pages.

## NineSong is the destination, its backend snapshot is frozen

NineSong is the server half of the product, hosted in its own repository, and the NSMusicS README positions it as the cloud-native backend for music today, with wider personal digital center ambitions covering video, gallery, notes and documents later. Its stated differences from conventional music servers are richer library management, stronger metadata and tag workflows, search behaviour tuned for music, CUE-related playback scenarios, and recommendations built from user data and metadata. Two saved copies of that project's README sit in this tree:

```bash
doc/NineSong_Open_Source_Reference.md
doc/NineSong_Open_Source_Reference.zh-CN.md
```

What matters for an adopter is the status note attached to them. The NineSong README saved here describes its open-source backend repository as a frozen public snapshot rather than a continuously updated backend. The client is being pointed at a server that the same documentation treats as parked, while the long-term direction keeps expanding toward a personal digital center.

## Four framework lines inside one refactoring wave

The planned wave covers React, React Native, Vue and Angular as parallel client lines. The project states that the Electron and Web variants inside that wave will follow the official and community-recommended practices of each stack instead of forcing one shared implementation style across all frameworks.

Read plainly, that decision trades one codebase for four, and each addition multiplies the surface that has to track backend changes in Navidrome, Jellyfin, Emby and NineSong. The repository's primary language tag says Vue, yet the only client directory in the entry list is `NSMusicS-Electron/`, so the language tag describes intent rather than the code sitting in front of you. Platform plans follow the same widening pattern: App Store packages for macOS and iOS, Google Play for Android, Linux already covered, and HarmonyOS named as a later scenario.

## Fetching the client without a single install command

There is no install command in the documentation. Nothing shows a package manager line, a clone step, a container run, a port or a build tool version. The project points readers at two places instead: the source tree on the default branch `main`, where the client lives under `NSMusicS-Electron/`, and the builds attached to the repository. For the paid Windows package it points at the Microsoft Store page, whose product id is 9N0RWS2TJXG1, and it gives the Store deep link for that same product:

```bash
ms-windows-store://pdp/?productid=9N0RWS2TJXG1
```

The web page for that product is:

```bash
https://apps.microsoft.com/detail/9N0RWS2TJXG1
```

Handing the deep link to the system opens the Store listing on Windows. On macOS and Linux there is nothing comparable in the documentation, since the App Store and Google Play packages are described as planned rather than published. A reader on those platforms is left holding the source tree and no instructions for turning it into a running app.

## The Docker image exists only as a table entry

The edition table names the delivery channels for the open-source line as the builds attached to the repository, a Docker image, and the source tree. The entry list at the top of this repository is exactly this:

```bash
.gitattributes
.github/
.gitignore
LICENSE
NSMusicS-Electron/
README.md
README.zh-CN.md
doc/
```

There is no Dockerfile, no compose file, no image tag, no registry and no exposed port. So the container channel is a name without coordinates: the same table cell that tells a reader container delivery exists gives that reader nothing to pull, and no digest to check.

A second gap sits beside it. The client needs a server address and a token before it can play anything, and the repository offers no configuration surface for either. That leaves a reader who wants container delivery to assemble the image and the credential plumbing from scratch, which is a different job from installing a music player.

## Search, tags, ratings and lyrics are the stated workload

The target reader is anyone whose music no longer lives in one simple folder. The stated workload is large libraries handled through search, metadata, tags, ratings, playlists and lyrics, and the client is described as pushing past basic playback with lossless support, precise lyric timing, audio effects, immersive playback views and theme customization.

Fifteen topic tags describe the repository, and two of them are never explained in the text: `naiveui` and `xiaomi-smart-home`. Nothing in the documentation says which interface library is used or what a smart home integration would do, so those tags point at capabilities a reader cannot verify from the published pages. A tag list is cheap to write and easy to carry over from another project, which is worth keeping in mind before treating it as a feature map.

## Conclusion

Take the source tree if you already run Navidrome, Jellyfin or Emby and want a desktop client you can read and patch. The Electron and Web line is buildable, and the AGPL-3.0 terms let you modify and redistribute it. Leave the Store package out of any adoption plan, because it is a closed-source Flutter product with its own private cadence and its own 15-day trial. Before committing an afternoon, confirm three things the repository does not answer: how server credentials are supplied, where the Docker image is published, and what turns the source tree into a running app.

## FAQ

### Is NSMusicS free to use?

The Electron and Web line in this repository is free under the repository licence and related project terms. The Windows package on Microsoft Store is NSMusicS-Flutter, a closed-source private codebase that is sold for money and currently offers a 15-day trial on Windows.

### Which music servers does NSMusicS connect to?

Navidrome, Jellyfin and Emby are named as supported backends, along with NineSong, the paired server project hosted in its own repository. The documentation gives no host, port, token or config key for reaching any of them.

### Does NSMusicS run on macOS and Linux?

The published Electron desktop client covers Windows, macOS and Linux. App Store packages for macOS and iOS and a Google Play build for Android are listed as planned, and no build instructions are given for any platform.

### How do I install NSMusicS?

The documentation contains no install command at all. It points to the source tree on the default branch main, where the client lives under NSMusicS-Electron/, and to the builds attached to the repository.

### Can I run NSMusicS in Docker?

A Docker image is named as one delivery channel for the open-source line, and Docker-oriented desktop scenarios are listed among the covered ones. The top-level entries of the repository contain no Dockerfile, compose file, image tag, registry or port.

## Sources

- [Issues](https://github.com/Super-Badmen-Viper/NSMusicS/issues)
- [License: AGPL-3.0](https://github.com/Super-Badmen-Viper/NSMusicS/blob/main/LICENSE)
- [README](https://github.com/Super-Badmen-Viper/NSMusicS/blob/main/README.md)
- [Releases](https://github.com/Super-Badmen-Viper/NSMusicS/releases)
- [Super-Badmen-Viper/NSMusicS on GitHub](https://github.com/Super-Badmen-Viper/NSMusicS)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/super-badmen-viper-nsmusics