Exigences matérielles de Hook0 : RAM, CPU, stockage et livraison des webhooks
Planifiez le matériel Hook0 pour la RAM, le CPU, PostgreSQL, le débit des webhooks, la concurrence des workers et des recommandations pratiques de déploiement pour le développement de ZimaOS.
Hook0 hardware requirements at a glance
Size Hook0 from verified upstream requirements first, then add headroom for workload and persistent data.
- RAM
- No numerical official minimum published
- CPU
- No numerical official minimum published
- Storage
- PostgreSQL volume + Mailpit development data + logs/backups
- Database
- PostgreSQL
- Ports
- 8001 frontend, 8081 API, 8025 Mailpit UI, 1025 SMTP, 5432 PostgreSQL in dev Compose
- Best Zima starting point
- ZimaBoard 2 832 for development/testing only
From official requirements to the right setup
Start with current upstream facts for Hook0, then size the real workload rather than copying generic container or app-store labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Webhook events/sec
- Output-worker concurrency
- PostgreSQL size
- Retry/retention policy
- Development vs production
- Observability
- Email verification
- Backup retention
Official minimum requirements
Hook0's public Docker Compose guide does not publish numerical whole-host CPU/RAM requirements and explicitly labels the Compose topology development/testing only.
For production, the official guide says the Compose setup does not address scalability, resilience, high availability, observability, or 24/7 operations and directs users to Hook0 Cloud.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical minimum published | Webhook/worker throughput dependent. | |
| No numerical minimum published | Multi-service stack. | |
| PostgreSQL 18 | Persistent postgres-data volume. | |
| Postgres, Mailpit, API, frontend, output-worker | Current local stack. | |
| 8001 / 8081 | Local testing endpoints. | |
| Compose guide is development/testing only | Not production-ready. | |
| Not required | No GPU workload. |
When to upgrade your hardware
Webhook throughput growth
Retention/database growth
Production requirement
Plan hardware growth with confidence
SSD PostgreSQL
Keep webhook state on SSD/NVMe.
SSD/NVMeMore RAM
Useful for higher concurrency in a lab/staging deployment.
ZimaBoard 2 1664Stronger CPU
Useful for more worker concurrency.
ZimaCube 2 ProProduction architecture
Add external DB, observability, HA, and resilient workers as required.
Dedicated infrastructureCan it run on ZimaOS?
Custom install Hook0 in ZimaOS for development/testing
No specific public ZimaOS per-app page was verified; the upstream Compose setup itself is explicitly non-production.
Custom install Hook0 in the ZimaOS app ↗Use the official Compose guide only for local/test deployments
It launches PostgreSQL, Mailpit, API, frontend, and worker services.
Open Hook0 Docker Compose docs ↗Do not label this topology production-ready
The vendor explicitly excludes scalability, resilience, HA, observability, and 24/7 concerns from this setup.
Open Hook0 production warning ↗Zima hardware for Hook0
Hook0 can run in a modest development environment, but production webhook delivery is an architecture/reliability problem, not just a hardware-sizing problem.
Choose by workload
ZimaBoard 2 832 is a practical local-stack starting point.
Use a production-grade architecture instead of treating the dev Compose file as sufficient.
Zima recommendations here apply only to development/testing unless a separate production architecture is designed.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services and small databases | Single-app or small multi-app deployments |
|
8 GB RAM can limit larger Java/database/collaboration stacks | Get Now |
| ZimaBoard 2 1664 | Memory-heavier services and larger small-team apps | Moderate multi-container and database workloads |
|
CPU remains the 4-core N150, so heavier Java/indexing workloads can still be CPU-limited | Get Now |
| ZimaCube 2 Pro | CPU-heavy, database-heavy, and higher-concurrency services | Jira, larger helpdesk/collaboration stacks, and heavier indexing |
|
16 GB RAM can still be low for large enterprise Jira deployments | 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
Does Hook0 publish a RAM minimum?
No numerical whole-host RAM minimum is published.
Which database does the development Compose stack use?
PostgreSQL 18.
Which services are included?
PostgreSQL, Mailpit, API, frontend, and output-worker.
Is the official Docker Compose setup production-ready?
No. Hook0 explicitly labels it development/testing only.
What ports are used in the development stack?
Frontend 8001, API 8081, Mailpit 8025/1025, and PostgreSQL 5432.
Can ZimaBoard 2 832 run Hook0?
Yes for development/testing.
Does Hook0 need a GPU?
No.
What changes for production?
You need a design for scalability, resilience, HA, observability, and operations.
