EKSO-Hardwareanforderungen: RAM, CPU, Speicher und PostgreSQL-Arbeitsverwaltung
EKSO-Hardware für RAM, CPU, PostgreSQL/pgvector, Worker und Helpdesk-Workloads planen sowie praktische Empfehlungen für die Bereitstellung von ZimaOS.
EKSO hardware requirements at a glance
Size EKSO 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
- Application/database data, attachments, logs, and backups
- Database
- PostgreSQL + pgvector in bundled stack; PostgreSQL or SQL Server for BYOD
- Deployment
- Docker Compose; app + worker + database stack
- Best Zima starting point
- ZimaBoard 2 1664
From official requirements to the right setup
Start with current upstream facts for EKSO, 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
- User count
- Projects/tickets
- PostgreSQL size
- pgvector use
- Attachments
- Worker activity
- Report volume
- Backup retention
Official minimum requirements
EKSO documents its Docker topology and supported database engines but does not publish a numerical whole-host CPU, RAM, or disk minimum.
Do not invent a minimum from the PostgreSQL container or trial license. Size the app, worker, database, vector workload, attachments, and concurrent users together.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical minimum published | Workload dependent. | |
| No numerical minimum published | App + worker + DB determine memory. | |
| app + worker + PostgreSQL/pgvector | Bundled quick-start stack. | |
| PostgreSQL or SQL Server | Both supported. | |
| 6050 | Startup URL in current instructions. | |
| Linux x64 native binary planned; Docker available now | Current fastest path is Docker stack. | |
| Not required | No baseline GPU requirement. |
When to upgrade your hardware
User/report growth
Database/vector growth
Attachment growth
Plan hardware growth with confidence
SSD database
Keep PostgreSQL/SQL Server on SSD/NVMe.
SSD/NVMeMore RAM
Useful for DB cache and workers.
ZimaBoard 2 1664 or higherAttachment capacity
Expand storage for files/backups.
ZimaCube storageStronger CPU
Useful for larger teams/reporting.
ZimaCube 2 ProCan it run on ZimaOS?
Custom install EKSO in ZimaOS
No specific public ZimaOS EKSO per-app page was verified, so use Custom Install.
Custom install EKSO in the ZimaOS app ↗Use EKSO's Docker stack
Official quick start runs app, worker, and Postgres with pgvector.
Open EKSO get-started docs ↗Choose bundled DB or BYOD deliberately
BYOD supports PostgreSQL or SQL Server and requires pgvector when PostgreSQL is used.
Open EKSO deployment instructions ↗Zima hardware for EKSO
EKSO is a stateful multi-service work-management stack; database and worker load matter more than the web UI itself.
Choose by workload
Start with 16 GB-class RAM for comfortable app+worker+DB headroom.
Use stronger CPU and storage throughput.
Zima sizing is workload-based because EKSO does not publish a whole-host minimum.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 1664 | Memory-heavier self-hosted services | Moderate multi-container and database workloads |
|
CPU remains the 4-core N150, so heavy build/search/CRM workloads can still be CPU-limited | Get Now |
| ZimaCube 2 Pro | CPU-heavier, database-heavy, and higher-concurrency services | Larger CRM/helpdesk/mail/platform workloads |
|
16 GB RAM can still be low for large enterprise stacks | 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 EKSO publish a RAM minimum?
No numerical whole-host RAM minimum is published.
Which database does the bundled stack use?
PostgreSQL with pgvector.
Can EKSO use SQL Server?
Yes, in the bring-your-own-database setup.
How is EKSO deployed today?
Docker Compose is the current fastest path.
What port does the current quick start use?
6050.
Can ZimaBoard 2 1664 run EKSO?
It is a practical small-team starting point.
Does EKSO need a GPU?
No baseline GPU requirement is published.
When should I choose ZimaCube 2 Pro?
For larger teams, heavier workers/reports, and bigger databases.
