Peach

Peach is a local-first, self-hosted video media manager and metadata scraper that unifies your personal video library from local hard drives, NAS shares, and…

  • Media Applications
  • Media Servers
Peach is a local-first, self-hosted video media manager and metadata scraper that unifies your personal video library from local hard drives, NAS shares, and online cloud drives into one browsable collection, running as a Docker image (full runtime included) on a home server or NAS, or as a desktop app for Mac and Windows.

Platform availability

Available on 3 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac
  • Windows
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

87/100 Excellent

Maintained
100last commit 5 days ago
Popular
8415,105 GitHub stars
Easy to install
553 install platforms, install notes, Docker image
Light to run
100102 MB minimum RAM

Availability: platform listings confirmed today

GitHub stars
15,105
Open issues
187
Last commit
2026-11-16
License
AGPL-3.0
Activity
steady

Checked 5 days ago - source: GitHub (peach-mitao/peach)

Resources & Compatibility

Minimum requirements: 102 MB RAM, 102 MB disk. ARM (e.g. Raspberry Pi) is not supported.

Checked 5 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Use Peach's sandbox for first tests Set up your first requests to use Peach's sandbox URL and test cards, not the live payment endpoint. This matters because live settings can accept real payments or charge real cards before you've confirmed everything works. source
  • Fill in Peach ID and Bearer token Enter your Peach entityId and Bearer token (the text key that proves your app is allowed) in your request settings. If either is missing or mistyped, Peach won't know which account you belong to and will reject the payment. source
  • Don't leave SSL checks off Keep SSL verification (checking that the connection to Peach is really encrypted and going to the right server) turned on after you finish experimenting. The docs leave it off only for easy testing, but leaving it off lets a fake server read or change payment information. source
  • Download the right build Download the Mac or Windows desktop app directly from the GitHub Releases page, or deploy the Docker image for headless server/NAS use — each Docker image ships with the full runtime so no separate client install is needed. source

Fetched 5 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where does Peach store metadata and watch history in a self-hosted setup?

Metadata and watch history are stored locally.

Can Peach browse media from SMB shares or mounted cloud storage?

It can browse local drives, SMB, mounted cloud storage, and PikPak libraries together.

Can I add magnet-link downloads into the library?

You can search by video code or submit a magnet link, then organize completed downloads into your library.

Does Peach show background task activity for self-hosted deployments?

The task center can pause, resume, or cancel local background tasks and view CPU, GPU, and download activity where available.

Will metadata scraping replace my manual edits?

It fills titles, performers, studios, and covers from multiple sources while keeping your edits.

Answers sourced from github.com

Community

Collected 5 days ago - public community threads