Budibase-Hardwareanforderungen: RAM, CPU, Speicher und Low-Code-Apps
Planen Sie die Hardware für Budibase hinsichtlich RAM, CPU, Docker-Diensten, CouchDB, Redis, Objektspeicher, Benutzerzahl und praktischen Empfehlungen für die Bereitstellung unter ZimaOS.
Budibase hardware requirements at a glance
Size Budibase from verified upstream requirements first, then add headroom for the actual workload and persistent data.
- RAM
- Official recommended reference: 6 GB for most use cases
- CPU
- Official recommended reference: 2 cores for most use cases
- Storage
- Persist /data or Compose service volumes
- Deployment
- All-in-one Docker or Docker Compose
- Services
- Compose includes multiple Budibase services and uses CouchDB/Redis/MinIO-related settings
- Best Zima starting point
- ZimaBoard 2 832 meets the 2-core/6-GB recommendation; 1664 gives better production headroom
From official requirements to the right setup
Start with current upstream facts for Budibase, 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
- App count
- Concurrent users
- Automation volume
- CouchDB data
- File/object storage
- External data sources
- Integration/API load
- Backup retention
Official minimum requirements
Budibase publishes a practical resource recommendation rather than a universal hard minimum.
For most use cases, Budibase documentation says 2 cores and 6 GB RAM should be enough. Treat this as a recommended reference; actual requirements depend on expected usage.
| Requirement | Official minimum | What this supports |
|---|---|---|
| 2 cores | Budibase says this should be enough for most use cases. | |
| 6 GB | Budibase says this should be enough for most use cases. | |
| Recent Docker required | All-in-one image and Docker Compose paths are documented. | |
| Linux host | Budibase recommends Linux for production self-hosting. | |
| /data for all-in-one; service volumes in Compose | Must survive container replacement. | |
| CouchDB, Redis, MinIO-related components/settings | Multi-service platform, not just a single web UI. | |
| Not required | No GPU baseline for low-code app hosting. |
When to upgrade your hardware
More users/apps
Automation pressure
Data/file growth
Plan hardware growth with confidence
SSD application data
Keep CouchDB/app state and active object data on SSD.
SSD/NVMeMore RAM
Provides comfortable headroom above the 6 GB reference.
ZimaBoard 2 1664File/object capacity
Expand storage as app attachments/object data grow.
ZimaCube 2 StandardHigher concurrency CPU
Use stronger CPU for larger teams and automation-heavy workloads.
ZimaCube 2 ProCan it run on ZimaOS?
Custom install Budibase in ZimaOS
No specific public official ZimaOS App Store page was verified, so the SOP requires Custom Install.
Custom install Budibase in the ZimaOS app ↗Use the official Budibase Docker path
The all-in-one image is budibase/budibase:latest with persistent /data.
Open Budibase Docker docs ↗Use Compose for the full multi-service topology
Docker Compose exposes the platform's internal service relationships and production configuration.
Open Budibase Compose docs ↗Zima hardware for Budibase
Budibase is a multi-service low-code platform. Its published 2-core/6-GB recommendation makes ZimaBoard 2 832 feasible, but 16 GB provides more useful production headroom.
Choose by workload
ZimaBoard 2 832 meets the published general recommendation.
More RAM and stronger CPU reduce contention across the multi-service platform.
The 2-core/6-GB values are an official recommendation for most use cases, not a hard universal minimum.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light web, SQL, mail, and small developer services | Single-app or small multi-app workloads |
|
8 GB RAM and 4-core CPU limit larger databases, CI builds, and browser grids | Get Now |
| 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 Budibase recommend?
Budibase documentation says 6 GB RAM should be enough for most use cases.
How many CPU cores does Budibase recommend?
Budibase documents 2 cores as a practical recommendation for most use cases.
Are 2 cores and 6 GB a hard minimum?
No. Budibase states resource needs depend greatly on expected usage.
How can Budibase be self-hosted?
The official docs support an all-in-one Docker image and Docker Compose.
What data must be persistent?
The all-in-one deployment maps /data; Compose deployments persist the data of Budibase's internal services.
Can ZimaBoard 2 832 run Budibase?
Its 4-core CPU and 8 GB RAM exceed Budibase's 2-core/6-GB general recommendation, though production workload still determines headroom.
Does Budibase need a GPU?
No.
When should I choose ZimaCube 2 Pro?
For larger teams, heavier automation/API load, or broader consolidation.
