NzbDav vs Decypharr — and Why You Might Want Both

ElfHosted Personal Media Stacks ship with one of two content layers, depending on the variant you bought:

• NzbDav side — Usenet streaming as a virtual filesystem (no downloads).
• Decypharr side — Real-Debrid via qBit-API shim, downloads cached on RD.

Buying this standalone Decypharr makes sense if your stack came with NzbDav (Usenet) and you want to add Real-Debrid alongside it without spinning up a second arr stack. The flip case — your stack came with Decypharr and you want to add Usenet — is what NzbDav [Standalone] is for. Run both alongside your bundled arrs and you get a single library fed by both Usenet and Real-Debrid.

Why Run Decypharr on ElfHosted?

Self-hosting a qBit-API shim is fiddly: you have to keep it reachable to your arrs, keep its config in sync with your RD token, handle the WebDAV side separately, and survive every Sonarr/Radarr update that nudges its qBit client expectations. ElfHosted's standalone Decypharr handles all of that:

• Pre-configured to authenticate with your stack's arrs out of the box.
• Real-Debrid token managed via your ElfHosted control panel — no editing config files.
• Mounts and library paths line up with your bundled NzbDav (or other content layer), so both content sources feed one library.
• Updates roll out in lockstep with the rest of your stack.