gateway-go Hardware Requirements: RAM, CPU, Storage & Network Throughput
Plan gateway-go hardware for RAM, CPU, host networking, remote-access traffic, Docker, and practical ZimaOS deployment recommendations.
gateway-go hardware requirements at a glance
Size gateway-go from verified upstream requirements first, then add headroom for the real workload and persistent data.
- RAM
- No numerical official minimum published
- CPU
- No numerical official minimum published
- Storage
- Small app footprint plus configuration and logs
- Networking
- Upstream Docker example uses host networking
- Deployment
- Prebuilt binaries and openiothub/gateway-go Docker image
- Best Zima starting point
- ZimaBoard 2 832
From official requirements to the right setup
Treat gateway-go as a network gateway: size simultaneous remote sessions, uplink throughput, encryption/proxy work, and host-networking constraints.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Remote users
- Concurrent connections
- Internet uplink
- Host-network mode
- QR/client enrollment
- Log retention
- Co-located apps
- Firewall/NAT rules
Official minimum requirements
Upstream documents deployment and configuration but no numerical whole-host CPU, RAM, or disk minimum.
Do not treat the ZimaOS App Store memory label as an upstream official minimum. Size from connection volume and the rest of the host workload.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Proxy and encryption work scale with traffic. | |
| No numerical official minimum published | Depends on concurrency and other containers. | |
| openiothub/gateway-go:latest | Upstream container path. | |
| Host networking | Documented example uses --net=host. | |
| /etc/gateway-go/gateway-go.yaml | Persist configuration. | |
| Not required | No GPU workload documented. |
When to upgrade your hardware
Remote-session growth
Network saturation
Host consolidation
Plan hardware growth with confidence
Persistent config
Keep gateway configuration and logs on reliable storage.
SSD or persistent host volumeMemory headroom
Add RAM when the wider host runs more services.
Higher-RAM hostFaster network
Improve Ethernet and WAN throughput when saturation appears.
2.5GbE or faster LAN plus adequate uplinkStronger CPU
Useful for sustained encrypted proxy traffic.
Higher-throughput CPUCan it run on ZimaOS?
Install gateway-go from the ZimaOS App Store
A specific public App Store page is verified.
Open gateway-go in the ZimaOS App Store ↗Use the upstream OpenIoTHub project
The ZimaOS listing aligns with OpenIoTHub gateway-go.
Open gateway-go source ↗Preserve host-network behavior
Verify interactions with other host services.
Review gateway-go Docker deployment ↗Zima hardware for gateway-go
gateway-go itself is light; network quality and the rest of the host workload usually matter more than application RAM.
Choose by workload
Use a low-power host and focus on stable networking.
Scale CPU and network when proxy throughput or co-located services become the constraint.
Zima product guidance is a practical workload mapping, not an upstream hardware certification.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services and small persistent workloads | Single-app or small multi-app home-server deployments |
|
8 GB RAM and a 4-core N150 limit heavier CI, databases, and high-concurrency work | Get Now |
| ZimaBoard 2 1664 | More containers and memory-heavier services on a low-power CPU | Moderate multi-app workloads |
|
CPU throughput is unchanged from the 832 model | Get Now |
| ZimaCube 2 Pro | CPU-heavy, higher-concurrency, and database-heavy workloads | Builds, indexing, many connections, or demanding containers |
|
16 GB RAM can still limit very large builds, databases, or local AI | 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 gateway-go need?
Upstream does not publish a numerical whole-host RAM minimum.
How many CPU cores does gateway-go need?
No numerical official CPU minimum is published; proxy traffic and encryption drive compute use.
Does gateway-go need much storage?
No. Plan for application files, configuration, and logs.
Does gateway-go use Docker?
Yes. Upstream documents the openiothub/gateway-go image.
Why does the Docker example use host networking?
The documented example uses host networking so the gateway can interact directly with local services.
Can ZimaBoard 2 832 run gateway-go?
Yes as a practical small-gateway starting point.
Does gateway-go need a GPU?
No GPU requirement is documented.
When should I move to ZimaCube 2 Pro?
Only when higher concurrency, CPU needs, or broader consolidation justify it.
![Unifi-controller [legacy]](http://shop.zimaspace.com/cdn/shop/files/Unifi-controller_legacy.webp?v=1790688426&width=1000)
