Background jobs increase worker and RabbitMQ activity.
Integrated agile teams.Taiga Hardware Requirements: RAM, CPU, PostgreSQL & RabbitMQ
Plan Taiga hardware for RAM, CPU, PostgreSQL, RabbitMQ, async workers and uploads, with practical ZimaOS Docker deployment recommendations.
Taiga requirements at a glance
Taiga is a multi-service agile project-management stack; database, RabbitMQ and async workers matter more than the frontend alone.
- RAM
- No numerical official whole-host minimum published.
- CPU
- No numerical official core minimum. Concurrent users, imports, webhooks and async tasks drive load.
- Deployment
- Docker is the easiest and recommended production installation path in the official documentation.
- Database
- The standard stack uses PostgreSQL.
- Message broker
- RabbitMQ is used for Taiga events and asynchronous task processing.
- Best Zima starting point
- ZimaBoard 2 832 is a reasonable small-team all-in-one host; 16 GB is safer when async workers and other services share the machine.
From official requirements to the right setup
Size Taiga as a full Docker stack rather than a single web container.
-
Official requirements
Use the official stable Docker deployment and review the environment variables/secrets before production use.
-
Confirm your needs
Budget for PostgreSQL, RabbitMQ and the Taiga backend/frontend/events/async services rather than only the web UI.
-
Leave room to grow
Estimate active users, webhooks, import/export jobs, attachments and asynchronous tasks because they increase database and worker activity.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with Taiga's official production Compose files, persist PostgreSQL/media data and map the Taiga web port behind HTTPS.
Check every playback client
- Active users
- PostgreSQL
- RabbitMQ
- Async tasks
- Webhooks/imports
- Attachments
- HTTPS/domain
- Backup retention
Official minimum requirements
Taiga documents its production stack and software dependencies but no numerical host hardware sizing table.
Do not invent a RAM or CPU minimum. The full stack includes PostgreSQL and RabbitMQ plus multiple Taiga services, so whole-host sizing should reflect concurrency and async work.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM minimum | No numerical official minimum published | Full stack includes several services. |
| CPU minimum | No numerical official minimum published | Concurrency and async tasks drive demand. |
| Recommended deployment | Docker | Official production documentation calls Docker the easiest/recommended path. |
| Database | PostgreSQL | Core Taiga database. |
| Message broker | RabbitMQ | Used by events and async processing. |
| Docker prerequisite | Docker 19.03+ | Current documented production requirement. |
When to upgrade your hardware
Taiga should scale when active users, async tasks or database workload becomes sustained.
Imports, webhooks and async queues grow
PostgreSQL working set expands
Attachments and backups grow
More projects, issues, comments and history increase DB cache and I/O.
Long-running workspaces.Project files and retained backups can become the main storage driver.
File-heavy teams.Plan hardware growth with confidence
Scale Taiga around PostgreSQL, worker headroom and persistent files.
Use SSD-backed PostgreSQL storage
Fast durable storage improves issue/activity responsiveness and backups.
Use SATA/NVMe with ZimaBoard 2.Use 8 GB for a small-team stack
Provides practical room for Taiga plus PostgreSQL/RabbitMQ despite no official numerical minimum.
ZimaBoard 2 832.Use 16 GB for more async work and co-hosted apps
Extra memory helps PostgreSQL, RabbitMQ and workers coexist.
ZimaBoard 2 1664.Use ZimaCube 2 Pro for heavier collaboration stacks
More CPU cores help worker activity and broader service consolidation.
ZimaCube 2 Pro.Can it run on ZimaOS?
No public official ZimaOS one-click Taiga App Store detail page was verified for this guide. Use the Custom Install route unless a concrete current listing is confirmed at publish time.
Custom install Taiga in ZimaOS
Use Taiga's official production Docker Compose stack, persist PostgreSQL/media data, configure the secret keys and expose the service behind HTTPS.
Custom install Taiga in the ZimaOS app ↗Use Taiga's official production Docker setup
Follow the current upstream deployment documentation rather than relying on outdated third-party examples.
Review Taiga deployment guidance ↗Review Taiga documentation
Use the current upstream requirements and dependency versions when preparing the container stack.
Review Taiga requirements ↗Choose Zima hardware for Taiga
Taiga fits compact Zima hardware for small teams, but the multi-service stack benefits from memory headroom.
Is this a small-team Taiga stack or a heavier integrated workspace?
Small team / normal agile use
Use ZimaBoard 2 with SSD-backed PostgreSQL.
- Best starting pointZimaBoard 2 832
- More memory headroomZimaBoard 2 1664
More users, async jobs and broader services
Use stronger CPU and storage.
- Higher-headroom platformZimaCube 2 Pro
These are practical recommendations, not official Taiga user-count tiers.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small Taiga teams. | Taiga stack, PostgreSQL, RabbitMQ and moderate activity. |
|
No official numerical minimum exists; watch DB/worker memory as the team grows. | Get Now |
| ZimaBoard 2 1664 | Larger Taiga or multi-app project servers. | More PostgreSQL/RabbitMQ/worker headroom. |
|
The N150 can still limit heavy async/import workloads. | Get Now |
| ZimaCube 2 Pro | Heavier Taiga collaboration stacks. | More users, async tasks, files and other services. |
|
Single-host deployment remains a single failure domain. | 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
These answers cover Taiga RAM, CPU, Docker, PostgreSQL, RabbitMQ and ZimaOS deployment.
How much RAM does Taiga need?
Taiga does not publish a numerical official whole-host RAM minimum.
How many CPU cores does Taiga need?
No numerical official core minimum is published.
What is Taiga's recommended production installation method?
The official production documentation recommends Docker as the easiest path.
Which database does Taiga use?
The standard production stack uses PostgreSQL.
Why does Taiga use RabbitMQ?
RabbitMQ handles event and asynchronous task messaging in the production architecture.
Does Taiga need a GPU?
No dedicated GPU is required.
Can ZimaBoard 2 run Taiga?
Yes. The 8 GB model is a practical small-team all-in-one host.
When should I use more RAM?
When PostgreSQL, RabbitMQ, async workers and other co-hosted apps compete for memory.
What sources informed this Taiga hardware guide?
Current Taiga production and documentation pages plus current Zima product pages.
