Audio and podcasting decision
SoundCloud Go Plus
A technical user can build a useful, narrow SoundCloud-like service (streaming + upload + search) themselves, but replicating the full production product (catalog, apps, discovery, scale, licensing) 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
- Host audio files, provide a web audio player, allow search/discovery, and enable uploads with user accounts.
What it still won’t have
- Large catalog and existing user community
- Mobile apps and platform-specific integrations
- Advanced discovery/recommendation algorithms
- Licensing deals and copyrighted catalogue
- Global scale and reliability engineering
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 12 seats.
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 minimal self-hosted music streaming service using Node.js (Express) backend, PostgreSQL for metadata, Elasticsearch (or PostgreSQL FTS) for search, AWS S3 for audio storage, CloudFront for CDN, and a React web frontend. In scope: upload endpoint with server-side validation, background transcoding (FFmpeg) producing streaming-friendly formats, storage and signed-URL delivery from S3/CloudFront, a searchable track listing API, user signup/login (JWT), and a web player that streams tracks and shows metadata. Out of scope: social features (comments/likes), in-app payments, large-scale recommendation engine, mobile native apps, and licensing negotiations. Include automated tests for upload and playback endpoints, error handling for failed transcoding/storage, and deployment scripts (Terraform or simple Docker + deployment docs).
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 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 · 3
Every page the run actually retrieved.
- official productSoundCloud — official product page
- open sourcenavidrome/navidrome
- open sourcekoel/koel
Integrity checks
What held up, and what did not.
