Gordo · Updated 2026-09-08

The Self-Hosted Music Software Landscape

A scannable directory of self-hosted music software by action — discovery, intake, library management, servers, desk and phone playback, networking, DJ/performance, playlists, multi-room, and hybrid stacks.

This post is the list of software developed and discussed on State of Self-Hosted Music Listening. I started it out of need, and out of a curiosity I could not drop: why isn’t there a horizontal, stable way to keep one coherent catalog — desk, phone, commute, crates, simple enough that listen and work your catalog stays fun instead of a technical challenge. The specialists below are excellent. The hole is cohesion. That research is also why I built Tape Music Suite — v1 now. It offers full service now from library management to away from home in all your devices. My goal is to slowly offer all the stack in to one cohesive experience.

If you want to add something to this list or you are working on any step of the process, it is open here: self-hosted-music-software.

Discovery

Here’s how I see this layer: two jobs people mix up. First, find music in the wild — storefronts and platforms where you hear something and want it later. Second, rediscover what you already own — radio-like paths from your catalog, not Spotify Radio with different branding. Not stage software.

Find (storefronts & platforms)

Spotify — Strength: the default browse/radio gravity most people still mean by “discovery”; playlists and algo as the map of “what exists.” Weakness: a rental catalog; likes and Discover Weekly are not files, and they vanish when the subscription does.
SoundCloud — Strength: the live/DJ/unreleased plane storefronts still miss — mixes, promos, one-off uploads. Weakness: identity and permanence are messy; a like is not a purchase and URLs rot.
Bandcamp — Strength: artist-direct browse plus a collection you actually buy; Friday-drop culture that feeds a real archive. Weakness: discovery is still a storefront habit; the files only arrive if you complete intake.
Beatport — Strength: DJ-storefront browse — new promo, genre charts, the “complete metadata” expectation. Weakness: personal rips never matched that shape; a cart is not a library manager.
Apple Music / YouTube / YouTube Music — Strength: the other mass catalogs people actually hear music in — editorial, video, radio. Weakness: same rental problem; a heart is not a file.
Tidal / Qobuz / Deezer — Strength: hi-res / alternate catalog gravity when Spotify isn’t the taste map. Weakness: another rental; Qobuz purchases are the honest file path, the rest is still a stream.
Discogs — Strength: marketplace + release-page crate digging — you find a pressing, not a playlist tile. Weakness: shopping and identity in one site; it won’t play your NAS.

Rediscover (owned catalog)

Plexamp sonic / radio — Strength: sonic analysis and radio-like paths inside owned Plex music; often leads local “mix” polish conversations. Weakness: closed loop; best discovery UI may not be where tags get fixed.
Symfonium smart playlists — Strength: rule-based playlists on the phone client; high bar when tags are good enough. Weakness: weak tags yield weak lists; rules that live only on the phone don’t export cleanly.
Server random / similar (Navidrome / Jellyfin-class) — Strength: built-in random/similar endpoints that cost nothing extra once the server is up. Weakness: often thinner than closed sonic loops — useful, not magical.
Desk dynamic playlists (foobar2000 / MusicBee / iTunes-class) — Strength: dynamic lists where the desk authority owns the rules. Weakness: best discovery UI may not be where enrichment happens or where the phone listens.
Manual crate rituals / Preview folders — Strength: human crate digging and staging as rediscovery — underrated and reversible. Weakness: unpaid discipline; doesn’t scale without tagging hygiene (n/a ritual).
MusicBrainz / Discogs-assisted browsing — Strength: release identity / provenance that makes search trustworthy. Weakness: not a replacement pitch for either service as a listening product — identity fuel, not a radio engine.
Last.fm / ListenBrainz scrobble habits — Strength: optional play-history aided rediscovery when you already scrobble; ListenBrainz is the open side-channel for the same job. Weakness: don’t invent centrality; history is a side channel, not the library.

Intake & acquisition

Arrival tools. They feed Downloads → Preview → archive; they are not the catalog authority. Tape’s future notes treat this as an optional plugin over external daemons, not core playback.

Purchases & collection sync

The honest file path: you paid, then you copy the files home.

Bandcamp — Strength: purchase includes a real download (often FLAC) you own; collection page is the receipt. Weakness: clicking through every release is unpaid labor unless a collection syncer runs.
Bandsnatch / BandcampSync — Strength: batch-sync a Bandcamp collection you already bought into an intake folder. Weakness: cookie/session auth; still Inbox, not identity — Picard/beets come next.
Beatport / Qobuz purchases — Strength: storefronts that actually hand you files (DJ WAV/AIFF; Qobuz hi-res) when you buy. Weakness: one more Downloads tree; tags still need a hygiene pass.

Streaming-catalog fetchers

Spotify/SoundCloud as a search key or playlist freeze — not a purchase. Same plane as yt-dlp: intake chaos until tagged. Storefront TOS apply; this list is inventory, not a how-to.

spotDL (often searched as SpotyDL) — Strength: Spotify URL/playlist as the map, YouTube (via yt-dlp) as the audio, metadata/art embedded so the Inbox looks like a library. Weakness: YouTube is not the master you streamed; matches miss; still not enrichment.
SpotiFLAC (SpotyFLAC-class) — Strength: Spotify link as the search key, lossless from other storefronts when people want FLAC instead of a YouTube match. Weakness: not a receipt; third-party APIs and TOS; treat the folder as Preview until identity is written.
streamrip — Strength: Qobuz/Tidal/Deezer/SoundCloud as one CLI when the subscription is already the catalog you live in. Weakness: account/TOS gravity; another daemon before the hub.
yt-dlp / scdl — Strength: CLI extraction when the “download” is a YouTube or SoundCloud idea, not a storefront purchase. Weakness: metadata is whatever the page had; this is intake, not enrichment.

Wanted lists & P2P

Lidarr — Strength: wanted-artist / quality-profile manager in the arr family — “I want this release” as state, not a one-off search. Weakness: indexer/download-client gravity; the wanted DB is yet another authority beside the files you actually play.
slskd — Strength: Soulseek as a daemon API — the transfer engine collectors already drop into an intake folder. Weakness: P2P seeking is not library hygiene; path chaos lands in Inbox unless something else stages it.
Soularr — Strength: bridge that reads Lidarr wanted state and acquires through slskd — the orchestrator our plugin research named instead of reimplementing Soulseek inside a hub. Weakness: three moving parts (Lidarr + slskd + Soularr) before a file is even tagged.
Soulseek / Nicotine+ — Strength: the human seeking UI that still finds rips and promos storefronts never carried. Weakness: desktop client as intake, not as identity; folders arrive messy on purpose.

Library management

Here’s how I see this layer: make a local archive searchable, identifiable, and trustworthy without destroying folder truth — tags in files, release identity, inbox/staging, duplicate judgment. Arrival tools live in intake.

Enrichment & identity

MusicBrainz Picard — Strength: release-aware tagging against MusicBrainz / AcoustID that writes identity into the files so it survives a player reinstall. Weakness: matching still costs attention, and same-title different masters punish overconfident auto-accept.
beets — Strength: scriptable CLI import, rename, and metadata pipeline for people who want the library as versionable data. Weakness: it can become yet another authority beside a player DB, and the learning curve is real before the pipeline feels safe.
SongKong / Yate / Jaikoz — Strength: automated tag repair that buys time back on mass enrichment. Weakness: destructive confidence against ambiguous releases.

Batch file editors

Mp3tag — Strength: durable batch tag editor (Windows + Mac) that writes portable edits to disk — the craft surface when DJ apps invited tagging and nothing round-tripped. Weakness: it won’t invent a listening or phone workflow for you; it’s hygiene, not a suite.
Kid3 / TagScanner — Strength: cross-platform / niche batch tagging on the same plane as Mp3tag-class. Weakness: fragmented naming and fewer shared workflows.

Desk / OS library homes

foobar2000 (as manager) — Strength: columns and components as organize+listen UI without installing a separate library app. Weakness: deepest state stays in the foobar world; phone continuity is still a separate problem.
MusicBee — Strength: whole-Windows-home for daily library, playlists, and playback — an emotional center that may never need a server. Weakness: Windows gravity and dual-library drift if the handset diverges from the desk home.
MediaMonkey — Strength: Windows library manager/player gravity with careful enrichment rituals. Weakness: auto-organize narratives can scare people who already fear destructive cleanup.
Swinsian — Strength: Mac-native library with playlist/XML-bridge habits that still feed export stories. Weakness: bridge labor remains; reliability and scale pain show up the same places iTunes-era lists did.
Apple Music / iTunes — Strength: historic smart-list authority and XML export source that still shapes how people think playlists should work. Weakness: reliability frays at scale; streaming volatility and Date Added / re-import pain compound the handoff.

DJ hygiene & accidental managers

Lexicon — Strength: commercial DJ library manager put beside performance apps so the stage DB is not the only hygiene home. Weakness: another paid seat in a fragmented toolchain; sync into DJ apps can still drop crates if paths fight.
Beatport Pro–shaped workflows — Strength: enrichment intake from the Beatport storefront world taught “complete” metadata expectations that make promo libraries feel finished. Weakness: personal rips never matched that shape; legacy desktop Pro appears discontinued — Pro URL TBD (no invented pro. page).
rekordbox / Serato / Traktor DBs — Strength: performance databases that become de-facto catalogs — cues, grids, and show confidence where it matters. Weakness: tags and prep often stay app-only; they may not round-trip to files, and migration or path moves hurt.

Server indexes as authority

Navidrome / Jellyfin / Plex indexes — Strength: scan-time catalog truth that clients can browse without another desk app. Weakness: a rescan “fixes” one truth and can break playlist edge cases another client depended on — now you have yet another authority.

Rituals (non-app)

Intake folders (Downloads → Preview → archive) — Strength: reversible staging before main-root commit; real management even when no library app is open. Weakness: discipline is unpaid labor; skip it and the main root inherits chaos.

Serving / backends

Here’s how I see this layer: index owned files, expose catalog + stream API, stay up — a finished backend vertical beside desk and phone layers.

Navidrome — Strength: lean Subsonic/OpenSubsonic music index + stream with a small footprint and replaceable clients — the DIY-Spotify convergence point I see most often. Weakness: “server up” is not organization, discovery polish, or DJ export; ops and tagging still sit on you.
Jellyfin (music) — Strength: music as a module on a broader self-hosted media appliance you may already run for video. Weakness: client quality and metadata awkwardness vary; music UX inherits whatever companion you pick.
Ampache — Strength: long-running web music server with API clients and Subsonic-family muscle memory. Weakness: older UX gravity; not always the first pick when people want a lean modern footprint.
Subsonic-family / forks — Strength: protocol-era servers that shaped the whole client ecosystem; older deployments still work. Weakness: lineage and licensing history confuse newcomers; forks and successors scatter the “which one” answer.
OpenSubsonic — Strength: spec / lingua franca that makes replaceable clients possible — a technical shared language, not a moral category. Weakness: a spec is not a product; someone still has to run a server and a client that both speak it honestly.
Plex (music) — Strength: index and stream owned music inside an ecosystem that usually pairs with Plexamp polish. Weakness: closed loop and cost/identity tax; management may still need a side tool.
gonic — Strength: minimal Subsonic-compatible music server for people who want even less than Navidrome’s surface. Weakness: thinner docs and client assumptions.
Polaris — Strength: lean self-hosted music streamer (Rust) with its own API and first-party Android client; cited when people want a small server without the Subsonic-family gravity. Weakness: thinner shared “how we run this with Symfonium” muscle memory than Navidrome.
Music Assistant — Strength: Home Assistant–adjacent music engine that can fan a library out to many player types (including Sendspin). Weakness: abstraction over local and cloud sources — easy to reintroduce a second catalog while chasing whole-home sync.
Lyrion (LMS) — Strength: legacy Squeeze network-audio lineage still honest in some collector homes. Weakness: niche continuity; not the default DIY-Spotify path most people mean today.
Emby — Strength: commercial media-server peer on the same plane as Plex/Jellyfin when music mode appears. Weakness: music is rarely the reason people choose it.
Docker — Added Docker mainly because it is the most used infra as a module system to mount on NAS services. Strength: the ops surface that makes mounts, backups, and rescans repeatable. Weakness: not a music product — listening trust now includes containers, volumes, and recovery fear.

Desktop playing

Here’s how I see this layer: craft playback on a serious desk machine — formats, gapless, DSP, dense listen UI — not merely staging for a gig.

foobar2000 — Strength: high-craft local playback and a component ecosystem that still defines serious desk listening for a durable cohort. Weakness: deepest state stays on the machine; “foobar on mobile?” is continuity demand the player itself never solved.
MusicBee — Strength: integrated Windows listen + organize so one app can be the whole home. Weakness: leaving Windows (or adding a phone path) reopens dual-library risk.
Plexamp (desktop path) — Strength: polished playback surface for Plex music — closed polish reference without pretending to replace foobar craft. Weakness: you’re inside the Plex loop; management and file hygiene may still need another tool.
Roon — Strength: high-polish commercial listening suite over local/NAS libraries — a closed reference bar for curated desk listening. Weakness: cost and subscription objections are fair; it’s not cheap hygiene, and continuity outside Roon is still your problem.
Feishin — Strength: desk/browser UI against OpenSubsonic-family servers; common in the Navidrome + Symfonium pride stack. Weakness: it’s a client, not a library manager — tagging and backups stay elsewhere.
OS stock players — Strength: zero-friction default glass that plays files today. Weakness: baseline serious users outgrow; no library craft, no portable identity story.
Audirvana / VOX — Strength: audiophile / high-res desk listening for format and DSP loyalty. Weakness: niche surface area; continuity outside the desk player is still your problem.
Strawberry / Quod Libet / Clementine / DeaDBeeF — Strength: Linux/open desk players on the same plane outside Windows-centric stacks. Weakness: thinner shared “how we run this with a phone” muscle memory.

Mobile clients

Here’s how I see this layer: use the owned archive away from the desk — browse, search, play, offline/cache, car — without rebuilding in a storefront.

Android & closed polish

Symfonium — Strength: Android API client high bar — profiles, smart playlists, offline cache against servers; the daily-driver citation in DIY-Spotify setups. Weakness: paid client value objections; export back to DJ apps and desk authorities still fragile.
Plexamp — Strength: closed polish ceiling for phone listening inside Plex — pre-cache, sonic features, finished-feeling UI. Weakness: you’re buying the Plex loop; outside that ecosystem the bar is a reference, not a portable library manager.

iOS (OpenSubsonic / Jellyfin-shaped)

Amperfy — Strength: iOS client against Subsonic-family / Jellyfin-shaped backends (GitHub is project home). Weakness: iOS field churn — features and polish vary; you’re still dependent on server honesty and cache freshness.
Shelv — Strength: iOS owned-library streaming client; class holds if renamed. Weakness: smaller surface than the Android high bar; continuity across desk ratings/playlists is not automatic.
Arpeggi — Strength: iOS OpenSubsonic/Jellyfin-field client with App Store as distribution home. Weakness: App Store–only footprint; expect the same server/cache seams as peers.
Narjo — Strength: another iOS client in the owned-library field. Weakness: inventory peer, not a guarantee of Symfonium-class depth — verify against your backend before committing.
Nautiline — Strength: iOS client for people already on Subsonic/Jellyfin-shaped stacks. Weakness: same field limits — phone is projection, not the place tags get fixed.
NaviBeat — Strength: newer iOS / Apple multi-device peer in the Subsonic/Jellyfin field. Weakness: newer means less shared muscle memory; treat as peer, not settled default.

Caching, on-device, DAP

Sonamp-class caching — Strength: aggressive start-fast / pre-cache pattern collectors praise over cellular. Weakness: product homepage TBD — treat as pattern until Comms confirms a software product (not Sonance hardware).
Local-files / on-device players — Strength: phone-as-DAP without a hub narrative; files in the pocket, honest and simple. Weakness: second-library risk if the pocket copy is not a projection of the hub (TBD / n/a).
Android / portable DAP players — Strength: dedicated portable playback of owned files for travel subsets. Weakness: subset vs NAS canonical — which truth wins on write? (URL TBD)
Poweramp / USB Audio Player Pro — Strength: on-device Android library playback with EQ/format craft. Weakness: desk and server identities stay elsewhere.

DJ-cloud mobile prep (alternate plane)

rekordbox Cloud — Strength: prep on phone via DJ-ecosystem cloud when stage workflows already live there. Weakness: trade is a second catalog tax — name it, don’t pretend it’s the default owned-archive thesis.
MIXO — Strength: cross-DJ / cloud prep bridging DJ apps and mobile — demand validation that phone prep matters. Weakness: second-catalog tax and paid fragmentation again.

Ecosystem & classic Subsonic clients

Finamp — Strength: popular Jellyfin music phone surface when the household already standardized on Jellyfin. Weakness: UX inherits companion quality; you’re still projecting a server catalog.
Tempo / DSub / Ultrasonic / play:Sub — Strength: earlier-generation Subsonic phone clients with historical density and muscle memory. Weakness: polish and offline expectations often lag the current Android high bar. play:Sub lives on the Subsonic apps list; no separate product homepage.

Networking / away-from-home

Here’s how I see this layer: reach the same hub catalog off-LAN without copying the library into a cloud music service. Good networking tools; wrong tax when the promise was a music suite. Architecture proof (not this directory’s hero): Iroh inside Tape.

LAN-only — Strength: correct default for owned libraries; no remote tax, disks feel local. Weakness: leave the house and the lifestyle pauses unless you add another layer.
Port forward + reverse proxy + DDNS (Caddy / Traefik / nginx) — Strength: classic remote exposure of a media server when you own the ops skill. Weakness: open-internet risk and an ops skill gate before playback.
Tailscale — Strength: the overlay I see named most often next to Navidrome/Jellyfin/Plex stacks — zero-config mesh so the phone treats home services as local. Weakness: sidecar app + identity on every device; wrong tax when the promise was a music suite.
Headscale — Strength: self-hosted Tailscale control plane for people who want the same overlay without Tailscale’s coordination server. Weakness: you now operate the control plane too.
Netbird / ZeroTier — Strength: other mesh/overlay products people actually install to reach a home music server. Weakness: same sidecar gravity — excellent homelab tools, still not a listening product.
WireGuard — Strength: lean VPN tunnels into the homelab; named constantly beside commute clients, often underneath Tailscale. Weakness: you’re a part-time network operator; cellular + VPN + cache fail together.
Cloudflare Tunnel — Strength: outbound tunnel without inbound ports. Weakness: third-party path and config surface between you and the catalog.
ngrok — Strength: quick temporary tunnels for testing a server from outside. Weakness: situational, not a commute lifestyle.
Iroh — Strength: embedded P2P pairing aimed at own devices inside the music suite — stance/proof for device connection without making mesh the product. Weakness: not a substitute for tagging, playlists, or server ops; architecture proof, not series hero.
Dropbox / Syncthing sync-folder second copy — Strength: mobile strategy via a synced tree when VPN feels like the product. Weakness: works until it encodes a second truth.

DJ / performance

Here’s how I see this layer: stage prep and show software — cues, grids, hardware, the night’s confidence. A different job from rediscovering your own catalog, and a different job from carrying playlists between apps.

rekordbox — Strength: performance preparation and show workflows — stage strengths deserve respect. Weakness: cloud prep is a separate plane; personal-library continuity and path moves still hurt outside the show.
Serato — Strength: crate-centric DJ performance library with hardware and show confidence. Weakness: crates/paths/portability threads — manager sync and folder moves can orphan work.
Traktor — Strength: DJ collection and performance surface with smart-list / migration narratives in real workflows. Weakness: migration hell and collection handoff remain unpaid when the desk library isn’t Traktor.
Engine DJ / VirtualDJ / djay — Strength: alternate performance surfaces in some workflows. Weakness: more destinations mean more export seams — still no vs-table.
Mixxx — Strength: open performance deck with serious local analysis (BPM/key lineage shared with KeyFinder). Weakness: still a stage/listen app; crates and tags may not be the hub catalog.

Analysis & key (prep, not the show)

Specialists our DJ-analysis roadmap named instead of pretending Rekordbox built-in is enough.

Mixed In Key — Strength: paid harmonic-mixing reference bar — batch key/energy into tags DJs actually trust. Weakness: another app before the stage DB; not a library manager.
KeyFinder — Strength: local OSS batch key estimation that writes files; historical “folder in, tags out.” Weakness: dated desktop; Mixxx now carries the algorithm for many people.
Lowkey — Strength: newer local batch key/BPM → ID3 so Rekordbox/Serato see it without a cloud upload. Weakness: small shared muscle memory; still a sidecar before the hub.

Playlists / export

Here’s how I see this layer: build ordered listening as labor; carry that work to phone and/or stage apps without forking the catalog. Performance destinations live in DJ / performance.

Smart lists, bridges, formats

Apple Music / iTunes smart playlists — Strength: historic rule engines that still feed XML export stories. Weakness: reliability pain at scale; Date Added and identity loss on re-import.
MIXO — Strength: move playlists/libraries across DJ ecosystems — demand validation that bridges matter. Weakness: second-catalog tax and paid fragmentation.
Lexicon export/sync — Strength: manager ↔ DJ bridge to keep hygiene and performance in sync without living only in the stage DB. Weakness: sync breaks still cost crates when paths fight; another paid seat.
M3U / XSPF paths — Strength: lowest-common-denominator playlist interchange almost everything can read. Weakness: break when mount points / NAS roots change (n/a format).
XML / crate exchange utilities — Strength: one-off bridges between library apps when nothing else speaks. Weakness: absurd pipelines = unpaid engineering (URL TBD).

Mobile playlist labor

Symfonium / Plexamp playlists + offline — Strength: sequence on phone for life; easy to cache and actually use on the commute. Weakness: fragile round-trip into DJ apps — export remains the seam.

Multi-room / streamers

Here’s how I see this layer: whole-home playback and dedicated streamer boxes — rooms in sync, a Pi as a DAC endpoint — not the commute phone path and not library hygiene. Adjacent to serving; not a substitute for a hub catalog. No dedicated essay in this series (lateral).

Sendspin — Strength: open whole-home sync (Open Home Foundation) aimed at audio + artwork across rooms, often via Music Assistant. Weakness: a multi-room protocol is not desk→phone continuity; HA gravity can become the product.
moOde Audio — Strength: Raspberry Pi streamer OS with a serious web UI for local and renderer playback. Weakness: appliance listening in the room; the phone and the tag pipeline still live elsewhere.
piCorePlayer — Strength: RAM-boot Squeeze/Lyrion player (and optional LMS host) that people trust through power pulls. Weakness: Lyrion-lineage world; not the default Navidrome + Symfonium commute stack.
Sonos / Chromecast / UPnP (Rygel) — Strength: room endpoints people already use when the phone is a controller, not the speaker. Weakness: renderer identity is not catalog identity; groups and caches drift from the hub.

Hybrid stacks

Here’s how I see this layer: specialists get you most of the way; living across them still asks for unpaid integration. These constellations are not failed attempts to be a suite — they are proof. Open and closed coexist.

Navidrome + Symfonium + Feishin — Strength: open-leaning pride stack — lean server + Android daily driver + desk/web client for DIY owned-library listening without a storefront. Weakness residual: tagging, backups, remote policy, DJ export.
Plex + Plexamp — Strength: closed polish reference loop (pre-cache, sonic, phone UX). Weakness: management may still need another tool; you’re inside one ecosystem’s gravity.
Navidrome ∥ Plex (parallel) — Strength: two backends on purpose — lean music index + broader media appliance, each loved for a job. Weakness: two authorities; lifetime math and which-truth-wins arguments never fully leave.
Jellyfin-first + phone client — Strength: music as a module on an existing video appliance. Weakness: UX inherits client quality; music is rarely the appliance’s first love.
foobar2000 + USB / synced phone folder — Strength: anti-server honesty; listening craft supreme. Weakness: continuity is manual; second-library risk when the pocket copy drifts.
MusicBee-as-whole-Windows-home — Strength: quiet variant — one Windows app as emotional center ± occasional phone sync. Weakness: dual-library drift when the handset diverges.
Lexicon + rekordbox/Serato ± MIXO/rekordbox Cloud — Strength: hygiene beside performance; protect stage tools from being the only DB. Weakness: paid fragmentation and sync/crate seams still show up on bad weeks.
iTunes/Apple Music smart lists → DJ XML — Strength: historic smart-list labor still feeding performance apps. Weakness: half-working bridges that ship weekends — reliability and identity loss at scale.
Dropbox / Syncthing synced music folder — Strength: sync-as-mobile-strategy when VPN feels like the product. Weakness: encodes second truth the moment both sides write.
NAS canonical + travel DAP subset — Strength: subset in pocket; NAS remains home authority. Weakness: dual library — which truth wins on write? (n/a / TBD)
Desk + server + WireGuard / Tailscale / Headscale + phone client — Strength: full franken lifestyle that can feel complete on a good LAN day. Weakness: completeness theater until one seam fails — cellular + VPN + cache.
beets + Navidrome + piCorePlayer + Symfonium — Strength: file pipeline + lean index + room streamer + commute client. Weakness: three listen surfaces; ratings and playlists still have to pick an authority.
Music Assistant + Sendspin + Home Assistant — Strength: whole-home sync when the house is already an HA node. Weakness: smart-home gravity; local files can become one source among storefronts.
Lidarr + Soularr + slskd → intake folder — Strength: wanted-library automation that drops files where a hub can scan — the acquisition stack our plugin research mapped instead of shipping Soulseek in-process. Weakness: three daemons plus legal/ops posture; Inbox still has to become identity.

“Almost one catalog feeling” is not almost a brand. Keep a quiet frankenstack if crates arrive, caches tell the truth, and remote nights are not incident response.

The State of Self-Hosted Music Listening — flagship state-of-play
Iroh inside Tape — networking stance / architecture proof only

If you maintain five truths so the same music can follow you from desk to phone to set, that is a cohesion problem — not a failure of any specialist named above.

This catalog is research for that build — not a ranking, not a feature war. I’m not asking you to abandon rekordbox on stage if that still wins the night. At the desk, Tape is the home — it replaces foobar2000-class players rather than sitting beside them. Trial on Tape is twenty hours of use or thirty days, then a license — V1 at $100, or Lifetime at $120 early bird ($150 later).

Want something added or corrected? Open a pull request on the public landscape repo.

Tape Music Hub is a local music library manager and personal server with a peer-to-peer phone companion. See how it works