Overview
TorrenClou is a self-hosted torrent-to-cloud platform. One Docker container, one command, no configuration files.
TorrenClou downloads torrents on your server and uploads them to Google Drive or S3-compatible storage, then cleans up after itself.
Everything ships as one container that generates its own secrets and is configured in the browser. If you find yourself editing a config file to do something ordinary, that is a bug — please open an issue.
Install
curl -fsSL https://raw.githubusercontent.com/TorrenClou/deploy/main/install.sh | bashWindows, in PowerShell:
irm https://raw.githubusercontent.com/TorrenClou/deploy/main/install.ps1 | iexDocker is the only requirement. Open the URL it prints and create your account.
What it does
- Add a torrent by file or magnet link, inspect its contents, and download only the files you actually want.
- Upload finished downloads to Google Drive or S3 — AWS, Backblaze B2, Cloudflare R2, DigitalOcean Spaces, Wasabi, MinIO.
- Uses your storage credentials. Nothing is proxied through a third party.
- Reroutes a failing upload to another healthy drive instead of giving up.
- Deletes local copies once they are safely uploaded, so the disk does not fill.
- Watch transfers, retries and failures from the dashboard, with Grafana dashboards bundled in if you want them.
Ports
| Port | Service |
|---|---|
| 47100 | Web interface |
| 47200 | API, plus /hangfire |
| 47500 | Grafana |
| 47600 | Prometheus |
Only 47100 needs to be reachable for normal use.
Where to go next
Getting started
- Installation — the one-liner, manual
docker run, reverse proxies, custom domains - First-run setup — the wizard, connecting Google Drive, connecting S3
Running it
- Usage guide — adding torrents, picking files, watching transfers
- Configuration — every setting, and the environment overrides
- Updating — upgrades, backups, rollbacks
- Troubleshooting — when something does not work
Understanding it
- Architecture — what runs inside the container, and how a torrent becomes a file in your storage
- Security — where secrets live, what is exposed, what to put behind a proxy
Source
| Repository | Contents |
|---|---|
| deploy | The all-in-one image, the installer, and CI |
| backend | .NET 9 API and the three workers |
| frontend | Next.js web app |
| website | This documentation |
MIT licensed.