Background workflows and integrations can consume CPU/RAM independently of interactive users.
Automated CRM deployments.Requisiti hardware di Twenty: RAM, CPU, PostgreSQL e Redis
Pianifica l'hardware di Twenty CRM per RAM, CPU, PostgreSQL, Redis, processi worker e archiviazione locale dei file, con indicazioni pratiche per la distribuzione su ZimaOS.
Twenty requirements at a glance
Twenty is a multi-container CRM stack, so the server, worker, PostgreSQL and Redis all belong in the hardware budget.
- RAM
- No numerical official whole-host RAM minimum published.
- CPU
- No numerical official core minimum. API traffic, imports, workflows and background jobs determine practical demand.
- Database
- The current official Docker Compose file uses PostgreSQL 16.
- Cache/queue
- The official stack uses Redis with a noeviction memory policy.
- Services
- The current Compose stack runs a server container and a separate worker container, plus PostgreSQL and Redis.
- Best Zima starting point
- ZimaBoard 2 1664 is the safer compact choice for an all-in-one Twenty stack; ZimaCube 2 Pro suits heavier automation and broader CRM use.
From official requirements to the right setup
Size Twenty from the full multi-service stack rather than only the frontend/API container.
-
Official requirements
Use Docker Compose v2 and the current official Twenty deployment scripts/Compose file.
-
Confirm your needs
Budget separately for the server, worker, PostgreSQL 16 and Redis; background workflows can load the worker even when the UI is quiet.
-
Leave room to grow
Persist PostgreSQL and local file data, or configure external object storage as the deployment grows.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with the official Twenty Compose stack, persist db/local-storage volumes, map port 3000 and configure the required encryption/database secrets.
Check every playback client
- Active users
- PostgreSQL 16
- Redis
- Worker jobs
- Local/S3 storage
- Port 3000
- Secrets
- Backup retention
Official minimum requirements
Twenty's current Docker project defines the service architecture and runtime prerequisites but no numerical hardware table.
Do not invent a 4 GB or 8 GB official minimum. Practical sizing must cover the server, worker, PostgreSQL and Redis together.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM minimum | No numerical official minimum published | Full stack includes four core services. |
| CPU minimum | No numerical official minimum published | Worker jobs and API traffic drive demand. |
| Docker Compose | Version 2+ | Current install script requirement. |
| Database | PostgreSQL 16 | Current official Compose image. |
| Cache/queue | Redis | Current official Compose service. |
| App services | Server + worker | Separate current production containers. |
When to upgrade your hardware
Twenty should scale when worker jobs, database growth or active CRM users create sustained pressure.
Automation and worker jobs increase
PostgreSQL working set grows
Files and backups grow
More objects, activities and relationships increase database cache and I/O needs.
Growing sales/operations teams.Local attachments or object-storage data and backups can become the main storage requirement.
File-heavy teams.Plan hardware growth with confidence
Scale Twenty around PostgreSQL, worker concurrency and file storage.
Use SSD-backed PostgreSQL storage
Low-latency durable storage improves CRM queries and backups.
Use SATA/NVMe with ZimaBoard 2 or SSD tiers on ZimaCube 2.Use 16 GB for a compact all-in-one stack
Provides more room for the server, worker, PostgreSQL and Redis despite no official numerical minimum.
ZimaBoard 2 1664.Use object storage when files grow
External/S3-compatible storage prevents local app volumes from becoming the only scaling path.
Use ZimaCube storage or an external S3-compatible service.Use stronger CPU for heavier workflows
More cores help worker jobs, imports and broader service consolidation.
ZimaCube 2 Pro.Can it run on ZimaOS?
No public official ZimaOS one-click Twenty 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 Twenty in ZimaOS
Use Twenty's official Docker Compose stack with server, worker, PostgreSQL and Redis, persist database/local-storage volumes, and configure encryption/database secrets before launch.
Custom install Twenty in the ZimaOS app ↗Use Twenty's official Docker installer
Follow the current upstream deployment documentation rather than relying on outdated third-party examples.
Review Twenty deployment guidance ↗Review Twenty's current Compose stack
Use the current upstream requirements and dependency versions when preparing the container stack.
Review Twenty requirements ↗Choose Zima hardware for Twenty
Twenty is heavier than a simple PHP CRM because its official stack includes separate worker, PostgreSQL and Redis services.
Is this a small all-in-one CRM or a heavier automation/workflow deployment?
Small-team all-in-one Twenty
Use 16 GB with SSD-backed PostgreSQL.
- Best compact choiceZimaBoard 2 1664
- Storage-oriented alternativeZimaCube 2 Standard
Heavier workflows/imports and broader services
Use stronger CPU and expandable SSD/storage.
- Higher-headroom platformZimaCube 2 Pro
These are practical recommendations, not official Twenty user-count tiers.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 1664 | Small Twenty CRM deployments. | Server, worker, PostgreSQL and Redis on one host. |
|
The N150 can become CPU-bound if worker automation grows. | Get Now |
| ZimaCube 2 Standard | Twenty with larger local file storage. | CRM stack plus broader storage and backups. |
|
8 GB RAM offers less stack headroom than ZimaBoard 2 1664. | Get Now |
| ZimaCube 2 Pro | Heavier Twenty automation and CRM workloads. | More worker jobs, database activity and broader service consolidation. |
|
Actual capacity depends on workflows, integrations and database size. | 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 Twenty RAM, CPU, PostgreSQL, Redis, workers and ZimaOS deployment.
How much RAM does Twenty need?
Twenty does not publish a numerical official whole-host RAM minimum.
How many CPU cores does Twenty need?
No numerical official core minimum is published.
Which database does Twenty use?
The current official Docker Compose stack uses PostgreSQL 16.
Does Twenty use Redis?
Yes. Redis is part of the current official Docker stack.
Why does Twenty have a worker container?
Background jobs and workflow processing run separately from the main server container.
Does Twenty need a GPU?
No dedicated GPU is required for the core CRM platform.
Can ZimaBoard 2 run Twenty?
Yes. The 16 GB model is the safer compact all-in-one choice for the current server/worker/PostgreSQL/Redis stack.
When should I choose ZimaCube 2 Pro?
When worker automation, imports, database load or broader service consolidation needs stronger CPU.
What sources informed this Twenty hardware guide?
Current Twenty Docker install script and official Compose configuration plus current Zima product pages.
