Peach: A Local-First Media Manager With 13,000 Stars

By Indie Kings | October 29, 2026

Updated October 29, 2026: peach-mitao/peach, a local-first video metadata scraper and media manager, reached version 0.50.0 and 13,177 stars with only six contributors. The project is AGPL-3.0-or-later, was created on August 19, 2026, ships Windows, macOS and Docker builds, and keeps metadata and watch history in a local database rather than a hosted account.

Note: Peach is built for adult video libraries and carries an 18+ notice. This article covers the software design and its data handling. It does not describe the content itself.

Image: a film projector at the Onomichi Cinema Museum, Japan, via Wikimedia Commons.

A scraper that keeps your edits

The premise is ordinary and the execution is where the work is. You point Peach at folders of video, it reads filenames, recognizes product codes, parses NFO files and pulls titles, performers, studios and cover art from several sources. The sentence that matters in the README is the last clause: while keeping your edits. Scrapers that overwrite hand corrections on the next scan are the standard complaint about this category of software, and a tool that treats local metadata as authoritative is making a promise about merge order that is easy to state and hard to implement.

Everything around that core is library management. Tags, duplicates, multiple versions of the same title and multi-part releases all get first class handling, which is the difference between a download folder and a catalog. Watch history, resume points and playback speed are tracked per item, and the player supports subtitles, rotation and timeline previews. For a collection spread across drives, the duplicate and version handling is the feature that prevents the library from turning into a mess again after the first cleanup.

The follow system adds a monitoring layer. Performers and creators can be followed, updates are surfaced, and there is a want list for titles you do not own yet. That turns the application from a viewer into something closer to a subscription tracker that happens to play local files, and it is the kind of feature that explains the star count: it addresses a workflow rather than a single task.

Local, network and cloud in one library

Storage support is broader than a desktop app usually bothers with. Peach browses local drives, SMB shares, mounted cloud storage and PikPak libraries in one view. PikPak support is a regional detail that signals the actual user base, and it is implemented as a library source rather than a special case in the UI. The cloud download feature accepts a video code search or a magnet link, then files completed downloads into the library with metadata attached.

Running it in Docker on a NAS is a documented path, and that is the configuration most likely to matter for a large collection: a small always-on box holding the files, with the web interface reached from a laptop. Source installs need Git, uv and Python 3.14 or newer, which is a modern baseline and a sign the project is not carrying legacy compatibility weight. The desktop builds are the convenience option, with a Windows x64 installer and portable zip, and separate macOS DMGs for Apple Silicon and Intel.

The README is careful about what the software does not do. It provides no video resources and no access to paid content, and it asks users to manage only media they own or are authorized to use, subject to copyright, platform terms and regional restrictions. That disclaimer does real work here, because a metadata scraper sits close to the line between cataloging and distribution, and the project draws the line at indexing files the user already has.

Unsigned builds and the trust question

The honest caveat is in the download table: desktop test builds are unsigned and macOS builds are not notarized. On Windows that means a SmartScreen warning, and on macOS it means Gatekeeper will refuse to open the app until the user overrides it. For a project with six contributors and a fast release cadence, paying for code signing certificates and Apple notarization is a real cost, and skipping it is common. It is also a genuine risk signal that users should weigh, particularly for software that reads a whole media library and talks to cloud services.

The mitigation is the same as for any self-hosted tool: build from source or run the Docker image, read the Dockerfile, and check what leaves the machine. The README points to a diagnostics and data sharing document, which suggests network behavior is documented rather than hidden, and the AGPL license means the source of any modified network service has to be offered to its users. None of that is a security audit, but it is more transparency than most closed media managers provide.

Version numbers tell their own story. Reaching 0.50.0 in about two months of public life, with 101 open issues and 1,543 forks, describes a project moving faster than its contributor count would suggest. Six people shipping a cross-platform app with a player, a scraper, a downloader and a library database is a lot of surface area, and the issue count is the honest measure of how much is still rough. The alternative reading, that the pace comes from heavy reliance on existing libraries, is also plausible and is visible in the credits to amane, Gfriends and CloudDrive2.

Project card

FAQ

What does Peach do?
It scans video folders, recognizes titles, pulls metadata and cover art, and manages the resulting library with tags, history and playback.

Does it upload my library?
Metadata and watch history are stored locally. Scraping and cloud features contact external services, and the project documents its diagnostics and data sharing behavior.

Which platforms are supported?
Windows x64, macOS on Apple Silicon and Intel, Docker for NAS use, and a source install with Python 3.14 or newer.

Why do the desktop builds warn about the developer?
They are unsigned and the macOS builds are not notarized, so Windows SmartScreen and macOS Gatekeeper flag them. That is a cost decision, not necessarily a sign of malice, but it deserves caution.

Does it include videos?
No. Peach provides no media and no access to paid content, and the README asks users to manage only material they are authorized to use.

Is it suitable for a very large collection?
The NAS and Docker path plus duplicate and version handling are built for large libraries, but the project is young and has 101 open issues.

Bottom Line

Peach is a well scoped media manager that treats local metadata as the source of truth, which is the single most important design decision in this category. The storage spread from local drives to SMB, cloud mounts and PikPak, plus a real player and a download queue, makes it more useful than the average scraper wrapper. The unsigned builds and six contributor team are the reasons to be careful rather than enthusiastic: run it in Docker, read the source, and keep backups of the database. For an adult library that has outgrown folders and filenames, it is the most complete open option reviewed here.

Sources

• GitHub peach-mitao/peach README, feature list, download table, license and content notice, accessed October 29, 2026
• GitHub API metadata for peach-mitao/peach, stars, forks, contributors, issues and latest commit, accessed October 29, 2026
• peach.video and demo.peach.video as linked from the repository, accessed October 29, 2026

Related: LumaFin-AndroidTV: The Open-Source Custom Jellyfin Client Reinventing the Living Room Streaming Experience | SteamOS 3.9: Valve Ships Plasma 6.7 and Linux 7.2 to Everyone