qui
PulseGate's liveness check found it on 13 Sep 2026; it is registered on GitHub and Firefox Add-ons and has been in the index since 13 Sep 2026. How this is checked
qui is a self-hosted web interface for managing multiple qBittorrent instances from one login. It includes cross-seeding, rule-based automations, scheduled backups, orphan-file scanning, a qBittorrent-compatible proxy, and support for SQLite or Postgres deployment.
Inferred · not functionally tested
Overview
6 featuresPurpose: Managing multiple qBittorrent instances, torrent automation, backups, and large libraries from separate interfaces.
Inferred · not functionally tested
Audience: qBittorrent users managing multiple torrent instances and large media libraries
Inferred · not functionally tested
Functions: workflow_automation
Inferred · not functionally tested
Interfaces: API: unknown · MCP: unknown · CLI: unknown · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: free · license: GPL-2.0 · platforms: WEB · deployment: browser, embeddable, self_hosted
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: getqui.com · addons.mozilla.org · github.com. These links do not verify the individual claims.
qui sits in PulseGate's Other file storage category. Inferred · not functionally tested: It focuses on managing multiple qBittorrent instances, torrent automation, backups, and large libraries from separate interfaces. Inferred · not functionally tested: It is built as an open-source project for qBittorrent users managing multiple torrent instances and large media libraries. Basis unknown · not verified: qui costs nothing to use. Basis unknown · not verified: It ships for the web and embeddable surfaces, and it can be self-hosted.
autobrr builds and maintains qui, and it first shipped in 2025. Development happens publicly on GitHub with 4.5k stars and 366 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are multi-instance management, torrent filtering, and cross-seeding.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Multi-instance management
- Torrent filtering
- Cross-seeding
- Rule automations
- Scheduled backups
- Orphan scanning
Topics: Inferred · not functionally tested
Built with & integrations
- Claude Code
- commit 29c60b6f829c · since Sep 2026
- Gemini CLI
- GEMINI.md
- Netlify
- x-nf-request-id header
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
Frequently asked questions about qui
- What does qui do?
- Inferred · not functionally tested: Qui focuses on managing multiple qBittorrent instances, torrent automation, backups, and large libraries from separate interfaces. It is catalogued under Other file storage on PulseGate.
- Who is qui for?
- Inferred · not functionally tested: qui is an open-source project built for qBittorrent users managing multiple torrent instances and large media libraries.
- Is qui free?
- Basis unknown · not verified: Yes — qui is free to use.
- What platforms does qui run on?
- Basis unknown · not verified: qui runs on the web and embeddable surfaces. It can also be self-hosted.
- Is qui still active?
- PulseGate's liveness check found it on 13 Sep 2026. Its GitHub repository shows 366 commits in the last 90 days.
- What projects are similar to qui?
- Similar projects tracked by PulseGate include qBittorrent, qRemote for qBittorrent, and qbit-ops.qBittorrentqRemote for qBittorrentqbit-ops
- Who makes qui?
- qui is developed by autobrr.
- When did qui launch?
- qui first shipped in 2025.
Similar projects
Closest matches by what these projects do