Beatbump

A privacy-focused alternative to YouTube Music’s surveillance-heavy client, honestly reviewed — including the part where it stopped working.

TL;DR

• What it is: An open-source (AGPL-3.0) alternative frontend for YouTube Music — the same catalog, without Google’s ad tracking, built with SvelteKit and deployed via Cloudflare Workers [1].
• Who it’s for: Privacy-conscious users who want YouTube Music’s catalog without YouTube Music’s data collection. Technically comfortable self-hosters who can maintain their own instance.
• Development status: Discontinued. The README states plainly: “Beatbump is no longer being actively developed, this is due to the changes made by YouTube.” The GitHub repository is archived [1][merged profile]. This is the most important fact in this review.
• Cost savings vs. YouTube Music Premium: YouTube Music Premium runs $10.99/mo. Beatbump is free and routes your requests through its own server proxy, so YouTube never sees your IP or account — but whether it still streams reliably depends entirely on whether the YouTube Music API changes have been worked around [1][merged profile].
• Key strength: Clean, feature-complete UI with automix, group sessions, P2P sync, and mobile background play — when it worked, it genuinely matched YouTube Music’s frontend quality [merged profile].
• Key weakness: Archived and unmaintained. YouTube’s API changes killed active development. Bugs and breakages are expected and will not be fixed [merged profile][1].

---

What is Beatbump

Beatbump is a privacy-respecting alternative frontend for YouTube Music. It sits between you and Google: you browse and play music through Beatbump’s interface, Beatbump fetches data from YouTube Music’s internal API, and your IP and browser fingerprint never touch YouTube’s servers directly [merged profile][1].

The project was built by a developer known as SnuffyDev using SvelteKit, hosted on Cloudflare Workers, with a custom wrapper around the YouTube Music API [merged profile]. The official instance lives at https://beatbump.io, and a handful of community-run mirrors exist for Clearnet, Tor, and I2P access [merged profile].

The motivation is simple: YouTube Music is a surveillance product. The app collects listening history, device data, and behavioral patterns to feed Google’s ad targeting. Beatbump gives you the same catalog — 100 million tracks, YouTube Music’s algorithm-driven mixes, artist pages, playlists — without any of that data collection [1][merged profile].

The architecture is not a media downloader or a local library tool. It’s a frontend proxy. Beatbump doesn’t host audio files; it streams them from YouTube’s CDN through its proxy server, which is why YouTube’s API changes broke it [merged profile].

As of this review, the project has 1,133 GitHub stars, 94 forks, and 100 open issues — with the repository archived in October 2025, meaning no new contributions will be accepted [1][merged profile].

---

Why people choose it

The primary draw is privacy without sacrifice. Most privacy-focused music tools ask you to give something up — you either pay for a privacy-respecting service like Tidal, switch to a different catalog entirely (Bandcamp, Spotify via Spotube), or run a local library with Navidrome/Jellyfin and accept you’ll miss the long tail of content. Beatbump’s proposition was different: keep using YouTube Music’s 100-million-track catalog, lose the surveillance [1].

AlternativeTo users consistently describe it as “fast, simple, and free” [1]. The zero-registration requirement matters — you don’t create an account, which means there’s no account to be compromised or subpoenaed [1]. Your listening history stays in your browser’s IndexedDB, not on Google’s servers.

The group sessions feature — a WebRTC mesh that lets multiple users in different locations listen to the same queue simultaneously — was genuinely unusual for a self-hosted tool of this type [merged profile]. Most privacy frontends are solo-use utilities. Beatbump treated music listening as a social activity.

The mobile background playback addressed one of the most common complaints about browser-based music players: that audio stops when you switch apps. Beatbump worked around this on iOS (with caveats noted for version compatibility) and Android [merged profile].

The “why people choose it” section is short because the third-party review ecosystem for Beatbump is thin. It never attracted the kind of dedicated review coverage that tools like n8n or Bitwarden get. It was a niche tool used by people who were already privacy-conscious enough to seek out alternative frontends — not a product marketed aggressively to a mainstream audience.

---

Features

From the README and project documentation:

Music playback:

• Automix and autoplay for uninterrupted listening sessions [merged profile]
• Search across artists, songs, playlists, and albums [merged profile]
• Audio-only playback (no video, which reduces bandwidth) [merged profile]
• Background play on mobile — documented as working on iOS 15.6+, with caveats for newer iOS updates [merged profile]

Library management:

• Local playlists stored in-browser via IndexedDB — no account required, no server-side data [merged profile][1]
• Favorites for individual tracks [merged profile]
• P2P library synchronization across devices using WebRTC — your library data syncs directly device-to-device, not through a central server [merged profile]

Social / collaborative:

• Group Sessions via WebRTC mesh networking — listen in sync with others, no central server required for the session coordination [merged profile]

Privacy architecture:

• Custom wrapper around YouTube Music’s internal API [merged profile]
• Users’ requests never touch YouTube’s servers directly [1]
• No registration, no accounts, no login [1]

Deployment:

• Docker image available on DockerHub [merged profile]
• Docker Compose setup for self-hosting [merged profile]
• Official instance at https://beatbump.io hosted on Cloudflare Workers [merged profile]
• Community-run mirrors for Tor and I2P access [merged profile]

What it doesn’t do:

• No podcast support
• No video playback (audio only)
• No Last.fm scrobbling (unlike some alternatives)
• No offline download — it’s a streaming proxy, not a downloader
• REST API is documented as incomplete and work-in-progress [merged profile]

---

Pricing: SaaS vs self-hosted math

YouTube Music Premium:

• Individual: $10.99/month
• Family (up to 6): $16.99/month
• Student: $5.49/month
• Free tier: exists, but includes ads and no background play

Beatbump (self-hosted):

• Software: $0 (AGPL-3.0)
• Hosting: $0 if you use the official instance or a community mirror; $3–6/mo on a VPS if you run your own
• Catch: the tool is discontinued, so any instance you run may stop working without warning if YouTube changes its API again

The math that doesn’t quite work: Unlike the Zapier-to-Activepieces comparison where the savings are clean and the alternative is maintained, Beatbump’s savings come with a fundamental asterisk. You’re not paying $10.99/month for YouTube Music Premium — but Beatbump doesn’t give you what YouTube Music Premium gives you either. Premium includes offline downloads, background play in the official app, and a guaranteed, maintained product. Beatbump gave you a privacy-respecting front-end that could break at any time, and now it has [merged profile].

If you want to escape YouTube Music’s surveillance for free, Beatbump’s archived codebase still exists. Whether it streams correctly on any given week is a different question.

---

Deployment reality check

Self-hosting is documented but frozen:

The Docker setup is straightforward on paper — docker-compose up and the app runs on ports 443/3000 [merged profile]. The DockerHub image exists at snuffydev/beatbump. But the last meaningful commit is from before the archive date (October 2025), and the README itself warns: “Beatbump is going through a major rewrite, so errors, bugs, and other problems may happen at random” — a warning that predates the abandonment notice [merged profile].

What you actually need:

• Docker and docker-compose
• A VPS or local machine (the Cloudflare Workers deploy model used by the official instance isn’t replicated in the self-host docs)
• Comfort with the possibility that it stops working and no fix is coming

The API problem: Beatbump wraps YouTube Music’s internal (unpublished, unofficial) API. YouTube changes this API without notice — that’s exactly what killed the project [merged profile]. Running your own instance doesn’t protect you from this; it just means you’re running the same broken code on your own hardware instead of the developer’s.

Community mirrors: The README lists six community instances: Clearnet mirrors, a Tor onion, and an I2P address [merged profile]. Uptime monitoring exists at https://stats.uptimerobot.com/9PnmRfz6Gm. How many of these still work, and how long they’ll stay up given the project’s archived status, is unknown.

Realistic expectation: If you deploy Beatbump today, you’re running archived software against an unofficial API. It may work perfectly for months. It may stop working tomorrow. There’s no maintainer to fix it.

---

Pros and Cons

Pros

• Genuine privacy protection. YouTube’s tracking never sees your requests — the proxy model is sound, and no account is required [1][merged profile].
• Full YouTube Music catalog. 100 million tracks, not a curated subset [merged profile][1].
• No ads. YouTube Music’s free tier runs ads; Beatbump strips them entirely [1][merged profile].
• P2P architecture for personal data. Library sync happens device-to-device via WebRTC, not through a central server [merged profile].
• Group Sessions. Genuinely unusual feature — synchronized listening with friends, no shared account required [merged profile].
• Mobile background play. Solved a real limitation of browser-based players [merged profile].
• AGPL-3.0 licensed. If you fork it and maintain it yourself, you can — the source is yours [1][merged profile].
• Multiple access methods. Tor and I2P mirrors make it accessible in restricted environments [merged profile].

Cons

• Discontinued. This is not a minor caveat. The project is archived, unmaintained, and will not receive bug fixes or API compatibility updates [merged profile][1]. Deploying it means accepting a ticking clock.
• Unofficial API dependency. The entire product depends on reverse-engineered YouTube Music internals. YouTube already changed these enough to kill development once [merged profile].
• 100 open issues, no fixes coming. The GitHub issue tracker shows 100 unresolved issues as of archival [1]. These will stay open.
• Incomplete documentation. The API docs are described as “temporary, incomplete, and in-progress” in the README — and they’ll never be completed [merged profile].
• No Last.fm scrobbling. A notable gap for users who track their listening history [merged profile].
• Audio only. If you want music videos, YouTube Music’s catalog includes them. Beatbump doesn’t serve video [merged profile].
• No offline mode. It’s a streaming proxy, not a downloader. No internet, no music [merged profile].
• Small community. 1,133 GitHub stars is modest for a self-hosted tool. The community never reached the critical mass needed to sustain the project after the developer stepped away [1][merged profile].

---

Who should use this / who shouldn’t

Consider Beatbump if:

• You’re a technically comfortable user who wants to try a privacy-focused YouTube Music frontend and accepts that it may break.
• You want to run one of the existing community mirrors for personal use and are comfortable with zero maintenance guarantees.
• You’re a developer interested in studying the SvelteKit/Cloudflare Workers architecture or forking the project to maintain your own version.
• You already know Docker and want a quick experiment, not a production music solution.

Skip it if:

• You want a reliable daily music player. Discontinued software on an unofficial API is not a dependable foundation for something you use every day.
• You’re non-technical. There’s no SaaS version to fall back on, no support, and no community actively fixing problems.
• You want offline downloads, Last.fm scrobbling, or any feature the README marks as incomplete.
• You’re evaluating tools for a small team or multiple users — the maintenance burden falls entirely on you, and the upstream has walked away.

What to use instead (see next section).

---

Alternatives worth considering

Given that Beatbump is discontinued, the more useful question is what replaced it:

• Piped — Active, open-source alternative frontend for YouTube (video + audio), maintained, self-hostable. For YouTube rather than YouTube Music specifically, but the overlap is significant.
• Invidious — The older, more established alternative YouTube frontend. Video-focused, large community, actively maintained [merged profile].
• ViMusic / RiMusic — Android-native alternative YouTube Music clients. Not self-hosted web apps, but actively maintained and do what Beatbump did on mobile. RiMusic is a maintained fork of ViMusic. Worth checking if Android is your primary use case.
• Spotube — Open-source Spotify client that routes through YouTube or Piped for actual audio. Different catalog framing but similar privacy philosophy.
• Navidrome — If you want to move entirely away from streaming services, Navidrome is a self-hosted music server with excellent Subsonic compatibility. Requires you to own your music files.
• Jellyfin — Full media server including music. Heavier than Navidrome but more versatile if you’re already in the Jellyfin ecosystem [2].
• Funkwhale — Federated, self-hosted music streaming. Social features built in. Different catalog model (your own library + federation), not a YouTube Music proxy.

The honest recommendation for someone who specifically wants YouTube Music’s catalog with privacy: ViMusic or RiMusic on Android is currently the most maintained path. For a web-based, self-hostable option in this category, there’s a gap that Beatbump used to fill and nothing active has cleanly replaced yet.

---

Bottom line

Beatbump was a good idea executed well enough to reach 1,133 GitHub stars and a small but loyal user base. The privacy architecture was sound, the SvelteKit frontend was clean, and the group session feature was genuinely interesting. But it built its entire foundation on an unofficial, reverse-engineered API that YouTube controls — and YouTube changed it. The project is now archived, the maintainer has moved on, and the README leads with a discontinuation notice.

If you’re looking for a maintained, privacy-respecting music experience, Beatbump is not the answer in 2026. It’s a useful reference implementation and a cautionary example of the fragility of alternative frontends that depend on unofficial API access. The self-hosted media category has better, actively maintained options — they just don’t give you YouTube Music’s specific catalog through a web proxy.

If you want help escaping streaming service surveillance and building a self-hosted music stack that won’t disappear when an upstream API changes, that’s exactly what upready.dev helps founders set up.

---

Sources

1. AlternativeTo — Beatbump listing (9 likes, 1 review, GitHub: 1,129 stars, archived Oct 2025). https://alternativeto.net/software/beatbump/about/
2. hostedsoftware.org — Media Streaming Service category listing (includes Beatbump: “Privacy-respecting alternative frontend for YouTube Music”). https://hostedsoftware.org/categories/media-streaming-service/
3. peterhil/delightful-humane-design — Codeberg (curated humane design resources list including Beatbump under privacy section). https://codeberg.org/peterhil/delightful-humane-design

Primary sources:

• GitHub repository (archived): https://github.com/snuffydev/beatbump (1,133 stars, AGPL-3.0, archived)
• Official instance: https://beatbump.io
• DockerHub image: https://hub.docker.com/r/snuffydev/beatbump
• Uptime monitoring: https://stats.uptimerobot.com/9PnmRfz6Gm