Hyperpipe

Open-source privacy frontends, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: A self-hostable, privacy-respecting frontend for YouTube Music — strips tracking, serves content without an account, runs on your own server [4].
• Who it’s for: Privacy-conscious users who want to listen to YouTube Music without Google’s surveillance apparatus. Not for teams, not for businesses — this is a personal privacy tool [3][4].
• Cost savings: YouTube Music Premium costs $10.99/mo. Hyperpipe lets you access the free-tier YouTube Music catalog through a privacy proxy, self-hosted on a VPS that costs $5/mo or less.
• Key strength: Zero tracking, no Google account required, automatic redirect via LibRedirect, multiple community-maintained instances [4].
• Critical weakness: The project is archived and discontinued. The Codeberg repository carries a prominent warning: “Hyperpipe has been discontinued.” No new commits, no issue responses, no maintenance [4].

---

What is Hyperpipe

Hyperpipe is a Vue.js web application that acts as a privacy-preserving frontend for YouTube Music. Instead of loading music.youtube.com — which tracks every play, search, and skip — you load a Hyperpipe instance. It communicates with YouTube’s InnerTube API and the Piped project’s infrastructure on your behalf, returning audio and metadata without exposing your IP address or browser fingerprint to Google [4].

The concept is well-established in the privacy community. The same pattern exists for regular YouTube (Invidious, Piped), Reddit (Redlib), Twitter (Nitter), and dozens of other platforms. Hyperpipe is specifically scoped to YouTube Music — the streaming-music product Google built to replace Google Play Music [3].

The project was created by Shiny Nematoda and lives on Codeberg rather than GitHub — itself a signal of the privacy-first values behind the project. It uses VueJS for the frontend, shaka-player for media playback, and PeerJS for some peer-to-peer capabilities. The Codeberg repository sits at 164 stars and 27 forks [4].

The number that matters more than the star count: the repository is archived. The README opens with a warning box in bold: “Hyperpipe has been discontinued. Please see Similar Projects for alternatives.” No date is given for when this decision was made, but the repo is read-only — no issues, no pull requests, no new commits are possible [4].

This review covers what the project was and what it offered, with the explicit understanding that you are looking at finished software. For a self-hosted personal tool you run and maintain yourself, “archived” is less catastrophic than it sounds for a commercial product. But you need to know going in.

---

Why people choose it

Privacy is the single reason. There is no other pitch.

YouTube Music has no privacy-friendly official client. If you use it without a frontend proxy, Google tracks your listening history across sessions, correlates it with your search and watch data, and uses it to build an advertising profile. Even if you’re on the free tier and can live with ads, the surveillance is the product [3].

Hyperpipe appears on LibRedirect’s curated list of alternative frontends — the browser extension that automatically redirects YouTube Music URLs to a Hyperpipe instance of your choice. Being on that list means Hyperpipe was evaluated and accepted as a working, open-source, self-hostable alternative [3]. The Privacy Guides community cites it alongside Invidious and FreeTube as the short list of legitimate YouTube Music privacy frontends available [3].

The secondary reason people choose Hyperpipe specifically is that Invidious and FreeTube focus on regular YouTube video, not music. Hyperpipe fills the music-specific gap in the privacy frontend stack [3][4].

What you do not choose Hyperpipe for: discovery, curated playlists, offline downloads, smart recommendations, podcasts, or any of the experience features that justify a music streaming subscription. Hyperpipe is a playback interface, not a streaming service.

---

Features

Based on the Codeberg repository and README [4]:

Playback and browsing:

• Browse and play YouTube Music catalog without a Google account
• Search artists, albums, songs, and playlists
• Audio playback via shaka-player (a mature Google-developed player library, Apache-2.0 licensed)
• Queue management via SortableJS drag-and-drop
• Playlist support

Privacy and access:

• All requests proxied through the instance — your IP never touches YouTube Music directly
• No account required to use
• Multiple public community instances available (listed at hyperpipe.codeberg.page)
• Automatic redirect via LibRedirect browser extension [4]
• Redirector extension configuration documented — wildcards for all music.youtube.com/* URLs [4]

Themes:

• Dracula theme
• Nord theme
• VueJS default theme [4]

Localization:

• Weblate integration for community translation — Turkish and other languages contributed [4]

Self-hosting:

• Docker deployment with environment variables for API URL configuration [4]
• Standard npm build pipeline (dev: npm run dev, production: npm run build)
• npm run host for LAN-accessible dev server [4]

What it does not have:

• Offline listening or downloads
• Account sync across devices
• Smart recommendations or personalized radio
• Podcast support
• A mobile native app (browser-only)
• Active maintenance or bug fixes [4]

---

Pricing: SaaS vs self-hosted math

There is no SaaS version of Hyperpipe. This is purely self-hosted software under the AGPL-3.0 license.

YouTube Music for comparison:

• Individual: $10.99/mo
• Family (up to 6 accounts): $16.99/mo
• Student: $5.49/mo
• Free tier: available with ads and limited features

Hyperpipe self-hosted:

• Software license: $0 (AGPL-3.0) [4]
• Hosting: $0 if you use one of the community public instances
• Hosting: $3–6/mo on a shared VPS if you run your own instance

The honest math: Hyperpipe gives you access to the YouTube Music catalog — the same songs, the same search — without paying $10.99/mo. But it gives you the free-tier experience with no account, not the premium experience. You still hear ads if the proxied content includes them. You don’t get background playback on mobile (since it’s a browser app), lyrics, or downloads.

If you’re currently paying $10.99/mo for YouTube Music Premium primarily for the ad-free listening and you’re comfortable losing smart recommendations, the self-hosted option saves you that full amount. If you value the premium features, Hyperpipe is not a replacement — it’s a different tool.

The other value proposition is data: using Hyperpipe on a community instance costs $0 and removes Google from your listening data entirely, with no VPS cost. The tradeoff is trusting the instance operator instead of trusting Google — a trade many privacy-focused users are willing to make [3].

---

Deployment reality check

The README documents two paths: use an existing public instance, or run your own [4].

Public instances:

• Listed at hyperpipe.codeberg.page
• Zero setup required — open browser, use it
• You trust the instance operator’s privacy practices
• Instance may go offline; the operator has no obligation to keep it running, especially on a discontinued project

Self-hosted:

1. A Linux server or VPS with Docker installed
2. Pull the Docker image or clone the repo and run npm install && npm run build
3. Environment variables to point at a Piped API backend (since Hyperpipe proxies through Piped’s infrastructure)
4. Reverse proxy (nginx or Caddy) if you want HTTPS

The setup is lighter than most self-hosted apps reviewed here — no database, no persistent storage, no worker processes. It’s a static Vue.js app that calls external APIs. A working instance can be running in under 30 minutes on a fresh VPS [4].

What can go sideways:

The bigger issue is not the setup but the dependency chain. Hyperpipe proxies through Piped, which in turn hits YouTube’s InnerTube API. Google routinely updates InnerTube in ways that break third-party clients. Piped has historically patched these breakages within days, but since Hyperpipe is discontinued, any future Piped API changes that require updates to Hyperpipe itself will not be fixed. The project’s own README acknowledges this explicitly in the original disclaimer: “STUFF THAT USED TO WORK MAY BREAK IN THE FUTURE.” [4]

The discontinuation makes this more than a caveat — it makes it a timeline. Community instances may stay up for months or years on the last working version, but once YouTube or Piped makes a breaking change that the Hyperpipe layer cannot handle, those instances go dark.

Bottom line on deployment: Easy to run today, uncertain shelf life. Fine for personal use where you accept the risk of it breaking. Not appropriate for anything you need to rely on.

---

Pros and Cons

Pros

• Genuinely privacy-respecting. No Google account, no tracking, no behavioral data sent to YouTube Music’s servers. This is the core value and it works [3][4].
• AGPL-3.0 license. Free to self-host, fork, and modify [4].
• Lightweight. No database, no heavy infrastructure — a static app proxying an API. Runs on the smallest VPS [4].
• LibRedirect integration. Automatic redirect from music.youtube.com to your chosen instance requires a one-time browser extension install [4].
• Multiple themes. Dracula and Nord themes for those who care about this [4].
• Community instances exist. Zero-effort option for users who don’t want to run their own server [4].
• Part of an established pattern. The privacy-frontend approach is proven — Invidious has been running for years. Hyperpipe followed the same model [3].

Cons

• Discontinued. This is the most important fact in this review. The project is archived. No new features, no bug fixes, no security patches [4].
• No mobile app. Browser-only. No background playback on mobile without browser-specific workarounds.
• Depends on Piped. If Piped changes its API, Hyperpipe breaks and nobody will fix it [4].
• Depends on YouTube. If YouTube changes InnerTube, Piped may take time to patch, and Hyperpipe is downstream of that entire chain [4].
• 164 stars on Codeberg is a small community by any measure. It was never a mainstream project [4].
• Missing premium features. No downloads, no lyrics, no smart recommendations, no cross-device sync.
• No official instance. The primary instance (hyperpipe.surge.sh) is a static hosting service page, not a maintained backend. Community instances are the real deployment story [4].
• Trust shift, not trust elimination. Using a public instance means trusting that instance operator instead of Google. For privacy-minded users this may be acceptable, but it’s not the same as zero trust [3].

---

Who should use this / who shouldn’t

Use Hyperpipe if:

• You want to access the YouTube Music catalog without giving Google your listening data.
• You’re comfortable using community-hosted instances and understand they may go offline.
• You want to self-host a privacy frontend as a learning project, and you accept the maintenance risk.
• You’re already using LibRedirect and want YouTube Music covered in your redirect rules.

Skip it if:

• You need a stable, maintained tool — the project is discontinued [4].
• You depend on YouTube Music Premium features: offline listening, smart radio, background mobile playback.
• You’re setting this up for anyone who will blame you when it breaks.
• You’re looking for a long-term, production-ready self-hosted music service. Look at Navidrome + Funkwhale + your own music library instead — that stack is actively maintained and you control the content.

Consider alternatives first if:

• You want a privacy frontend for YouTube Music that is still actively developed — check ytify and Beatbump, which the Hyperpipe README itself recommends [4].

---

Alternatives worth considering

Hyperpipe’s own README lists alternatives when directing users away from the discontinued project [4]:

• ytify — Active YouTube audio streaming frontend. Described as “Efficient YouTube Audio Streaming, Effortlessly, Anywhere.” Focus on lightweight audio, not full YouTube Music UX.
• Beatbump — Alternative YouTube Music frontend built with Svelte/SvelteKit. More actively maintained than Hyperpipe at the time of writing. Similar privacy goals.
• VibeYou — Privacy-focused music player built with Material Design 3. Android-native, not a web frontend.

Outside the discontinued project’s own list:

• Invidious — The established YouTube privacy frontend. Covers regular YouTube, not YouTube Music specifically, but the most battle-tested option in the category [3].
• FreeTube — Desktop app for YouTube with no tracking. Not a YouTube Music frontend, but covers video and some music use cases [3].
• Navidrome — If you want to escape YouTube Music entirely, Navidrome is a self-hosted music streaming server for your own library. No YouTube dependency, fully under your control, actively maintained.
• Funkwhale — Self-hosted music social network and streaming. AGPL-3.0, active community, supports podcasts and federation.

For a non-technical founder who wants to escape a music streaming bill while maintaining privacy, the more sustainable path is Navidrome + your own music files over any YouTube frontend. YouTube-dependent proxies are fragile by nature; a self-hosted server with your own library is not.

---

Bottom line

Hyperpipe was a clean, privacy-first YouTube Music frontend that did what it said: strip the tracking, proxy the audio, serve the content without Google knowing you were there. The code is AGPL-3.0, the setup is lightweight, and the LibRedirect integration made it genuinely useful as part of a privacy stack.

The problem is that it’s over. The repository is archived, the maintainer has moved on, and the project depends on two external APIs (Piped and YouTube InnerTube) that change without notice. Using it today means riding a working snapshot until the next breaking change, with nobody to fix it.

If you are specifically looking for a YouTube Music privacy frontend that is still being maintained, start with ytify or Beatbump — the same project author points you there. If you want to escape YouTube Music entirely and own your music stack, Navidrome on a $5 VPS is the more permanent solution.

Hyperpipe is worth knowing about as a case study in privacy frontend design and as context for the broader ecosystem. It is not the tool to build on in 2026.

---

Sources

1. Codeberg — Hyperpipe/Hyperpipe repository (164 stars, AGPL-3.0, archived). https://codeberg.org/Hyperpipe/Hyperpipe
2. selfh.st — This Week in Self-Hosted (11 October 2024). https://selfh.st/weekly/2024-10-11/
3. Privacy Guides Community — More Privacy Frontends (March 2025). https://discuss.privacyguides.net/t/more-privacy-frontends/25931
4. Codeberg — Hyperpipe README and repository files (same repository as [1], specific README content). https://codeberg.org/Hyperpipe/Hyperpipe