Audio and podcasting decision
Flow State Radio
A capable technical user can build and self-host a small internet radio service using existing open-source media servers and player components; the vendor's hosted audience and brand cannot be reproduced.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off140 h to build
$0/mo6 h/mo upkeep
No published price to break even against.
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. All Flow State Radio alternatives, with the arithmetic →
What a replacement has to do
- Ingest live or scheduled audio, encode/stream to listeners, host a web audio player, manage a small schedule/CMS, and provide analytics/basic logging.
What it still won’t have
- Existing brand, listeners and social audience
- Proprietary curated programming and curation workflows
- Dedicated mobile apps or integrations the vendor may provide
- Any commercial licensing/rights the vendor holds
- Operational support and uptime SLAs from a hosted provider
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Flow State Radio does not publish a price we could read, so there is nothing to compare against. What building costs is below.
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 internet radio stack using Docker on a single VPS (Debian/Ubuntu). Stack: MediaMTX (or SRS) for ingest and streaming, FFmpeg for encoding/transcoding, Node.js + Express + Postgres for a lightweight CMS/scheduler API, and React for a web player UI using react-player. Core features: accept live RTMP/RTSP or scheduled file playback, transcode to HLS/LL-HLS and AAC streams, present a web player with current show metadata, an admin UI to upload shows and set a schedule, basic listener metrics and health checks. Out of scope: mobile native apps, multi-region CDN setup, user accounts/billing. Include Docker compose, HTTPS via Let's Encrypt, robust error handling, unit/integration tests for API and player integration, and deployment/run instructions.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 5 cited sources+3
- Evidence score86
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 · 5
Every page the run actually retrieved.
- official productFlow State Radio
- open sourcebluenviron/mediamtx
- open sourceossrs/srs
- open sourceFFmpeg
- open sourcereact-player
Integrity checks
What held up, and what did not.
