Mopidy

Spotify routes playback telemetry through remote servers and locks audio output into closed desktop or mobile apps. Mopidy runs as an extensible headless music server on your own hardware, routing local audio files and external streams through an open GStreamer pipeline. Playback data, network exposure, and audio routing remain entirely on infrastructure you manage.

Why Mopidy instead of Spotify

Mopidy replaces the closed client layer of commercial streaming platforms with a modular Python daemon. While Spotify offers a proprietary cloud catalog and algorithmic radio, it forces you to use closed apps that continuously report listening activity. Mopidy shifts playback authority back to your local network. It plays your local audio collection—FLAC, MP3, OGG, or AAC—and can connect to external backends when remote tracks are needed. You control the server using independent MPD clients or browser interfaces, removing vendor lock-in.

From a privacy and operational perspective, the trade-off centers on infrastructure ownership versus cloud convenience. Spotify operates as a black box dependent on an internet connection. Mopidy runs locally on Linux or macOS, exposing JSON-RPC and MPD endpoints that you can isolate behind a firewall. The cost of that privacy is operational responsibility: you must maintain the host, organize storage, and manage network routing. While third-party streaming plugins can break when upstream APIs change, local media playback remains entirely within your control.

What it does well

• Dual interface protocols: Exposes standard MPD and WebSocket JSON-RPC endpoints, allowing control from terminal clients like ncmpcpp, web frontends like Iris, or custom shell scripts.
• Resilient actor architecture: Uses the Pykka actor model in Python to isolate backends and frontends, preventing a failing plugin from crashing core playback.
• Configurable GStreamer pipeline: Routes audio via mopidy.conf directly to ALSA devices, PulseAudio, PipeWire, or multi-room tools like Snapcast.
• Direct filesystem browsing: Reads directory trees from disk without requiring a slow initial library index or relational database.
• Declarative configuration: Uses plain-text INI files that integrate into Ansible playbooks, Docker containers, and version-controlled homelab repositories.
• Home automation hooks: Integrates with Home Assistant and MQTT to trigger music playback, audio chimes, or alerts from server events.