Bindery

Bindery is a self-hosted ebook and audiobook automation server.

  • Media Applications
  • Media Servers
  • Tools & Utilities
Bindery is a self-hosted ebook and audiobook automation server. Search OpenLibrary, Hardcover, and DNB for books and authors; monitor authors and series; hand requests to your *arr-style indexers and download client (NZB or torrent); import completed files into your library with proper metadata; serve an OPDS 1.2 catalogue to e-readers.

Platform availability

Available on 2 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

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.

78/100 Good

Maintained
100last commit 10 days ago
Popular
55569 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data
Security check
94no serious findings, CI, tests, OpenSSF Scorecard 8.5/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 38 days ago

GitHub stars
569
Open issues
30
Last commit
2026-11-10
Latest release
v1.50.0
License
MIT
Activity
steady

Checked 10 days ago - source: GitHub (vavallee/bindery)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Install with Helm and set storage and host Use the Helm install command and set persistence.config.storageClass to a storage class your cluster has, plus ingress.enabled=true and ingress.host for the web URL. The storage class tells Kubernetes where to keep persistent data, and the ingress settings let you open the app in a browser. source
  • Add the Calibre plugin if you use Calibre If Bindery should send books to Calibre, download the Calibre Bridge plugin into your Calibre pod, install it with calibre-customize, then restart the Calibre deployment. Without the plugin and restart, Calibre will not receive the new books Bindery sends it. source
  • Set the downloader URL Base correctly For a download client like qBittorrent behind a reverse proxy, put the path such as /qbit or the full URL such as https://nas.local/qbit in the URL Base field. Leave it blank only if you reach the client directly without an extra subpath, otherwise Bindery may send requests to the wrong address and downloads will fail. source
  • First-run & container user Open the WebUI to create an admin account. No env vars required for auth. Default user is 99:100. If you change PUID/PGID, also change the --user value in Extra Parameters; the container will fail fast if they don't match. source

Fetched 38 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can Bindery import an existing Readarr database?

Yes, Bindery can take over an old Readarr database.

How do I point a Helm deployment at persistent storage and expose the web UI?

Set persistence.config.storageClass to a storage class your Kubernetes cluster has. Also set ingress.enabled=true and ingress.host to the web URL so the app can be opened in a browser.

How should I configure the downloader URL Base when qBittorrent is behind a reverse proxy?

Put the proxy path, such as /qbit, or the full proxied address in the URL Base field. Leave it blank only if you reach the client directly without an extra subpath.

Why do finished downloads show as importFailed in Bindery's queue?

This can happen when Bindery and the download client see the storage at different paths because of different container mounts. Bindery cannot find the finished download in that case, which usually surfaces as importFailed in the queue.

Answers sourced from github.com, github.com, github.com, github.com

Community

Collected 53 days ago - public community threads