Your media library, streamed from Usenet

1.xStableWritten in C#. Mounts through an rclone sidecar and has every feature, including Stremio and search.ghcr.io/infinidysk/infinidyskRead the 1.x docs

Coming from nzbdav-dev/nzbdav 0.6.4? Start here

2.xBetaRewritten in Rust. Starts in half a second, uses under a third of the CPU per GB streamed and mounts over FUSE itself. One-step upgrade from 1.x.ghcr.io/infinidysk/infinidysk-nextRead the 2.x docs

New install? Pick 1.x for a stable setup, or 2.x to try the beta. Already running infinidysk? Match the image name in your compose file. Still on ghcr.io/nzbdav/nzbdav? That is 1.x under its old name; switch the image and keep everything else.

How it works

Your Arr instances add infinidysk as a SABnzbd download client, but it never downloads the release. Work happens at two moments:

1. 1When Sonarr or Radarr grabs a release

   1. Sonarr, RadarrSend the NZB over the SABnzbd API
   2. infinidyskReads the NZB and a few headers per file
   3. MountThe files appear, without a full download
   4. LibraryThe Arr imports a symlink or STRM file

2. 2When you press play

   1. Plex, JellyfinRead a byte range over WebDAV or FUSE
   2. infinidyskFinds the articles that hold that range
   3. Usenet providersSend only those articles, several at once

   Seek

   • Read
   • Fetched ahead
   • Still on Usenet

   One file, split into the articles it was posted in. After a seek, infinidysk fetches the articles at the new position and a few ahead. Everything else stays on Usenet until something reads it.

Rewritten in Rust

2.x is the same product rebuilt from scratch in Rust: one native binary with the web UI built in, no .NET runtime and no garbage collector. Why Rust explains what that changes.

Both versions speak the same SABnzbd API and serve the same WebDAV paths, so Arrs and media servers see no difference.

Feature	1.x	2.x
In both
SABnzbd API for Arrs	Yes	Yes
WebDAV	Yes	Yes
Symlink and STRM imports	Yes	Yes
Health checks and Arr replacement	Yes	Yes
Multiple providers with priority levels	Yes	Yes
Download speed limit	Yes	Yes
Disk segment cache	Yes	Yes
SQLite and PostgreSQL	Yes	Yes
Prometheus metrics	Yes	Yes
Backup and restore	Yes	Yes
Single sign-on (OIDC)	Yes	Yes
New or changed in 2.x
Mount	rclone sidecar	Built-in FUSE
Provider catalog with backbones	No	Yes
Only in 1.x
PAR2 repair	Yes	Not yet
Connection cap across all providers	Yes	Not yet
Stremio and addon routes	Yes	Not yet
Search, indexers and Prowlarr	Yes	Not yet
Read-only role for SSO users	Yes	No
Watchtower, Preflight and Warden	Yes	Not planned

Performance

• 12× faster startup
• 3× less CPU per GB streamed
• 2× less memory at idle

1.x is C# on .NET; 2.x is Rust. Lower is better. Bars show the range across three passes.

Startup

1.x6.2 s

2.x0.4–0.5 s

CPU time per GB streamed

1.x13.2–13.3 s

2.x3.7–4.1 s

Memory at idle

1.x165–302 MB

2.x68–70 MB

Memory per stream

1.x1.28–1.53 GB

2.x1.14–1.26 GB

Sequential throughput is on par within run-to-run variance: 103–111 MB/s on 1.x, 92–103 MB/s on 2.x. Neither version rebuffered in five plays at a 3.1 MB/s playback rate.

Measured on 27 October 2026 with 1.6.3 and 2.0.0-alpha.8 in Docker on one Apple M4 Pro host, one commercial provider with 20 connections, five posts with a median size of 10.7 GB, three passes.

Community and support

Chat on Discord and follow releases. After joining, use the channel and role selector to enable release notifications.

Join Discord1.x releases2.x images

infinidysk is free and open source. If infinidysk is useful to you, you can support its development.

GitHub SponsorsPatreonBuy Me a Coffee