More API requests, Admin App users and realtime activity can push the app container beyond the minimum profile.
Growing applications and multi-user internal tools.Directusのハードウェア要件：RAM、vCPU、データベースとストレージ
公式の最小要件である0.25 vCPU/512 MB、推奨コンテナサイズである1 vCPU/2 GBと、ZimaOSのデプロイガイダンスに基づいてDirectusのハードウェアを計画します。
Directus requirements at a glance
Directus publishes direct container resource guidance and distributes the platform as an official Docker image.
- Required minimum
- Directus' current docs list 1 × 0.25 vCPU / 512 MB as the required minimum container resources.
- Recommended minimum
- The docs list 2 × 1 vCPU / 2 GB as the recommended minimum resource profile.
- Database
- The Directus image supports multiple SQL databases/storage adapters; database resources are separate from the Directus app container sizing.
- Storage
- No universal numerical disk minimum. Database size, uploaded files, extensions, cache and backups determine capacity.
- GPU
- No GPU is required for the Directus API/Admin App itself.
- Best Zima starting point
- ZimaBoard 2 832 has ample resources for a small Directus deployment; 16 GB or ZimaCube 2 Pro adds database, file and multi-service headroom.
From official requirements to the right setup
Size Directus in layers: app-container resources first, then database, file storage and extension workloads.
-
Official requirements
Use Directus' published container floor: 1 × 0.25 vCPU / 512 MB required, with 2 × 1 vCPU / 2 GB documented as the recommended minimum profile.
-
Confirm your needs
Choose the database and size it independently. Directus supports common SQL database engines through its Docker image.
-
Leave room to grow
Plan uploaded assets and storage adapters separately from the app container. File libraries and backups can become the main disk requirement.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with the official directus/directus image, persist uploads/database data, set required environment variables, and monitor API/database latency before increasing container resources.
Check every playback client
- Expected API request volume
- Admin App users
- Database engine
- Database size
- Uploaded file volume
- Extensions/hooks/flows
- Cache/Redis usage
- Other ZimaOS services
Official minimum requirements
Directus currently publishes explicit application-container resource guidance for self-hosted deployments.
The 0.25 vCPU/512 MB figure is the required container minimum, not a whole-server recommendation. Database, files and production redundancy must be budgeted separately.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Required app-container minimum | 1 × 0.25 vCPU / 512 MB | Current Directus self-hosting requirement. |
| Recommended minimum profile | 2 × 1 vCPU / 2 GB | Current Directus recommendation; preserve this as container-resource guidance rather than whole-host hardware. |
| Docker | Official Directus Docker image | Directus distributes the self-hosted application as a Docker image. |
| Database | Multiple supported SQL engines | The Docker image includes optional dependencies for supported databases/storage adapters. |
| Storage minimum | No universal numerical minimum published | Database, files, cache, logs and backups drive capacity. |
| GPU | Not required for core Directus | AI/image-processing extensions may have separate needs, but core Directus does not require GPU hardware. |
When to upgrade your hardware
Directus should scale when API/Admin traffic, database performance or file/extension workloads outgrow the current container profile.
API concurrency raises sustained CPU or memory use
Database latency becomes visible
Files, extensions and flows add background work
Directus can remain lightly loaded while the SQL database becomes the actual bottleneck.
Large collections, complex relations and higher query volume.Uploads, transformations, hooks, automation and custom extensions can change the resource profile significantly.
Content platforms using Directus as more than a simple API.Plan hardware growth with confidence
Scale Directus by separating app, database and storage bottlenecks instead of treating the 512 MB minimum as a production target.
Use SSD-backed database and uploads
Low-latency persistent storage improves database responsiveness and asset operations.
Use SATA/NVMe with ZimaBoard 2 or SSD tiers on ZimaCube 2.Move to 16 GB for app + database consolidation
More RAM gives Directus, database cache and other containers room to coexist.
ZimaBoard 2 1664 is a compact 16 GB option.Use stronger CPU for higher API/automation load
More cores help when API concurrency, flows and extensions saturate the N150 class.
ZimaCube 2 Pro provides a 10-core/12-thread Core i5.Separate database/storage for larger production deployments
At higher scale, split stateful services so they can be tuned and backed up independently.
Use external or separate infrastructure when production reliability/scale requires it.Can it run on ZimaOS?
Directus is not currently confirmed as a public official one-click ZimaOS App Store page in the sources checked for this guide. It can be deployed cleanly through Install Custom App using the official Directus Docker image.
Custom install Directus in ZimaOS
Use Install Custom App with directus/directus, configure database/storage environment variables, persist uploads and stateful data, and expose the Directus web/API port through ZimaOS networking.
Custom install Directus in the ZimaOS app ↗Use the official Directus Docker image
Directus distributes its self-hosted platform as an official Docker image and documents multi-database/storage support.
Review Directus Docker deployment ↗Keep container sizing separate from database sizing
The published 0.25 vCPU/512 MB minimum refers to Directus container resources; SQL database and file storage require their own budget.
Review Directus self-hosting requirements ↗Choose Zima hardware for Directus
Directus' app-container floor is small enough for ZimaBoard 2; database, file storage and automation determine when larger hardware becomes useful.
Is this a small Directus backend or a heavier API/database/content platform?
Small project or internal tool
ZimaBoard 2 832 has far more RAM/CPU than the required app-container minimum; add durable database/storage volumes.
- Best starting pointZimaBoard 2 832
- More consolidation headroomZimaBoard 2 1664
Higher API traffic, large database or automation
Use stronger CPU and storage when the wider Directus/database stack becomes the bottleneck.
- Higher-headroom platformZimaCube 2 Pro
These recommendations are not API-throughput guarantees. Database complexity, realtime traffic, extensions, flows and file processing can materially change capacity.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small Directus apps and internal tools. | Directus, small SQL database, uploads and moderate API/Admin traffic. |
|
The app container easily fits; database design and persistent storage are more likely to limit performance. | Get Now |
| ZimaBoard 2 1664 | Directus plus larger database cache and more services. | More API concurrency, extensions, automation and co-hosted developer tools. |
|
16 GB is whole-host headroom, not an official Directus host requirement. | Get Now |
| ZimaCube 2 Pro | Heavier Directus API/database/content workloads. | Larger SQL database, more flows/extensions, uploads and broader self-hosted services. |
|
Large production systems may still need separate database/storage and redundancy rather than one stronger host. | 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 Directus RAM, vCPU, database, storage, Docker and ZimaOS deployment.
How much RAM does Directus need?
Directus currently lists 512 MB as the required app-container minimum and 2 GB in its recommended minimum profile.
How much CPU does Directus need?
The required minimum is listed as 0.25 vCPU for one container, while the recommended profile is documented as 2 × 1 vCPU.
Does Directus need a database?
Yes. Directus supports multiple SQL databases, and database resources should be sized separately from the Directus app container.
How much storage does Directus need?
There is no universal official disk minimum. Database data, uploaded assets, cache, logs and backups determine capacity.
Does Directus need an SSD?
SSD is not stated as a strict minimum, but SSD-backed database and asset storage is a strong practical choice.
Does Directus need a GPU?
No dedicated GPU is required for the core Directus API/Admin App.
Can ZimaBoard 2 run Directus?
Yes. The 8 GB ZimaBoard 2 has ample headroom over the required app-container resource floor for small deployments.
When should Directus use ZimaCube 2 Pro?
When database/API load, extensions, automation or broader service consolidation makes stronger CPU and storage more useful than the compact N150 platform.
What sources informed this Directus hardware guide?
The guide uses Directus' current self-hosting requirements and Docker guide plus current Zima product pages for practical hardware matching.
