Piped is a free and open-source, self-hostable alternative frontend and JSON API for YouTube, maintained under the AGPLv3 by a pseudonymous volunteer team ("TeamPiped": initial author kavin, maintainer Bnyro) with no disclosed legal entity, funded by Liberapay and cryptocurrency donations. Its README advertises no ads, no tracking, and no connections to Google's servers; the frontend's own interface text states every feature works without an account, with all data kept in the browser's local cache, while an optional per-instance username/password account syncs subscriptions and playlists to that instance's server. The main privacy caveat is architectural: whichever public instance a user picks proxies and can see all of their requests, and the project's own docs warn against using third-party listed instances that may run modified code — while the live official instance list currently advertises a single public instance (private.coffee, Austria). Instance operators may also enable optional server-side components (Sentry error tracing, a captcha-solving service, a Have I Been Pwned password check, SponsorBlock and Return YouTube Dislike proxies). No breach, regulatory action, or third-party audit involving Piped was found; the notable track-record artifact is sustained YouTube anti-bot blocking of instance IPs since mid-2024, which the project's docs and issue tracker document candidly.
TIMELINE
NO ENTRIES ON FILE YET.
TOOLS WE RECOMMEND
PLUS
RECEIPTS
12 ON FILE
COLLECTION
Piped's README lists 'No connections to Google's servers' and 'Locally saved Preferences' among its user features, alongside an optional 'Login' feature; it positions the project as a way to watch YouTube content without handing data to YouTube, and no Google account is involved.
The frontend's own registration notice states that every feature works without an account, with all data kept in the browser's local cache; creating an optional account on a specific instance syncs subscriptions and playlists to that instance's server under a username and password, and the notice tells users not to use an email address as their username.
The project's 'Why' documentation, written in the first person by its creator, states Piped was built to fix architectural issues in NewPipe and Invidious, listing as NewPipe's drawback that the user's IP is exposed to YouTube — i.e., Piped's design routes YouTube requests through the instance rather than the user's device; the same page concedes Piped requires JavaScript.
Piped's README identifies no legal entity behind the project: donations are directed 'to Kavin' via Bitcoin, Ethereum, Monero, Nano, and Dash wallet addresses and via Liberapay pages for two pseudonymous maintainers — 'kavin (Initial author)' and 'Bnyro (Project maintainer)' — with public Matrix and Lemmy rooms as the support channels; the code is hosted under the TeamPiped GitHub organization.
Piped's frontend repository publishes its complete source code under the GNU Affero General Public License version 3, which also obliges anyone running a modified instance to publish their changes — the basis for the project's warning about undisclosed modifications on third-party instances.
Privacy Guides lists Piped on its frontends page (criteria: open-source, self-hostable, all basic functionality available to anonymous users) but states that Piped does not provide privacy by itself and recommends against logging into any accounts.
The official public-instance list that the Piped frontend and downstream clients read (piped-instances.kavin.rocks) currently advertises a single public instance — private.coffee, located in Austria, with roughly 31,000 registered accounts and registration open — so a user who does not self-host has effectively one third-party operator, who proxies and can observe all of their requests, to choose from.
The project's own 'Public instances' documentation page warns users against using the frontends of the third-party instances it lists, because they are not checked for correct configuration and may run modified code without disclosing their source as the AGPL requires, and recommends the project-run piped.video, IPFS, or the README mirrors instead — a candid statement that trust in a Piped deployment rests on the individual instance operator.
Piped's self-hosting documentation states that YouTube tends to ban instance IP addresses and recommends operators use the Invidious team's IPv6 rotator or a VPN/proxy between the Piped backend and YouTube to keep a public instance running — documenting the sustained blocking pressure behind the shrinking public-instance pool; no third-party security audit, transparency report, or bug-bounty program for Piped was found.
An issue opened in June 2024 on the Piped repository — still open with roughly 100 comments — reports that YouTube's 'Sign in to confirm that you're not a bot' check blocks video playback on the reporter's private instance and on public instances; maintainers' replies advise operators to obtain unblocked IP addresses or put a VPN/proxy in front of the backend. This is operational fragility rather than a privacy incident; no breach, regulatory action, or security advisory involving Piped was found in this research.
The reference backend configuration shipped with Piped-Backend shows the third-party server-side components an instance operator can enable: an optional Sentry DSN to 'log errors and trace performance', a captcha-solving service (capmonster.cloud by default), a Have I Been Pwned compromised-password check on registration (enabled by default), configurable SponsorBlock and Return YouTube Dislike proxy servers, and a 30-day retention for unauthenticated subscription lists — choices made per instance, not by the user.
Piped's README advertises 'No Ads' and 'No Tracking' as user features and states the project does not use official YouTube APIs, extracting data with NewPipeExtractor instead; it also lists integrations with the third-party SponsorBlock, LBRY, and Return YouTube Dislike (via the project's own RYD-Proxy) services.