Configuration matérielle requise pour Bookwyrm : RAM, processeur, stockage, fédération et recherche
Planifiez le matériel Bookwyrm pour la RAM, le CPU, PostgreSQL, Redis, la fédération, les médias, la recherche et des recommandations pratiques de déploiement de ZimaOS.
Bookwyrm hardware requirements at a glance
Size Bookwyrm from verified upstream requirements first, then add headroom for the actual workload and persistent data.
- RAM
- No numerical official minimum published
- CPU
- No numerical official minimum published
- Storage
- Database + uploaded media/static assets + backups
- Database
- PostgreSQL
- Queues/cache
- Redis activity and broker subsystems
- Best Zima starting point
- ZimaBoard 2 1664 for a small instance; ZimaCube 2 Pro for larger federation/search workloads
From official requirements to the right setup
Start with current upstream facts for Bookwyrm, then size the workload rather than copying generic container or catalog labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Local users
- Federated traffic
- Book imports
- PostgreSQL size
- Redis/worker queues
- Media storage
- Search/index work
- Backup retention
Official minimum requirements
BookWyrm documents its production service stack but does not publish a numerical whole-host CPU, RAM, or disk minimum.
Do not invent a single BookWyrm RAM minimum. Whole-host sizing must include PostgreSQL, Redis, workers, federation activity, media and backups.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Workers, federation, imports and search determine compute use. | |
| No numerical official minimum published | PostgreSQL, Redis and worker count determine memory. | |
| Docker + Docker Compose | Production branch contains deployment-specific Compose configuration. | |
| PostgreSQL | Required in both Docker and dockerless production paths. | |
| Redis | Used for activity and broker subsystems. | |
| nginx, Python venv/pip, gunicorn and related packages | Docker production bundles these concerns into services. | |
| Not required | No GPU baseline for federation/social reading. |
When to upgrade your hardware
Federation queue growth
Database/search pressure
Media growth
Plan hardware growth with confidence
SSD PostgreSQL
Keep PostgreSQL and active application state on SSD.
SSD/NVMeMore RAM
Useful for PostgreSQL, Redis and workers on a larger instance.
ZimaBoard 2 1664 or higherMedia/backup capacity
Expand storage for covers, uploads and backups.
ZimaCube 2 StandardStronger CPU
Useful for larger federation, imports, search and worker concurrency.
ZimaCube 2 ProCan it run on ZimaOS?
Custom install Bookwyrm in ZimaOS
No specific public official ZimaOS App Store page was verified, so the SOP requires Custom Install.
Custom install Bookwyrm in the ZimaOS app ↗Use BookWyrm's production branch/Compose
The production guide is the source of truth for service relationships, secrets, Redis and PostgreSQL.
Open BookWyrm production install ↗Plan SMTP and federation networking
BookWyrm production requires domain/DNS and email-service configuration in addition to application resources.
Open BookWyrm production guide ↗Zima hardware for Bookwyrm
BookWyrm is a multi-service social/federation application, so a small instance still needs database, queues/workers, media and backup planning.
Choose by workload
Use 16 GB RAM for comfortable multi-service headroom and SSD-backed database storage.
CPU, RAM and storage concurrency become more important.
Zima recommendations are workload mappings; upstream does not publish one numerical minimum.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 1664 | Memory-heavier web, database, CI controller, and collaboration workloads | Moderate multi-container workloads |
|
CPU is still a 4-core N150; more RAM does not raise build or browser-execution throughput | Get Now |
| ZimaCube 2 Standard | Storage-heavy mail, repositories, attachments, and media | Large persistent datasets where drive bays matter most |
|
8 GB RAM can be less suitable than ZimaBoard 2 1664 for memory-heavy services | Get Now |
| ZimaCube 2 Pro | CPU-heavy CI, larger SQL/search workloads, and higher concurrency | Build orchestration, larger databases, and consolidated services |
|
16 GB RAM can still constrain very large enterprise or browser-grid workloads | 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
How much RAM does BookWyrm need?
Upstream does not publish a numerical whole-host RAM minimum.
Which database does BookWyrm use?
PostgreSQL.
Does BookWyrm use Redis?
Yes. Production configuration uses Redis-backed activity and broker subsystems.
How is BookWyrm deployed in production?
The official guide uses the production branch with Docker and Docker Compose.
What usually drives CPU usage?
Federation activity, background workers, imports, image handling and search/index work.
Can ZimaBoard 2 1664 run a small instance?
It is a practical small-instance starting point because BookWyrm is a multi-service stack.
Does BookWyrm need a GPU?
No.
When should I choose ZimaCube 2 Pro?
For larger federation volume, more users, imports/search workload, or broader consolidation.
