Appwrite exposes worker-per-core tuning because request and realtime services scale with CPU availability.
Apps with growing API traffic or many concurrent realtime clients.Hardwarevereisten voor Appwrite: RAM, CPU, swap en opslag
Plan hardware voor zelfgehoste Appwrite met de officiële minimumvereisten van 2 cores, 4 GB RAM en 2 GB swap, met praktische opslagvereisten voor een aangepaste ZimaOS-installatie.
Appwrite requirements at a glance
Appwrite has a clear self-hosting floor: 2 CPU cores, 4 GB RAM, 2 GB swap, a Docker-capable operating system and Docker Compose v2. Real production sizing grows with API/realtime load, database/cache usage, storage and compute functions/sites.
- CPU
- Official self-hosting minimum: 2 CPU cores.
- RAM
- Official self-hosting minimum: 4 GB RAM.
- Swap
- Official self-hosting minimum: 2 GB swap memory.
- Storage
- No universal numerical disk minimum in the current installation prerequisites; database, object/file storage, logs, builds and backups determine capacity.
- Docker
- Requires an operating system that supports Docker and Docker Compose Version 2.
- Best Zima starting point
- ZimaBoard 2 832 exceeds the CPU/RAM minimum for development/small self-hosting; ZimaBoard 2 1664 or ZimaCube 2 Pro gives more production headroom.
From official requirements to the right setup
Start from Appwrite's official minimum, then size the stateful database/cache/storage layer and compute workloads separately.
-
Official requirements
Reserve at least 2 CPU cores, 4 GB RAM and 2 GB swap, and use Docker Compose v2 on a supported host.
-
Confirm your needs
Estimate API and Realtime concurrency. Appwrite lets operators tune workers per CPU core, so CPU demand grows with request traffic and service concurrency.
-
Leave room to grow
Plan database, Redis, storage buckets, logs and backups on durable fast storage. These stateful services determine much of the long-term capacity requirement.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App with Appwrite's official Docker installer/Compose stack, persist every stateful volume, and add extra CPU/RAM for Functions/Sites builds or other compute workloads.
Check every playback client
- API request volume
- Realtime connection count
- Database size
- Storage bucket growth
- Functions/Sites build workload
- Redis/database persistence
- Backup/log retention
- Other ZimaOS apps
Official minimum requirements
Appwrite's current self-hosting installation guide explicitly publishes CPU, RAM and swap minimums.
The 2-core/4-GB/2-GB-swap profile is the official installation floor, not a production throughput guarantee. Appwrite's production docs expect operators to monitor and scale CPU, memory, storage, database and containers as workload grows.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | 2 CPU cores minimum | Current official self-hosting requirement. |
| RAM | 4 GB minimum | Current official self-hosting requirement. |
| Swap | 2 GB minimum | Current official self-hosting requirement. |
| Container runtime | Docker-capable OS | Appwrite is designed to self-host through Docker. |
| Compose | Docker Compose Version 2 | Current installation requirement. |
| Storage minimum | No universal numerical minimum published | Database, files, build artifacts, logs and backups determine disk usage. |
When to upgrade your hardware
Appwrite should scale when API/realtime traffic, stateful services or compute builds push beyond the minimum deployment envelope.
API and Realtime concurrency saturate CPU
Database, Redis or storage becomes I/O-bound
Functions and Sites add build/runtime compute
The stateful data plane can become the bottleneck even when API containers still have CPU headroom.
Production apps with growing data and file storage.Function and site builds/runtime containers add CPU, memory and temporary storage demand beyond the base platform.
Teams using Appwrite Compute heavily.Plan hardware growth with confidence
Scale Appwrite by protecting stateful services first, then add CPU/RAM for API/realtime workers and compute workloads.
Use SSD-backed stateful volumes
Database, Redis and Appwrite storage benefit from reliable low-latency persistence.
Use SATA/NVMe with ZimaBoard 2 or SSD tiers on ZimaCube 2.Move to 16 GB for more production headroom
More RAM helps the multi-container platform, stateful services and compute workloads coexist.
ZimaBoard 2 1664 is a compact 16 GB option.Use stronger CPU for higher API/compute load
More cores allow additional workers and faster build/function workloads when the 4-core N150 is saturated.
ZimaCube 2 Pro provides a 10-core/12-thread Core i5.Separate stateful services at larger scale
Appwrite documents scaling database and Redis as standard clusters according to workload needs.
Move beyond a single all-in-one Zima host when production architecture requires independent scaling or HA.Can it run on ZimaOS?
Appwrite is not currently confirmed as a public official one-click ZimaOS App Store page in the sources checked for this guide. It can still be deployed through Install Custom App using Appwrite's official Docker installation path.
Custom install Appwrite in ZimaOS
Use Install Custom App with Appwrite's generated Docker Compose stack or a carefully adapted official configuration. Persist all stateful volumes and ensure the host meets the 2-core/4-GB/2-GB-swap minimum.
Custom install Appwrite in the ZimaOS app ↗Use the official Appwrite Docker installer
Appwrite's current self-hosting guide uses Docker and a web-based installation wizard to generate the deployment.
Review Appwrite self-hosting ↗Plan production scaling beyond the minimum
Appwrite's production docs cover worker-per-core tuning, stateful database/Redis scaling, resource limits and monitoring.
Review Appwrite scaling guidance ↗Choose Zima hardware for Appwrite
Appwrite's 2-core/4-GB floor fits ZimaBoard 2 easily, but a production multi-service backend benefits from 16 GB RAM and fast persistent storage.
Is this a development/small Appwrite backend or a heavier production self-hosted platform?
Development, homelab or small app
ZimaBoard 2 832 exceeds the official CPU/RAM minimum; add SSD-backed stateful storage and the required swap.
- Best starting pointZimaBoard 2 832
- More memory headroomZimaBoard 2 1664
Higher API, realtime or compute workload
Use stronger CPU, 16 GB RAM and expandable SSD storage before considering multi-node scaling.
- Higher-headroom platformZimaCube 2 Pro
These recommendations are not guarantees for API requests, realtime connections or function throughput. Database size, storage, builds, functions and other ZimaOS services can change capacity.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Development and small self-hosted Appwrite backends. | Core Appwrite services, database/cache, light storage and moderate API traffic. |
|
Add SSD-backed persistent volumes and configure the official 2 GB swap minimum; 8 GB RAM does not guarantee production throughput. | Get Now |
| ZimaBoard 2 1664 | Appwrite with more data, realtime traffic or light Compute use. | Larger multi-container memory budget, database/cache and additional functions/services. |
|
CPU remains 4 cores; compute-heavy builds or high API concurrency may need a stronger processor. | Get Now |
| ZimaCube 2 Pro | Heavier production-style Appwrite on one self-hosted system. | Higher API/realtime load, more stateful data, functions/sites builds and other developer services. |
|
High availability and large-scale production may still require separated database/cache/application infrastructure. | 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 Appwrite RAM, CPU, swap, storage, Docker and ZimaOS custom installation.
How much RAM does Appwrite need?
Appwrite's current official self-hosting requirement is at least 4 GB RAM.
How many CPU cores does Appwrite need?
The current official self-hosting requirement is at least 2 CPU cores.
Does Appwrite require swap?
Yes. The current installation guide lists 2 GB of swap memory as a minimum requirement.
How much storage does Appwrite need?
The current installation prerequisites do not publish one universal disk minimum. Database data, storage buckets, logs, build artifacts and backups determine capacity.
Does Appwrite need an SSD?
SSD is not listed as a strict installation requirement, but SSD-backed database, Redis and storage volumes are a strong practical choice.
Does Appwrite need a GPU?
No dedicated GPU is required for the core Appwrite platform. Compute workloads should be sized according to the functions or sites you run.
Can ZimaBoard 2 run Appwrite?
Yes. The 8 GB ZimaBoard 2 exceeds the official 4 GB RAM and 2-core minimum; add suitable persistent storage and at least the required swap.
When should Appwrite move beyond one Zima server?
Move toward separate or clustered stateful services when database, Redis, storage, API/realtime or availability needs can no longer be met predictably on one host.
What sources informed this Appwrite hardware guide?
The guide uses current Appwrite installation, production and scaling documentation plus current Zima product pages for practical hardware matching.
