BotWave
FM broadcasting system with server-client architecture for managing multiple Raspberry Pi transmitters remotely.
- GitHub stars
- 142
- License
- GPL-3.0
- Latest release
- v1.2.13-ostodes
11 October 2026 - Last commit
- 11 October 2026
- Runs on
- Python
Commits per month, last 12 months
794 commits
How to self-host BotWave
BotWave runs on Python. The project's own install guide is the place to start; most people put it on a small server with Docker and a reverse proxy for HTTPS.
- Get a server: a home server, a VPS, or a managed app host.
- Install it the way the project's docs describe, usually with Docker Compose.
- Put it behind HTTPS and set up backups before you add real data.
- Update it regularly. Watch the project's releases.
Similar apps
- Navidrome Music Server
Modern Music Server and Streamer, compatible with Subsonic/Airsonic.
- koel
Personal music streaming server that works.
- Beets
Music library manager and MusicBrainz tagger (command-line and Web interface).
- Audiobookshelf
Audiobook and podcast server. It streams all audio formats, keeps and syncs progress across devices. Comes with apps for Android and iOS.
- Mopidy
Extensible music server. Offers a superset of the mpd API, as well as integration with 3rd party services like Spotify, SoundCloud etc.
- Snapcast
Synchronous multiroom audio server.
Questions
Is BotWave free?
Yes. BotWave is open source under the GPL-3.0 license, so you can use it without paying for a license. You pay only for the server it runs on.
Can I self-host BotWave?
Yes. BotWave runs on Python. Follow the install guide in the project's documentation, or use a host that installs it for you.
Is BotWave still maintained?
The last change to BotWave's code was on 11 October 2026, with 794 commits in the last 12 months.
Topics
App data from awesome-selfhosted (CC BY-SA 3.0), stars and activity from GitHub.