Home Assistant, cameras, media and databases can consume the resources grocy itself does not need.
All-in-one home servers.grocy hårdvarukrav: RAM, CPU och lagring
Planera grocy-hårdvara för RAM, CPU, SQLite-data, säkerhetskopior och Docker-distribution, med praktiska rekommendationer för anpassad ZimaOS-installation i hemmet.
grocy requirements at a glance
grocy is designed for household inventory, shopping and chores, so the core workload is light. Upstream does not publish a numerical CPU/RAM/disk minimum.
- RAM
- No numerical official minimum published. Practical memory use is small compared with media, AI or large database services.
- CPU
- No numerical official core minimum published. Normal household transactions and UI usage are lightweight.
- Storage
- No universal official minimum. Persistent SQLite/app data and backups determine capacity.
- Database
- grocy uses SQLite for its normal application data, keeping the self-hosted stack simple.
- Docker
- Current project guidance points Docker users to maintained container options; the old grocy/grocy-docker project is archived.
- Best Zima starting point
- ZimaBoard 2 832 is vastly more than enough for grocy and leaves substantial headroom for Home Assistant and other home services.
From official requirements to the right setup
Treat grocy as a lightweight home app and size the host for the wider household automation stack.
-
Official requirements
Start with current grocy setup guidance. Upstream does not publish numerical CPU/RAM minimums.
-
Confirm your needs
Persist the grocy data directory because SQLite/application data is the important state.
-
Leave room to grow
Use a maintained container image such as LinuxServer's current grocy image rather than the archived grocy/grocy-docker repository.
-
Run it on ZimaOS
On ZimaOS, use Install Custom App, map the web port, persist configuration/data, and choose hardware for the other services sharing the host.
Check every playback client
- Household users
- Item/recipe count
- Barcode integrations
- Persistent data path
- Backup retention
- Reverse proxy/HTTPS
- Home Assistant integration
- Other ZimaOS services
Official minimum requirements
grocy's current documentation provides deployment options but no numerical hardware sizing table.
Do not invent a 256 MB or 512 MB official minimum. grocy is light, and ZimaBoard 2 has ample whole-host headroom for it.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM minimum | No numerical official minimum published | Upstream setup docs do not define host RAM. |
| CPU minimum | No numerical official minimum published | Normal household workload is light. |
| Storage minimum | No numerical official minimum published | Data and backups determine capacity. |
| Database | SQLite | Core application uses a local SQLite database. |
| Container guidance | Use a maintained container image | Current grocy repository points Docker users to LinuxServer. |
| Old grocy-docker repo | Archived/retired | Do not base a new deployment on it. |
When to upgrade your hardware
grocy rarely needs a hardware upgrade by itself.
The host adds many other home services
Backup or storage policy expands
Automation integrations grow
Long retention or broader household file storage may justify more capacity.
NAS-centric deployments.Companion services and integrations may add more load than grocy itself.
Highly automated homes.Plan hardware growth with confidence
Scale the wider home-server stack, not grocy alone.
Keep grocy on the smallest Zima host
Its core SQLite-backed household workload is modest.
ZimaBoard 2 832 is already ample.Persist grocy data on reliable storage
Protect the database/configuration rather than chasing extra CPU.
Any durable Zima SATA/NVMe storage is sufficient.Use 16 GB for many companion apps
Extra memory benefits Home Assistant, databases and other services.
ZimaBoard 2 1664.Use ZimaCube for broader NAS duties
Choose a larger chassis for backups/media/storage, not because grocy itself requires it.
ZimaCube 2 Standard.Can it run on ZimaOS?
grocy is not currently confirmed as a public official one-click ZimaOS App Store page in the sources checked for this guide. It can be deployed through Install Custom App with a maintained grocy container image.
Custom install grocy in ZimaOS
Use Install Custom App with a maintained grocy container such as LinuxServer's, persist the configuration/data directory and expose the web port.
Custom install grocy in the ZimaOS app ↗Follow current grocy setup guidance
The project documents Docker/Podman, Home Assistant and PHP-web-server installation paths.
Review grocy setup ↗Avoid the archived grocy-docker repository
That repository is retired and explicitly points users to the LinuxServer container instead.
Review archived grocy-docker notice ↗Choose Zima hardware for grocy
grocy is so light that hardware choice should be driven by the rest of the home-server workload.
Is grocy mostly standalone, or part of a larger home-automation/NAS stack?
grocy plus lightweight utilities
Use ZimaBoard 2 832; grocy uses only a small fraction of the host.
- Best starting pointZimaBoard 2 832
grocy plus many home services
Choose more RAM/storage for the wider stack.
- More app headroomZimaBoard 2 1664
- Broader storage platformZimaCube 2 Standard
These recommendations apply to grocy itself; companion services can have very different requirements.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | grocy and lightweight household apps. | grocy, SQLite, reverse proxy and small companion services. |
|
The host is far larger than grocy needs; size for other apps. | Get Now |
| ZimaBoard 2 1664 | grocy plus a broader home-automation stack. | grocy alongside Home Assistant, databases and more containers. |
|
Extra RAM is for companion services. | Get Now |
| ZimaCube 2 Standard | grocy on a broader NAS/home server. | Household apps plus multi-drive backups, media and storage. |
|
Choose it for the broader NAS workload, not grocy. | 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
These answers cover grocy RAM, CPU, SQLite, Docker and ZimaOS deployment.
How much RAM does grocy need?
grocy does not publish a numerical official server RAM minimum.
How many CPU cores does grocy need?
No numerical official minimum is published; normal household use is lightweight.
Which database does grocy use?
grocy uses SQLite for its application data.
How much storage does grocy need?
No universal minimum; persistent data and backups determine capacity.
Does grocy need a GPU?
No dedicated GPU is required.
Can ZimaBoard 2 run grocy?
Yes, easily. The 8 GB model is vastly above grocy's practical needs.
Which Docker image should I use for grocy?
Current project guidance points users to maintained images such as LinuxServer's; the old grocy-docker repository is archived.
When should I use larger Zima hardware?
When other home-automation, media or storage services—not grocy itself—need it.
What sources informed this grocy hardware guide?
Current grocy setup and repository guidance plus current Zima product pages.
