Qui Hardware Requirements: RAM, CPU, Storage & qBittorrent Instances
Plan Qui hardware for RAM, CPU, torrent databases, qBittorrent instance count, automations, and practical ZimaOS deployment recommendations.
Qui hardware requirements at a glance
Size Qui from verified upstream requirements first, then add headroom for the workload and persistent data.
- RAM
- No numerical official minimum published
- CPU
- No numerical official minimum published
- Storage
- Small config/database footprint
- Database
- SQLite or PostgreSQL
- Port
- 7476
- Best Zima starting point
- ZimaBoard 2 832
From official requirements to the right setup
Start with verified upstream facts for Qui, then size the workload rather than copying a container or app-store resource label.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- qBittorrent instance count
- Torrent count
- Automation rules
- Cross-seed usage
- SQLite vs PostgreSQL
- Shared torrent paths
- Backup snapshots
- Concurrent UI/API users
Official minimum requirements
Qui publishes deployment, database, and data-path requirements but no numerical whole-host CPU, RAM, or disk minimum.
Do not size Qui as if it were the torrent engine; qBittorrent handles downloading/seeding while Qui is the management/automation layer.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Qui is described as lightweight. | |
| No numerical official minimum published | Depends on managed instances and automation scale. | |
| ghcr.io/autobrr/qui:latest | Official project image. | |
| 7476 | Default web interface. | |
| SQLite or PostgreSQL | Migration tooling is documented. | |
| Config/data plus matching torrent path when hardlink detection is used | Path layout matters for inode visibility. | |
| Not required | No GPU workload. |
When to upgrade your hardware
Large torrent collections
Database growth
Automation/path complexity
Plan hardware growth with confidence
SSD config/database
Keep Qui state on SSD.
SSDMore RAM for larger stack
Useful with qBittorrent, cross-seed, indexers, etc.
ZimaBoard 2 1664Torrent data storage
Size capacity for qBittorrent separately.
ZimaCube 2 StandardHigher CPU for consolidated stack
Only if broader stack is CPU-bound.
ZimaCube 2 ProCan it run on ZimaOS?
Install Qui from the ZimaOS App Store
A specific public Qui App Store page is verified.
Open Qui in the ZimaOS App Store ↗Use official autobrr/qui image
Upstream documents ghcr.io/autobrr/qui:latest and port 7476.
Open Qui source ↗Match qBittorrent paths exactly
Hardlink detection requires matching paths and underlying storage.
Review Qui automation path requirements ↗Zima hardware for Qui
Qui is a light management layer; size mainly for qBittorrent, torrent storage, and the surrounding stack.
Choose by workload
ZimaBoard 2 832 is sufficient for Qui itself.
DB, RAM, and the surrounding torrent stack may justify larger hardware.
Do not attribute qBittorrent transfer/hashing workload to Qui itself.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services and small download/transfer workloads | One light app or a small home-server stack |
|
8 GB RAM and a 4-core N150 can limit CPU-heavy extraction, AI, and large multi-service stacks | Get Now |
| ZimaBoard 2 1664 | Memory-heavier download automation and multi-container workloads | Apps benefiting from 16 GB RAM without needing a much faster CPU |
|
CPU throughput is unchanged from the 832 model | Get Now |
| ZimaCube 2 Standard | Storage-heavy downloads and media libraries | Large persistent data sets where drive bays matter most |
|
8 GB RAM can be less suitable than ZimaBoard 2 1664 for memory-heavy services | Get Now |
| ZimaCube 2 Pro | CPU-heavier extraction and higher-concurrency workloads | Stronger CPU plus expanded storage and networking |
|
16 GB RAM can still constrain large local AI workloads | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
How much RAM does Qui need?
No numerical whole-host RAM minimum is published.
How many CPU cores does Qui need?
No numerical official CPU minimum is published.
Which database does Qui use?
SQLite is supported and PostgreSQL is also supported.
What port does Qui use?
7476.
Does Qui download torrents itself?
No; it manages qBittorrent instances.
Why do Docker paths matter?
Hardlink-scope detection needs matching paths on the same underlying storage.
Can ZimaBoard 2 832 run Qui?
Yes for normal home deployments.
When should I choose larger hardware?
When the combined qBittorrent, automation, DB, and storage workload needs it.
