Self-hosted music streaming for the whole family
A family shares a lot of music and very different tastes. Most self-hosted servers handle shared storage well and per-person listening less well. Melarka is designed for a household: everyone has their own account and phone app, and everyone benefits from the songs any one of you adds.
One library, one account per person
You add your family under Admin, Users. From then on each person signs in on their own phone and has their own:
- favorites and dislikes;
- playlists and play history;
- personal radio and a nightly "For you" list of YouTube songs they do not have yet, based on what they play and favorite most;
- interface language: English, 简体中文, 繁體中文 or svenska, chosen per person (music metadata is never translated).
The library underneath is shared. A song one person adds, by download or by copying it to the music folder, is there for everyone. That is the main difference from a streaming plan where each person builds their own library.
Keeping the shared library tidy
Songs added after the first scan start as pending. Three plays keep a song automatically, so a one-off track does not clutter the library for long. A deleted song waits 30 days in the trash before it is gone. Admins can fix titles, artists, albums and years as overrides, without touching the files, and manage users, pending songs, downloads, trash and libraries from one admin console.
Phones, car and tablets for every family member
There are native iPhone and Android apps, and a web app that installs to the home screen of any phone and runs full screen. Favorites can be cached on the phone for tunnels and dead zones, and the Android app can start your favorites when the phone connects to the car. See the car autoplay guide.
Private by design
Melarka has no tracking. Your server only contacts the services you use: YouTube for search and downloads, lyrics sources, and Last.fm if you configure it. The apps talk only to your server; the phone never contacts YouTube directly. Nothing about your family's listening leaves the house. (An anonymous weekly install count, with no user names, songs or history, can be switched off in Admin, System.)
What you need at home
- A Linux machine or NAS with Docker (amd64 or arm64) that stays on. A small home server is enough.
- A domain name and an HTTPS reverse proxy to use it from phones outside the house; the README shows Caddy and nginx.
- Music folders, YouTube downloads, or both.
Install steps are in the Docker install guide. For how this compares with a streaming subscription, see Spotify alternative.
Limits to know about
Melarka is a music server, not a catalogue: you bring the music. It is Linux-and-Docker only on the server side. The iPhone app is signed with your own Apple ID rather than installed from the App Store, and each phone needs to reach the server over HTTPS.
Install in one command
Needs a Linux machine or NAS with Docker.
curl -fsSL https://raw.githubusercontent.com/aaronsuns/melarka/main/deploy/install.sh | sh -s -- /path/to/your/music
Install in one command ★ Melarka on GitHub
Step by step and configuration: docs/install.md.
FAQ
Can each family member have their own favorites and playlists?
Yes. Each person has their own account with favorites, playlists, history, radio and language.
Do we share the music library?
Yes. The library is shared, so a song one person adds is available to everyone.
Does it work for children's phones?
Yes, with the iPhone, Android or web app. You create accounts under Admin, Users. Melarka has no tracking and the apps only talk to your server.
What happens to songs nobody plays?
Songs added after the first scan start as pending; three plays keep a song automatically, and a deleted song waits 30 days in the trash.