-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Kheopsian edited this page Aug 2, 2026
·
5 revisions
🇬🇧 English · 🇫🇷 Français
Hydra is a self-hosted BitTorrent daemon built for scale and seeding: a Go
control plane driving a purpose-built Rust engine ("Typhon"). It holds 100k+
torrents in a single instance, with a live SSE web UI, a native REST API, and
a qBittorrent-compatible shim so your existing *arr / autobrr / cross-seed
setup just works.
This wiki covers how to run it and the edge cases that aren't obvious from the README.
New here? Read Concepts first (5 minutes — the mental model), then go to Installation and First Run and shape it to your setup.
- Concepts — the three ideas behind Hydra: front vs agent, hoard vs race, how you talk to it.
- Architecture — the wiring: processes, sockets, persistence.
- Installation and First Run — Docker Compose, first boot, login, first torrent.
- Bare-metal Install — running without Docker.
-
Windows install — the
.exepath. - Networking Modes — direct, SOCKS5 egress, PROXY-v2 relay, gluetun with hot port rebind.
- Gluetun (VPN) — the full recipe for running behind a VPN.
- Deployment Topologies — monolith, agent, front-only; sharding; which to pick.
- Categories and Routing — placement, strategy, and save-path per engine.
-
Adding Torrents and Existing Data — download vs seed,
skip_checking, and recheck of on-disk data. - qBittorrent Shim and Automation — autobrr, Sonarr/Radarr, cross-seed.
-
Configuration Reference —
default.tomlsections and the Config tab. - Troubleshooting — the gotchas people actually hit.
Hydra · 🇬🇧
Understand
Install & set up
- Installation & First Run
- Bare-metal Install
- Windows install
- Networking Modes
- Gluetun (VPN)
- Deployment Topologies
Use day-to-day
Reference
Hydra · 🇫🇷
Comprendre
Installer & mettre en place
- Installation & premier démarrage
- Installation bare-metal
- Installation Windows
- Modes réseau
- Gluetun (VPN)
- Topologies de déploiement
Utiliser au quotidien
Référence