The Nabbed agent
What the agent does, what it needs, and how it keeps your credentials private.
The agent is a small program you run on your own hardware: a NAS, a home server, a Raspberry Pi or a Kubernetes cluster. Nabbed's cloud decides what to download. The agent downloads it and files it into your library.
It downloads over usenet and BitTorrent itself, so you don't need a separate download client.
How it works
- You pair the agent with your Nabbed account once, by approving a short code in the web app.
- The cloud searches your indexers, picks the best release for your quality profile and sends it to the agent.
- The agent downloads it, reports progress to the web app, then moves the finished files into your library folder, named the way your library is set up.
What it needs
| Platforms | Linux (amd64, arm64, armv7), macOS (Intel and Apple silicon), Windows (amd64, arm64). The Docker image is Linux only. |
| Outbound network | HTTPS to api.nabbed.media, plus your usenet providers and BitTorrent peers. |
| Inbound network | None required. Forwarding port 6881 (TCP and UDP) speeds up BitTorrent downloads. |
| Storage | A small persistent folder for the agent's credentials and state, space for downloads in progress, and write access to your library folders. |
Your credentials stay yours
When you add a usenet provider in the web app, your browser encrypts the username and password to this agent's key before sending them. Nabbed stores the encrypted copy but cannot read it; only the agent can.
That key belongs to one agent. If you pair an agent again, it gets a new key, and you'll need to enter its usenet providers again.
Library folders are opt-in
The web app chooses where each imported file goes, but only inside folders you allow on the agent's machine. By default none are allowed, so imports are refused until you allow the parent folders of your libraries. Each install guide shows how.