selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

Music Assistant logo

Self-host Music Assistant

2.10.12

One music library for every service and speaker

ReleaseOpen SourceApache-2.0
docker run -v <dir>:/data --network host ghcr.io/music-assistant/server
Updated2 days ago
LanguagePython
Setup difficultyModerate
MobileNative app
ThemeDark mode
Stars
3 343
CPU
Raspberry Pi 4 or newer, or equivalent
RAM
2GB of RAM
Ports
8095 (Web interface / API), 8097 (Audio stream server for players)
Requires
Ffmpeg
Docker
ghcr.io/music-assistant/server
Discover screen in dark theme with rooms playing, top picks and recently playedAlbum library shown as a grid of album covers (dark theme)Now playing view on a phone with cover, progress and playback controlsMusic Assistant web UI screenshot from the documentation previewMusic Assistant web UI screenshot from the documentation previewMusic Assistant mobile app screenMusic Assistant mobile app screenInitial authentication setup dialog of the UIEdit user dialog with player and music source restrictions

What is Music Assistant?

Music Assistant is an open-source media library manager that pulls music from subscription services and from your own files, and also handles radio, podcasts and audiobooks. Releases found on several services are merged into a single entry, playlists may mix providers, and metadata providers supply artwork, lyrics and artist details. The server owns playback state, so music carries on after you close the tab and a queue can be handed to another speaker; group hardware from different brands (Sonos, AirPlay, Google Cast, DLNA, Squeezelite and others) for synchronized multiroom listening, with gapless output, crossfade, loudness levelling and per-player DSP filters. Its web UI listens on port 8095, a JSON API with long-lived tokens supports automation, and several accounts with roles plus per-user player or source restrictions can share one installation. It pairs closely with Home Assistant for automations, voice control and ducking announcements, while plugins add party mode, quizzes, lyrics and AI Radio. Install it from the HA App store, the recommended route, or from the ghcr.io container image using host or macvlan networking so mDNS and uPnP discovery work. Plan for a 64-bit machine that never sleeps, with 2GB of RAM as the floor. The server is deliberately not on PyPI, distro packages are unsupported, and every music service still needs its own subscription.

Music Assistant alternatives

Should you self-host Music Assistant?

Music Assistant scores 71/100 on selfhost.directory (how scoring works) and ranks #3 of 59 in Music Streaming. It has 3 343 GitHub stars, +179 in the last 30 days.

It shipped 50 stable releases in the past year. The latest, 2.11.0b9, came out on 14 November 2026. New versions land roughly every 3 days.

Setup is moderate: expect some configuration beyond a single command. An official Docker image is available. It is Apache-2.0-licensed and written mostly in Python.

Its closest alternative on selfhost.directory is koel (74/100, 17 351 stars). It scores higher overall, so compare the two before you pick. See Music Assistant vs koel side by side.

Features

  • Broad player support
  • Cross-service item matching
  • Discover view
  • Gapless playback and crossfade
  • Metadata Enrichment
  • Multiroom speaker groupingSynchronization depends on speakers and group type
  • Multi-user accounts with permissions
  • Per-player DSP filters
  • Playlist sync between servicesAvailability depends on the destination service catalogue
  • Plugin System
  • Queue transfer between players
  • Server-hosted playback queue
  • Smart Playlists
  • Unified music library
  • Volume Normalization

Music Assistant README

Music Assistant

Music Assistant Server

CodSpeed

Music Assistant is a free, opensource Media library manager that connects to your streaming services and a wide range of connected speakers. The server is the beating heart, the core of Music Assistant and must run on an always-on device like a Raspberry Pi, a NAS or an Intel NUC or alike.

How to install Music Assistant

Install Music Assistant with Docker

host networking or macvlan networking
Environment variables
LOG_LEVEL
docker run -v <dir>:/data --network host ghcr.io/music-assistant/server

Docker compose (recommended):

services:
  music-assistant-server:
    image: ghcr.io/music-assistant/server:latest # <<< Desired release version here (or use beta to get the latest beta version)
    container_name: music-assistant-server
    restart: unless-stopped
    # Network mode must be set to host for MA to discover and stream to players (see networking note below)
    network_mode: host
    volumes:
      - ${USERDIR:-$HOME}/docker/music-assistant-server/data:/data/
      # Optional: expose local music to MA by bind-mounting it read-only
      - /path/to/your/music:/media:ro
    environment:
      # Provide logging level as environment variable.
      # default=info, possible=(critical, error, warning, info, debug)
      - LOG_LEVEL=info

/data is the persistent data volume; mount local music read-only. Bridge networking with explicit 8095/8097 mappings only works for software players and is not supported by the team.

How to configure Music Assistant

  • LOG_LEVELinfoLogging level, provided as environment variable in the docker compose setup.

    values: critical, error, warning, info, debug

  • --log-levelCommand-line log level when running the server module directly (development).

    values: debug and other levels

Music Assistant releases & version history

@ Every self-hosted release, weekly

One Monday email with the week's stable releases across the directory.

More in Music Streaming

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…