Buddy Enterpriseのハードウェア要件：RAM、CPU、ストレージ、CIランナー
RAM、CPU、Dockerワーカー、CIの同時実行数、キャッシュ、アーティファクトを考慮したPlan Buddy Enterpriseのハードウェアと、実用的なZimaOS導入の推奨事項を計画します。
Buddy Enterprise hardware requirements at a glance
Size Buddy Enterprise from verified upstream requirements first, then add headroom for the actual workload and persistent data.
- RAM
- No universal official minimum published
- CPU
- No universal official minimum published
- Storage
- Repositories, Docker layers, caches, artifacts, logs and backups
- Deployment
- Docker-based self-hosted/Enterprise platform
- Runners
- Distributed runners can be added to scale builds
- Best Zima starting point
- ZimaCube 2 Pro for a small local CI node; separate runners as concurrency grows
From official requirements to the right setup
Start with current upstream facts for Buddy Enterprise, 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
- Pipeline concurrency
- Resource profile per pipeline
- Docker builds
- Multi-arch builds
- Runner count
- Cache size
- Artifact retention
- Repository size
Official minimum requirements
Buddy documents self-hosted architecture and per-pipeline resource profiles but does not publish one universal whole-host CPU/RAM minimum.
Do not treat the Nano/Small/Medium/Large pipeline profiles as Buddy server minimums. Host sizing must cover concurrent pipelines, Buddy services, Docker/Sysbox, caches and runner overhead.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No universal whole-host minimum published | Determined by concurrent pipeline/runner workloads. | |
| No universal whole-host minimum published | Determined by concurrent pipeline resource profiles. | |
| 2 GB/2 vCPU Nano through 16 GB/4 vCPU X2Large | Per-pipeline allocation profiles, not server minimums. | |
| Docker-based | Buddy Enterprise operates on customer infrastructure using Docker. | |
| Linux recommended | Buddy notes Docker works on supported OSes and recommends Linux for on-premises use. | |
| QEMU on every worker | Required for multi-arch Docker builds. | |
| Not required | Only specific CI jobs may independently require GPU. |
When to upgrade your hardware
Build queue growth
Cache/artifact growth
Multi-arch/build complexity
Plan hardware growth with confidence
Fast CI storage
Use SSD/NVMe for repositories, Docker layers and caches.
SSD/NVMeMore RAM
Useful for concurrent medium/large pipeline profiles.
16 GB+ based on concurrencyArtifact capacity
Expand storage for caches and artifacts.
ZimaCube storageDistributed runners
Scale out build compute rather than only scaling the main instance.
Additional workers / ZimaCube 2 Pro-class nodesCan it run on ZimaOS?
Custom install Buddy Enterprise in ZimaOS
No specific public official ZimaOS App Store page was verified, so the SOP requires Custom Install.
Custom install Buddy Enterprise in the ZimaOS app ↗Use Buddy's self-hosted architecture
Buddy Enterprise uses Docker and can add distributed runners for build capacity.
Open Buddy Self-Hosted docs ↗Keep build dependencies on every worker
Sysbox and QEMU requirements apply to specific Docker/multi-arch workflows on self-hosted workers.
Open Buddy self-hosted troubleshooting ↗Zima hardware for Buddy Enterprise
Buddy Enterprise is a CI platform, so build runners—not just the web/control service—determine hardware demand.
Choose by workload
Use a stronger CPU host and fast SSD, keeping concurrency conservative.
Scale out with runners and size each worker for its build profile.
Pipeline resource profiles are workload allocations, not an official whole-host 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 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 Buddy Enterprise need?
Buddy does not publish one universal whole-host RAM minimum.
Does Buddy provide resource sizes for pipelines?
Yes. Buddy documents profiles from 2 GB/2 vCPU Nano up to 16 GB/4 vCPU X2Large, but these are per-pipeline allocations.
Does Buddy Enterprise use Docker?
Yes. Buddy states that Docker is the underlying technology for the on-premises product.
What OS does Buddy recommend?
Buddy recommends Linux for the self-hosted deployment.
How do I scale CI execution?
Add distributed runners and size them from build concurrency and job requirements.
What is needed for multi-arch Docker builds?
Buddy requires QEMU on every self-hosted worker used for multi-arch builds.
Does Buddy itself need a GPU?
No. Specific CI jobs may independently need GPU hardware.
When should I use ZimaCube 2 Pro?
For local build-heavy workloads where the stronger CPU and storage options are useful.
