完全なヘルプ ハードウェア要件：RAM、CPU、ストレージ＆ヘルプデスク＆ナレッジベース
RAM、CPU、ヘルプデスクの会話、メールボックス、ナレッジベースのコンテンツ、ストレージ向けに、ハードウェアを完全に計画し、実用的なZimaOS導入の推奨事項をまとめます。
Full Help hardware requirements at a glance
Size Full Help from verified upstream requirements first, then add headroom for workload and persistent data.
- RAM
- No numerical official minimum published in accessible official docs
- CPU
- No numerical official minimum published
- Storage
- No numerical official disk minimum published
- Application stack
- Official API docs expose a Laravel 5.7 Passport-powered authentication layer
- Mail integration
- Mailboxes support forwarding, IMAP, or POP3 inbound connections
- Best Zima starting point
- ZimaBoard 2 832 for a small helpdesk
From official requirements to the right setup
Start with current upstream facts for Full Help, 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
- Agent count
- Conversation volume
- Mailbox count
- IMAP/POP3 polling
- Knowledge-base traffic
- Attachments
- Database/app backups
- Current vendor runtime requirements
Official minimum requirements
The accessible official Full Help public documentation does not publish a numerical whole-host CPU, RAM, or disk minimum.
Third-party catalogs estimate low resource usage, but the SOP requires official evidence for official_minimum. Those estimates are therefore excluded from the minimum claims.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical minimum published | Helpdesk workload dependent. | |
| No numerical minimum published | No official current host-RAM figure found. | |
| No numerical minimum published | Attachments/history determine growth. | |
| Laravel 5.7 Passport | Confirms application framework component, not a host minimum. | |
| Forwarding, IMAP, or POP3 inbound options | Mail integrations affect background workload. | |
| Path, subdomain, or custom-domain sites | Public help-center traffic varies. | |
| Not required | No GPU workload is documented. |
When to upgrade your hardware
Conversation/mail growth
Attachment growth
Runtime uncertainty
Plan hardware growth with confidence
SSD app/database state
Keep application and database state on SSD.
SSDMore RAM
Useful for more agents and mailbox processing.
ZimaBoard 2 1664Attachment capacity
Expand storage for support files and KB assets.
ZimaCube storageBackup capacity
Protect database/config/assets with tested backups.
External backupCan it run on ZimaOS?
Custom install Full Help in ZimaOS
No specific public ZimaOS Full Help per-app page was verified, so use Custom Install.
Custom install Full Help in the ZimaOS app ↗Verify the current licensed installer requirements
The public developer docs do not expose a current complete runtime/system-requirements page.
Open Full Help developer docs ↗Do not treat third-party resource estimates as official
Keep unofficial 512 MB/1 GB estimates out of official_minimum.
Open Full Help public docs ↗Zima hardware for Full Help
Full Help should be sized by actual helpdesk usage and the runtime shipped with the licensed/current release.
Choose by workload
ZimaBoard 2 832 is a practical provisional starting point, pending verification of the current licensed runtime requirements.
Scale CPU/RAM and storage based on measured helpdesk workload.
Because official public system requirements are incomplete, the JSON intentionally avoids inventing CPU/RAM minima.
| 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 workloads |
|
8 GB RAM can limit larger CRM, mail, database, or platform stacks | Get Now |
| 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 Standard | Storage-heavy file, mail, attachment, and archive workloads | Large persistent data sets |
|
8 GB RAM is less suitable for memory-heavy multi-service 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 Full Help publish an official RAM minimum?
No numerical whole-host RAM minimum was found in the accessible official public documentation.
Does Full Help publish an official CPU minimum?
No numerical whole-host CPU minimum was found in the accessible official public documentation.
What does the official API documentation confirm?
It documents Full Help's helpdesk API, OAuth authentication using Laravel Passport, mailboxes, accounts, and knowledge-base sites.
How can Full Help receive email?
Official mailbox docs describe forwarding, IMAP, and POP3 inbound connection modes.
Can I use third-party 512 MB or 1 GB estimates as the official minimum?
No. They are not vendor-published system requirements.
Can ZimaBoard 2 832 run a small Full Help instance?
It is a reasonable provisional starting point, but verify the current licensed installer/runtime requirements before production.
Does Full Help need a GPU?
No GPU requirement is documented.
What should drive upgrades?
Agent count, conversation volume, mail processing, attachments, knowledge-base traffic, and database growth.
