One Web Interface, All Your qBittorrent Instances

If you're running more than one qBittorrent instance—maybe one for Linux ISOs, one for... other things—you already know the pain of juggling browser tabs and re-authenticating every time you want to check on a download. qui is a single-binary web interface that lets you manage all of them from one place.

What It Does

qui is a web interface for qBittorrent that supports managing multiple instances from a single, lightweight application. It's built to be fast and responsive, with particular attention paid to handling large torrent collections without choking.

The architecture is deliberately simple: it ships as a single binary with no external dependencies. You download it, run it, and you've got a web UI listening on port 7476. There's also a Docker image if that's more your speed. The whole thing is developed by the autobrr team (the same folks behind autobrr itself), and full documentation lives at getqui.com.

Beyond basic multi-instance management, qui includes a cross-seed feature that automatically finds and adds matching torrents across trackers, rule-based automations for torrent management, and scheduled backups with multiple restore modes. It can also act as a transparent reverse proxy for qBittorrent, which means external apps can talk to your instances through qui without knowing they're going through a middleman.

Why It's Cool

The single binary thing is genuinely nice. No Python virtualenvs, no Node.js runtime, no Docker orchestration required (though Docker's supported). You download a tarball, extract one file, and run it. For a self-hosted tool, that's about as frictionless as it gets.

Multi-instance support is the headline feature, and it's done properly. If you've got qBittorrent running on three different boxes (or three different containers), qui treats them as first-class citizens in one interface. You're not context-switching between bookmarks—everything's in one dashboard.

The reverse proxy feature is a clever touch. Instead of pointing your external tools directly at qBittorrent, you can point them at qui, which proxies the requests through. This means you can centralize access control and routing without reconfiguring every app that talks to qBittorrent.

Cross-seed and automations round out the "power user" toolkit. Cross-seeding—finding the same torrent on multiple trackers and adding it everywhere—is a manual chore if you do it by hand. Automations let you define rules with conditions and actions, so torrents can be managed based on criteria you set rather than you clicking around.

Backups and restore modes are handled. You can schedule snapshots and restore them in multiple ways. If you've ever lost your qBittorrent state and had to rebuild it from memory, you'll appreciate this.

Localization is broader than you'd expect. The interface supports English, German, French, Italian, Czech, Ukrainian, Korean, Brazilian Portuguese, Simplified Chinese, Traditional Chinese, and Catalan—with automatic browser-language detection. That's a lot of languages for a project at this stage.

One thing worth noting: the project offers premium themes as a way to support development. You can buy them through Settings, and a license also unlocks the ability to write custom themes (or grab them from the qui-community-themes repo). It's an interesting funding model—optional cosmetics rather than paywalling core functionality.

How to Try It

The fastest path on Linux x86_64:

# Download and extract the latest release
wget $(curl -s https://api.github.com/repos/autobrr/qui/releases/latest | grep browser_download_url | grep linux_x86_64 | cut -d" -f4)
sudo tar -C /usr/local/bin -xzf qui*.tar.gz qui

# Run
qui serve

The web interface will be available at http://localhost:7476.

If you prefer Docker:

docker run -d \
  -p 7476:7476 \
  -v $(pwd)/config:/config \
  ghcr.io/autobrr/qui:latest

That's it. No additional setup, no dependency wrangling. You can find the full documentation at getqui.com and the source at github.com/autobrr/qui.

Final Thoughts

qui is aimed squarely at people who run multiple qBittorrent instances and want a unified way to manage them without building their own dashboard. The single-binary approach makes it easy to deploy, and the feature set—cross-seeding, automations, backups, reverse proxy—covers the practical needs of a serious self-hoster. It's not trying to be everything to everyone; it's a focused tool that does one thing well. If that one thing is what you need, it's worth a look.

Follow @githubprojects for more developer tools and open source projects.