Harvest

Harvest is a self-hosted seedbox-to-homelab sync tool that pulls finished downloads from File Transfer Protocol (FTP), FTP over TLS (FTPS), or Secure File…

  • Cloud
  • Downloaders
  • Network Services
Harvest is a self-hosted seedbox-to-homelab sync tool that pulls finished downloads from File Transfer Protocol (FTP), FTP over TLS (FTPS), or Secure File Transfer Protocol (SFTP) servers into local folders on a schedule, verifies file stability, and keeps a ledger so deleted files are never re-downloaded.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • 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.

42/100 Fair

Maintained
77last commit 26 days ago
Popular
102 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
108 GB minimum RAM

Availability: platform listings confirmed today

GitHub stars
2
Open issues
0
Last commit
2026-10-26
License
MIT
Activity
rising

Checked 23 days ago - source: GitHub (Pross/harvest)

Resources & Compatibility

Minimum requirements: 8 GB RAM.

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

First-install notes

  • Install the server certificate After the CA certificate is installed, install the server certificate and its private key on the cluster. This lets Harvest trust the cluster's secure connection; without it, HTTPS or certificate checks can fail. source
  • Get Grafana before first run Download and unpack the Grafana binary into your Harvest install folder. Grafana provides the dashboards for viewing Harvest data, so you need it before you expect to see charts. source
  • Staging prevents incomplete file processing Harvest stages files in a .harvest-staging folder and renames them atomically, so media apps do not process incomplete files. source
  • SFTP setup Secure File Transfer Protocol (SFTP) support uses rclone as the transport. source

Fetched yesterday - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Will a file I delete locally be downloaded again on the next run?

No. Each synced file is recorded in a ledger, local deletion is invisible, and rerunning a job does not re-download the same file.

How does Harvest avoid Sonarr, Radarr, or Plex seeing half-written files?

It uses a settle check to skip incomplete or growing files, stages files in a hidden directory, verifies them, and atomically renames them into the target folder.

How are interrupted or stalled downloads handled?

Killed or stalled downloads can resume where they left off, with progress checkpointed every 16 MB.

Can a torrent client trigger a Harvest job?

Yes. Harvest supports webhook-triggered runs using job-scoped API tokens with Bearer auth, with copy-paste curl snippets for qBittorrent, rTorrent, and Deluge.

How can the Harvest web UI be protected behind a reverse proxy?

It can use the built-in single-user login with scrypt-hashed passwords and CSRF-protected sessions, or set auth to none and rely on Origin and Host checks for reverse-proxy auth.

Answers sourced from github.com

Community

Collected 44 days ago - public community threads