Audio and podcasting decision
Apple Music
A capable developer can build or self-host a minimal personal streaming service (search, play, playlists) quickly using existing open-source projects, but reproducing Apple Music's licensed catalog, exclusive content, and deep platform integrations is not realistic.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Search tracks, manage a personal library and playlists, stream playable audio to a web or mobile client, and control playback (play/pause/seek/queue).
What it still won’t have
- Licensed commercial music catalog and exclusive releases
- Cross-device cloud-synced library integrated with Apple ecosystem
- Curated editorial playlists and human curation
- Deep platform integrations (Siri, Apple Watch, system-level playback on iOS) and DRM-protected streams
What remains hard
- Brand trust
84% of top U.S. companies use Mac at scale. 1
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a self-hosted personal music streaming server using Go (or Node) + SQLite, with a React web client. In scope: scanning local music files to import metadata and cover art; storing tracks, playlists and users in SQLite; serving audio streams over HTTP with range requests and optional on-the-fly transcoding; REST API for search, library and playlist management; a single-user React web player with playback controls, queue, and simple offline caching. Out of scope: purchasing or licensing commercial catalogs, DRM content, and third-party streaming integrations. Include error handling, unit tests for API endpoints, and a Docker Compose config for local deployment.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 4 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score64
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 4
Every page the run actually retrieved.
- official productApple
- official productApple homepage
- open sourcenavidrome/navidrome
- open sourcekoel/koel
Integrity checks
What held up, and what did not.
