About Musonic
Musonic is made by one person: me, Doodz. I write the server, the Android app, the web player and the console together.
Why
I wanted to host my music myself. The existing servers and Subsonic apps work, but it felt like an MP3 player: a dull interface, no suggestions, nothing around it. What I wanted did not exist, so I made it.
Most self-hosted setups pair a server with apps made by other people. They talk through Subsonic, a protocol written years ago, so each side can only do what it allows. I write both sides: when I want something new, such as moving playback from the phone to the computer, I add it to both at the same time. Musonic Server still speaks Subsonic, so your Subsonic apps keep working.
Principles
Your files stay yours
Your music stays on your disk, on your server. Nothing is uploaded anywhere.
No ads, no subscription
No account to create with me, nothing to pay.
No tracking
Neither the apps nor the server report how you use them or when they crash. What leaves your server is listed in the documentation.
Said as it is
The benchmark shows where Navidrome is ahead too, and the limits are on this page.
Licences
The code is public on GitHub, under non-commercial licences: the apps under CC BY-NC 4.0, the server under PolyForm Noncommercial 1.0.0. In plain words: you may use Musonic for free, read the code, change it and share it, keeping my name on it, but never to make money. These licences are not « open source » in the official sense, because they forbid commercial use.
How AI is used
I organise everything and an AI writes most of the code. I make the decisions, draw the screens down to the pixel, bring the ideas, test on real phones and document every step and every mistake so it does not happen twice. The AI fills in the programming I cannot do. The method and every figure are public, including where Musonic is behind.
What Musonic does not do yet
Things other servers have and Musonic does not, today:
- smart playlists (filled by rules)
- several music libraries (one music folder only)
- scrobbling to Last.fm or ListenBrainz (plays are counted on your server only)
- public share links for a song, an album or a playlist
- ReplayGain, every song at the same loudness
- jukebox mode (playing on the server's own speakers)
- sign-in handled by a reverse proxy
- importing .m3u playlists
- plugins loaded while the server runs
Measured against Navidrome
1.8 s to scan the whole library, against 18.9 s for Navidrome; 19.5 MB of memory at rest, against 100 MB.
Measured on 22 October 2026 with Musonic Server 1.0.1 and Navidrome 0.64.2 (both have had new versions since). Both servers on the same small ARM server (2 cores), with the same library of 1,871 files, one at a time, three passes each. 36 measures in all, including the few where Navidrome is ahead.
The whole benchmark →