More active users, imports and automations raise CPU, Redis/database and worker activity.
Growing teams.Krav på maskinvara för Plane: RAM, CPU, lagring och PostgreSQL
Planera självhostning av Plane för CPU, RAM, lagring, PostgreSQL, Redis, sökning och bilagor, med praktiska rekommendationer för distribution på ZimaOS.
Plane requirements at a glance
Plane is a multi-service project-management platform, so sizing must include its stateful dependencies rather than the web app alone.
- Current self-host baseline
- Plane's current self-host overview lists 4 CPU cores, 8 GB RAM and 50 GB storage as the minimum infrastructure footprint.
- Community Docker guidance
- The current Docker Compose guide still lists at least 2 vCPUs and 4 GB RAM, with 8 GB recommended, for Community Edition.
- Production sizing
- Plane's newer production guidance says real capacity depends on active users, work-item history, attachments, imports, automation, collaboration and search/AI indexing.
- Dependencies
- Self-hosted Plane uses PostgreSQL and other stateful services; newer production guidance recommends external database/object storage for production and high availability.
- Storage
- Use at least 50 GB for a conservative new deployment, then add capacity for attachments, database growth, search indexes and backups.
- Best Zima starting point
- ZimaBoard 2 1664 is the safer compact choice because it provides 4 cores, 16 GB RAM and 64 GB onboard storage; ZimaCube 2 is better when attachments and search data grow.
From official requirements to the right setup
Use Plane's newer platform baseline for conservative sizing, then refine by edition and workload.
-
Official requirements
For a new self-hosted deployment, plan around the current public baseline of 4 CPU cores, 8 GB RAM and 50 GB storage rather than only the older 2-vCPU/4-GB Community Docker floor.
-
Confirm your needs
Estimate active users, work-item/activity history, attachment retention, imports, automations, realtime collaboration and optional search/AI indexing.
-
Leave room to grow
Persist PostgreSQL and object/file data carefully. For production, Plane's guidance increasingly favors external stateful services rather than keeping every dependency on one Docker host.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with Plane's Docker deployment, put stateful data on SSD-backed storage, and treat one-box deployment as evaluation/small-team infrastructure rather than high availability.
Check every playback client
- Plane edition
- Active users
- PostgreSQL persistence
- Attachment storage
- Search enabled
- Automation/import volume
- 50 GB+ capacity
- Backup retention
Official minimum requirements
Plane currently exposes more than one official baseline depending on edition and deployment surface.
For new hardware pages, use the newer public self-host overview's 4-core/8-GB/50-GB minimum as the conservative platform baseline, while noting that the Community Docker guide still documents a lower 2-vCPU/4-GB floor with 8 GB recommended.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Current platform CPU minimum | 4 CPU cores | Newest public self-host overview. |
| Current platform RAM minimum | 8 GB | Newest public self-host overview. |
| Current platform storage minimum | 50 GB | Newest public self-host overview. |
| Community Docker CPU floor | 2 vCPUs | Docker Compose guide for Community Edition. |
| Community Docker RAM floor | 4 GB | Docker Compose guide; 8 GB recommended. |
| Supported CPU architectures | x64 / AMD64 and AArch64 / ARM64 | Current Docker Compose prerequisites. |
When to upgrade your hardware
Plane should scale when database/search state, collaboration or attachment volume outgrows the initial Docker host.
Realtime collaboration and automation increase
Search and activity history expand
Attachments and object storage grow
OpenSearch/advanced search and long work-item history increase memory and storage demand.
Long-running workspaces.Files can become the main long-term capacity driver.
File-heavy product and engineering teams.Plan hardware growth with confidence
Scale Plane by separating stateful services and storage as the workload matures.
Use SSD-backed PostgreSQL and local state
Database latency and durable persistence matter more than raw web-app compute.
Use SATA/NVMe on ZimaBoard 2 or SSD tiers on ZimaCube 2.Use 16 GB for a safer compact all-in-one host
Provides more headroom than the 8 GB platform minimum for PostgreSQL, cache and workers.
ZimaBoard 2 1664.Use ZimaCube for attachments and broader storage
Multi-drive capacity helps when files, backups and search indexes grow.
ZimaCube 2 Standard.Use stronger CPU for heavier collaboration/search
More cores help workers, imports, search and broader service consolidation.
ZimaCube 2 Pro.Can it run on ZimaOS?
No public official ZimaOS one-click Plane App Store page was verified for this guide. Plane can be deployed through Install Custom App using its official Docker path.
Custom install Plane in ZimaOS
Use Install Custom App with Plane's Docker deployment, persist database/object data, and allocate at least the current conservative 4-core/8-GB/50-GB baseline.
Custom install Plane in the ZimaOS app ↗Use Plane's official Docker deployment
Plane documents Docker Compose as a supported self-hosting method and provides current prerequisites for CPU, RAM and architecture.
Review Plane Docker Compose ↗Use production guidance as the workload grows
Plane's self-hosting guidance recommends external stateful services and workload-driven sizing for production environments.
Review Plane self-hosting guidance ↗Choose Zima hardware for Plane
Plane's current platform baseline is heavier than many productivity apps; RAM, storage and stateful services justify starting above the smallest Zima configuration.
Is this a small all-in-one Plane deployment or a heavier collaboration/search workload?
Small-team all-in-one Plane
Use 16 GB and at least 50 GB durable storage to leave room above the current platform baseline.
- Best compact choiceZimaBoard 2 1664
- Storage-first alternativeZimaCube 2 Standard
Heavier search, automation or broader consolidation
Use stronger CPU and expandable SSD/storage.
- Higher-headroom platformZimaCube 2 Pro
These are practical mappings to current Plane baselines, not guaranteed user-count or automation throughput tiers.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 1664 | Small self-hosted Plane deployments. | Plane with PostgreSQL, cache/workers and moderate attachments. |
|
64 GB onboard storage only narrowly clears the 50 GB baseline; use external SSD for durable growth. | Get Now |
| ZimaCube 2 Standard | Storage-heavy Plane deployments. | Plane with larger attachments, backups and broader NAS duties. |
|
8 GB matches the current platform minimum but leaves less memory headroom than ZimaBoard 2 1664. | Get Now |
| ZimaCube 2 Pro | Heavier Plane collaboration/search stacks. | More workers, database/search activity, attachments and co-hosted services. |
|
Single-host deployment is not equivalent to Plane's high-availability production architecture. | 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 Plane RAM, CPU, storage, Docker and ZimaOS deployment.
How much RAM does Plane need?
The newest public self-host overview lists 8 GB RAM as the platform minimum, while the Community Docker guide still lists 4 GB minimum and 8 GB recommended.
How many CPU cores does Plane need?
The newest self-host overview lists 4 CPU cores; the Community Docker guide documents a lower 2-vCPU floor.
How much storage does Plane need?
The current public self-host overview lists 50 GB minimum, with more needed for attachments, database growth, search and backups.
Why do Plane requirements differ across docs?
Plane publishes different baselines by edition and deployment path; newer platform-level guidance is more conservative than the Community Docker floor.
Does Plane use PostgreSQL?
Yes. PostgreSQL is one of Plane's core stateful dependencies, and production guidance favors external durable state as deployments mature.
Does Plane need a GPU?
No dedicated GPU is required for the core project-management platform.
Can ZimaBoard 2 run Plane?
Yes. The 16 GB model is the safer compact choice because it meets the current 4-core baseline and provides memory headroom above 8 GB.
When should I choose ZimaCube 2 Pro?
When search, automation, attachments or broader service consolidation justify stronger CPU and expandable storage.
What sources informed this Plane hardware guide?
Current Plane self-hosting, Docker Compose and production guidance plus current Zima product pages.
