Each active user can hold connections, result sets and UI state, increasing JVM and server-database pressure.
Teams sharing one CloudBeaver server.CloudBeaver-Hardwareanforderungen: RAM, CPU, Java und Datenbankverbindungen
Informieren Sie sich über die Anforderungen von CloudBeaver an CPU, RAM, Java-Heap, Workspace-Speicher und gleichzeitige Datenbankverbindungen und wählen Sie anschließend die passende ZimaOS-Hardware aus.
CloudBeaver requirements at a glance
CloudBeaver Community is a Java web server for browser-based database administration. Current Community Google Cloud deployment guidance recommends at least 1 CPU and 4 GB RAM for optimal performance with a 100 GB disk image. This is deployment guidance rather than a universal minimum; real usage grows with concurrent users, active database sessions, drivers, query history and Java heap settings.
- CPU
- Current Community Google Cloud guidance: at least 1 CPU for optimal performance.
- RAM
- Current Community Google Cloud guidance: at least 4 GB RAM for optimal performance.
- Storage
- Community Google Cloud image guidance uses at least 100 GB disk; Docker Community itself can be deployed as a single container with a persistent workspace.
- Java heap
- CloudBeaver is a Java server and supports explicit JVM memory limits such as -Xmx2048M.
- Internal data
- CloudBeaver stores users, access-control data and query history in its server database/workspace.
- Best Zima starting point
- ZimaBoard 2 832 meets the current 4 GB guidance with substantial headroom; 1664 is better for more users, drivers and co-hosted developer services.
From official requirements to the right setup
CloudBeaver sizing starts with users and database-session concurrency, then Java heap and persistent workspace.
-
Official requirements
Use 1 CPU and 4 GB RAM as a current official Community deployment reference for optimal performance, not as a hard universal minimum.
-
Confirm your needs
Estimate simultaneous users, open connections and query activity. CloudBeaver is only the client/server management layer; the remote PostgreSQL, MySQL, Oracle or other database must be sized separately.
-
Leave room to grow
Keep the CloudBeaver workspace/server database persistent because it stores users, permissions, connection metadata and query history.
-
Run it on ZimaOS
Install CloudBeaver from ZimaOS, monitor JVM memory, active sessions and workspace growth, then raise Java heap or host RAM only when measured concurrency requires it.
Check every playback client
- Concurrent users
- Open database sessions
- JDBC drivers
- Java heap limit
- Query history volume
- Workspace backup
- Remote database latency
- Reverse proxy / HTTPS
Official minimum requirements
CloudBeaver Community does not publish one universal bare-metal minimum, but its current official Google Cloud Community guide provides a concrete deployment reference.
Treat 1 CPU / 4 GB RAM / 100 GB disk as official Community cloud guidance for optimal performance, not proof that every small single-user container requires 4 GB.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | At least 1 CPU | Current Community Google Cloud guidance for optimal performance. |
| RAM | At least 4 GB | Current Community Google Cloud guidance for optimal performance. |
| Disk | At least 100 GB | Current Community cloud-image deployment guidance. |
| Server type | Java application | CloudBeaver server is implemented in Java. |
| Java heap | Configurable with JVM options | Official docs show -Xmx2048M as a memory-limit example. |
| GPU | Not required | Database administration is CPU/RAM/network oriented. |
When to upgrade your hardware
Upgrade CloudBeaver when Java heap, user concurrency or the wider developer stack becomes constrained.
More simultaneous users and database sessions
Large query results or long query-history retention increase memory/storage
CloudBeaver shares the host with databases and developer tools
CloudBeaver stores query history and can handle large result sets; browser/server responsiveness can suffer when many heavy sessions overlap.
Data teams and analytics users.PostgreSQL, MariaDB, MongoDB, Jenkins or other services can dominate RAM and I/O even if CloudBeaver itself remains moderate.
All-in-one developer servers.Plan hardware growth with confidence
Scale CloudBeaver by controlling JVM memory and separating database workloads.
Set an explicit Java heap when needed
CloudBeaver supports normal JVM options such as -Xmx to cap or raise server heap deliberately.
Useful for predictable multi-container memory allocation.Keep databases on their own sizing plan
CloudBeaver is a management interface; the target database's buffer pool, cache and query execution do not belong to CloudBeaver's requirement.
Use separate database hardware guidance.Back up the workspace/server database
Users, permissions, query history and configuration are operational state and should survive container recreation.
Use persistent local storage and tested backups.Move to 16 GB when the developer stack grows
More CloudBeaver users plus databases, CI and other containers can justify whole-host memory well above the app's own needs.
ZimaBoard 2 1664 is the natural compact step-up.Can it run on ZimaOS?
CloudBeaver is currently available in the ZimaOS App Store under Developer.
Install CloudBeaver from ZimaOS
Use the packaged browser-based cloud database manager.
Open CloudBeaver in the ZimaOS App StoreUse Community deployment guidance
Current Community cloud documentation recommends at least 1 CPU and 4 GB RAM for optimal performance.
Read CloudBeaver Community deployment guidanceTune Java memory when concurrency grows
Official CloudBeaver docs expose normal JVM parameters and show explicit maximum-heap configuration.
Read CloudBeaver command-line parametersChoose Zima hardware for CloudBeaver
CloudBeaver fits comfortably on current ZimaBoard 2 hardware; larger tiers are mainly for multi-user or co-hosted developer/database stacks.
Is CloudBeaver a small shared database UI or part of a larger developer server?
Personal/small-team CloudBeaver
ZimaBoard 2 832 exceeds the current 4 GB Community guidance.
- Normal CloudBeaver hostZimaBoard 2 832
- More users/developer toolsZimaBoard 2 1664
CloudBeaver plus databases/storage/dev stack
Use ZimaCube when the surrounding databases, storage and backup workload drives the platform.
- Integrated developer/data serverZimaCube 2 Standard
No fixed user or query-count guarantee is implied. JDBC driver, result size, Java heap, target database, query history and co-hosted services all matter.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Personal and small-team CloudBeaver. | Java web server, multiple database connections and normal query history. |
|
Large co-hosted databases can consume far more RAM than CloudBeaver. | Get Now |
| ZimaBoard 2 1664 | CloudBeaver plus more developer/database services. | More JVM/session headroom and larger container stack. |
|
Database performance is still determined by the target database host/storage. | Get Now |
| ZimaCube 2 Standard | An integrated developer/data server with CloudBeaver. | CloudBeaver, local databases, backups and multi-drive storage. |
|
Choose it for the wider data/storage stack, not CloudBeaver alone. | 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
FAQ topics follow query fan-out around 4 GB RAM guidance, Java heap, PostgreSQL, users, query history and ZimaBoard deployment.
How much RAM does CloudBeaver need?
Current official Community Google Cloud guidance recommends at least 4 GB RAM for optimal performance. That is deployment guidance rather than a universal bare-minimum claim.
How many CPU cores does CloudBeaver need?
The current Community Google Cloud guide recommends at least 1 CPU for optimal performance. More cores mainly help when many users and queries overlap.
Is CloudBeaver a Java application?
Yes. The server is Java-based, and official docs support standard JVM memory controls such as -Xmx.
Does CloudBeaver need PostgreSQL?
CloudBeaver maintains its own server data and can use supported server-database configurations, but the external databases you administer are separate systems.
Can I limit CloudBeaver memory in Docker?
Yes. Use container memory limits together with appropriate JVM heap settings; official CloudBeaver docs show an -Xmx2048M example.
Can ZimaBoard 2 832 run CloudBeaver?
Yes. Its 8 GB RAM exceeds the current 4 GB Community cloud guidance and leaves headroom for normal small-team use.
Why is CloudBeaver slow when the server CPU is low?
Remote database latency, large result sets, JDBC behavior or the target database itself can dominate response time.
When should I move CloudBeaver to 16 GB RAM?
When many concurrent users, large result sets or co-hosted databases/developer tools create whole-host memory pressure.
What sources and further reading informed this CloudBeaver hardware guide?
CloudBeaver Community deployment guidance provides the 1 CPU/4 GB/100 GB cloud reference. Official server and command-line documentation defines the Java server, workspace data and heap controls, while ZimaOS confirms the Developer app.
