Qui-sync
Qui-sync is a web tool for managing Qui automation rules as code.
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
36/100 Low
- Maintained
- 61last commit 167 days ago
- Popular
- 2619 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
- Security check
- 07 serious findings, 2 minor, CI, tests
Based on 4 of 5 factors.
Security check: 7 serious findings
- Uses golang.org/x/crypto v0.37.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.37.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.37.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.37.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.37.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.37.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.37.0, which has a known critical vulnerability (Go)
Automated checks on commit 0495941, 17 Nov 2026. Not an audit.
Availability: platform listings confirmed today, links checked 18 days ago
- GitHub stars
- 19
- Open issues
- 0
- Last commit
- 2026-06-07
- License
- MIT
- Activity
- stale
Checked 6 days ago - source: GitHub (ProphetSe7en/qui-sync)
Resources & Compatibility
Requirements not published yet.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Run qui serve to start the web app Put the qui binary in a PATH folder (a place your terminal searches for commands, like /usr/local/bin), then run qui serve; if qui is not on your PATH, the command will not be found and the web app will not start. source
- Keep config and data folders safe Use --config-dir and --data-dir when running qui serve to choose where settings and data are stored, and back those folders up because losing them means losing your configuration and data. source
- Set host, port, and baseUrl In config.toml, set host (where qui listens), port (the network number, usually 7476), and baseUrl (the URL prefix). If you keep port 7476, make sure that port is reachable; otherwise your browser cannot open the qui web page. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives (4)
- LibreTorrent - LibreTorrent is a Free as in Freedom torrent client for Android 4 and later, based on libtorrent.
- SeedBox Lite - Streams torrents instantly with a Netflix-like interface using modern web tech, supports popular video formats, password protection, and ad…
- Tixati - Tixati is a peer-to-peer file sharing program that uses the popular BitTorrent protocol.
- qui - Qui is a fast, modern web interface that lets self-hosters manage one or more qBittorrent instances from a single lightweight application.
Checked 40 days ago - source: AlternativeTo
Common questions
Should I back up my Qui automations before applying a Qui-sync subscription update?
Yes, the project says to always back up before applying a subscription update. It also warns that early-development bugs could affect your Qui automations.
Is Qui-sync ready for production use?
It is in early development and may contain bugs that could affect your Qui automations. The authors say they are not responsible for those issues.
How do I start the Qui web app that Qui-sync manages?
Put the qui binary in a PATH folder such as /usr/local/bin, then run qui serve. If qui is not on your PATH, the command will not be found and the web app will not start.
How do I set the host, port, and URL prefix for the Qui web app?
In config.toml, set host, port, and baseUrl. If you keep the usual port 7476, make sure it is reachable or your browser cannot open the Qui web page.
Answers sourced from github.com, github.com, github.com
Community
- Quicken Community (other)
Collected 49 days ago - public community threads