Heavy JavaScript logic, parsing, image/data transformation or high message rates can shift Node-RED from an event router into a compute workload.
For large automation pipelines, data processing and custom JavaScript-heavy flows.متطلبات أجهزة Node-RED: ذاكرة الوصول العشوائي ووحدة المعالجة المركزية والتخزين والتدفّقات
تعرّف على متطلبات أجهزة Node-RED من حيث ذاكرة RAM ووحدة المعالجة المركزية والتخزين والتدفقات وNode.js وDocker وMQTT وأجهزة ZimaOS.
Node-RED hardware requirements at a glance
Node-RED is intentionally lightweight and runs well on low-cost edge hardware, but current upstream does not publish one universal CPU/RAM minimum. The most important current hard requirement is the Node.js runtime: Node-RED 5.x requires Node.js 22.9.0 or newer and recommends Node.js 24.
- CPU
- No universal official CPU minimum is published. Node-RED's event-driven runtime can run on modest hardware, while CPU demand grows with Function nodes, parsing/transformation, high message rates, image/data processing and additional local services.
- RAM
- No universal current upstream RAM minimum is published. Older community guidance suggested about 512 MiB for general use, while current ZimaOS Node-RED 4.1.2 reserves only 64 MB. Neither number is a universal current Node-RED 5.x whole-system minimum.
- Node.js
- Current Node-RED 5.x requires Node.js 22.9.0 or newer and recommends Node.js 24. Current Node-RED documentation also notes that older 32-bit ARM platforms are no longer supported by Node-RED 5 because the required modern Node.js builds are unavailable.
- Storage
- Node-RED persistent data includes flows, credentials, settings, installed nodes and project files. Docker deployments should persist /data. Storage demand grows with npm packages, project repositories, logs and any local databases/files used by flows.
- GPU
- Node-RED itself does not require a GPU. A GPU becomes relevant only when a flow calls a same-machine workload such as local AI, computer vision or other accelerator-dependent software.
- Best Zima starting point
- ZimaBoard 2 832 is already far beyond the needs of ordinary home-automation and API flows. Choose 1664 when Node-RED shares the host with databases, Home Assistant, MQTT, Grafana or more services; choose ZimaCube 2 when storage and the broader home-server stack become the real requirement.
From official requirements to the right setup
Node-RED sizing starts with the runtime version, then checks flow complexity, message rate, installed nodes, local databases/services, persistent storage and the rest of the ZimaOS host.
-
Official requirements
Start with version compatibility. Current Node-RED 5.x requires Node.js 22.9.0+ and recommends Node.js 24. The current ZimaOS package is still Node-RED 4.1.2, so do not automatically apply every Node-RED 5 platform constraint to the packaged 4.x container.
-
Confirm your needs
Classify the flows. Simple MQTT/webhook/routing flows are light; large JavaScript Function nodes, image/data processing, high-frequency messages and many community nodes can increase CPU and heap use.
-
Leave room to grow
Persist /data and plan storage for flows, credentials, settings, installed nodes and projects. Databases such as InfluxDB/MySQL and MQTT brokers are separate services and need their own resources.
-
Run it on ZimaOS
Test the real automation workload while monitoring Node.js heap, total container RAM, CPU, event-loop responsiveness and storage I/O. Upgrade only after identifying Node-RED or a co-hosted dependency as the actual bottleneck.
Check every playback client
- Node-RED major version and compatible Node.js version
- Number and complexity of active flows
- Message/event frequency and payload size
- Function nodes and CPU-heavy data transformations
- Community nodes and npm package footprint
- Persistent /data storage and project backups
- MQTT, InfluxDB, Home Assistant and other co-hosted services
- Other ZimaOS containers sharing CPU and RAM
Official minimum requirements
Current Node-RED documentation does not publish a universal CPU/RAM/disk minimum. It does publish current Node.js compatibility and continues to position Node-RED as suitable for edge hardware such as Raspberry Pi.
Do not promote the 2020 forum's 512 MiB suggestion or the current ZimaOS 64 MB reservation into a universal requirement. For current upstream Node-RED 5.x, version/platform compatibility is the firmer hard boundary; practical memory depends on flows and co-hosted services.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Current Node-RED | 5.x | Node-RED 5.0 was released in June 2026. |
| Minimum Node.js for 5.x | Node.js 22.9.0+ | Current official hard software/runtime requirement. |
| Recommended Node.js | Node.js 24 | Current official recommendation and the basis for current Node-RED Docker images. |
| CPU minimum | No universal official minimum published | The project remains oriented toward low-cost edge hardware, but workload complexity determines actual CPU use. |
| RAM minimum | No universal official current minimum published | Historical/community and package reservation numbers should not be converted into a Node-RED 5 minimum. |
| Current ZimaOS package | Node-RED 4.1.2, 64 MB memory reservation | Current ZimaOS manifest supports amd64, arm64, s390x and arm and persists /data. The 64 MB value is a reservation, not a hard limit. |
When to upgrade your hardware
Node-RED upgrades are driven by actual flow execution, Node.js heap pressure and the services it orchestrates.
Large Function nodes or data transformations keep CPU busy
Heap pressure or restarts appear as flows and nodes grow
Co-hosted MQTT, databases and dashboards dominate the server
Older community tuning references use Node.js heap caps such as 128–512 MB on Raspberry Pi-class devices. Modern larger flows may need more, but the right threshold should be measured from actual heap use rather than copied from an old Pi setup.
For large palettes, many flow tabs and data-heavy messages.A common Node-RED home stack also runs Mosquitto, InfluxDB/MySQL, Grafana or Home Assistant. Those services can consume more resources than Node-RED itself.
For consolidated home-automation and IoT servers.Plan hardware growth with confidence
Node-RED grows best when the flow runtime, persistent data and external services are treated as separate resource layers.
Keep /data on persistent SSD-backed storage
Docker Node-RED stores flows, credentials, settings and installed nodes under /data. Persistent local storage makes upgrades and recovery safer.
Use SATA/NVMe SSD for important Node-RED AppData.Move time-series and SQL data out of Node-RED
Node-RED should orchestrate data flows rather than become a substitute for InfluxDB, PostgreSQL or another dedicated database.
Size the database separately and add RAM/SSD only when that service requires it.Keep compute-heavy AI/vision services separate
A Node-RED flow can call Ollama or vision software without making those model requirements part of Node-RED itself.
Use a separate GPU/model backend when local AI exceeds the automation host's resources.Upgrade RAM for the whole automation stack
Move from 8 GB to 16 GB when Home Assistant, databases, dashboards and many containers—not Node-RED alone—create sustained memory pressure.
Choose ZimaBoard 2 1664 or ZimaCube 2 Pro only when total workload justifies it.Can it run on ZimaOS?
Node-RED is currently available in the ZimaOS App Store under Developer. The current package is 4.1.2 and uses persistent /data storage.
Install the current ZimaOS Node-RED package
The current manifest uses nodered/node-red:4.1.2, network_mode host, WebUI port 1880 and a persistent /data bind mount.
Open Node-RED in the ZimaOS App StoreTreat 64 MB as a reservation, not a minimum or cap
The current manifest places memory: 64M under resource reservations and does not set a matching hard limit. Actual usage can exceed 64 MB.
Review the ZimaOS Node-RED manifestKeep package version separate from current upstream 5.x
Current upstream Node-RED 5.x requires Node.js 22.9+ and recommends Node.js 24, while the current ZimaOS image is still 4.1.2. Validate package updates before applying new upstream platform assumptions.
Read current Node-RED version requirementsChoose Zima hardware for your Node-RED workload
Node-RED itself is light enough that ZimaBoard 2 832 is the default choice. More hardware should follow databases, dashboards, large automation pipelines and other applications rather than the editor/runtime alone.
Is Node-RED mainly handling home automation and APIs, or part of a larger data/monitoring/application stack?
Normal home automation, MQTT, webhooks and APIs
Start with ZimaBoard 2 832. Its N150 and 8 GB RAM provide substantial headroom over ordinary Node-RED use. Choose 1664 when databases and many other services share the same host.
- Node-RED and light automation stackZimaBoard 2 832
- Larger automation/database stackZimaBoard 2 1664
Heavy data pipelines, broad homelab or storage workloads
Choose ZimaCube 2 from the complete workload. Standard is storage-first; Pro adds CPU/RAM/network headroom. Creator Pack only makes sense when a separate GPU workload is present.
- Storage-first automation/NASZimaCube 2 Standard
- Heavier all-in-one automation/data stackZimaCube 2 Pro
- Only for independent GPU/AI workloadsZimaCube 2 Creator Pack
This is a workload guide, not a fixed flow-count or messages-per-second benchmark. Node types, JavaScript logic, payload size, event rate and external services can change resource use substantially.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | The default Zima choice for Node-RED home automation, MQTT, webhooks and API workflows. | Node-RED, MQTT, lightweight dashboards, reverse proxy and several ordinary automation services. |
|
Use added SSD for a serious persistent automation stack; large databases or AI services should be sized separately. | Get Now |
| ZimaBoard 2 1664 | Node-RED plus a denser database/automation/home-server stack. | Node-RED, Home Assistant, databases, MQTT, Grafana and more always-on containers. |
|
Do not claim Node-RED requires 16 GB. | Get Now |
| ZimaCube 2 Standard | Storage-first automation/NAS systems where Node-RED orchestrates files and broader services. | Node-RED plus storage, backups and moderate NAS applications. |
|
Choose for storage, not because Node-RED needs a Core i3. | Get Now |
| ZimaCube 2 Pro | Heavier all-in-one automation/data/home-lab stacks. | Node-RED plus databases, monitoring, many containers, storage and higher-throughput local services. |
|
Pro is unnecessary for normal Node-RED alone. | Get Now |
| ZimaCube 2 Creator Pack | Node-RED on hardware already required for separate local AI/GPU workflows. | Node-RED orchestrating independent GPU/AI or creator services. |
|
Extreme overkill for Node-RED 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
The supplied Node-RED sources span 2020–2026 and therefore describe several different Node-RED/Node.js generations. Current upstream version compatibility takes precedence.
How much RAM does Node-RED need?
Current upstream does not publish one universal RAM minimum. A 2020 forum answer suggested 512 MiB as a general minimum and said 256 MiB may work for small setups, but that was community guidance for a much older Node-RED generation.
Is 64 MB RAM enough for Node-RED on ZimaOS?
The current ZimaOS manifest reserves 64 MB but does not set a 64 MB hard limit. It should not be presented as the maximum or universal minimum; actual memory depends on flows and installed nodes.
What Node.js version does Node-RED need now?
Current Node-RED 5.x requires Node.js 22.9.0 or newer and recommends Node.js 24. Localtonet's March 2026 article says Node.js 18+, which was appropriate to Node-RED 4.x-era guidance but is stale for current Node-RED 5.
Can Node-RED run on Raspberry Pi?
Yes on suitable current Raspberry Pi hardware and 64-bit OS. Node-RED 5 no longer supports older 32-bit ARM platforms such as Pi 3B-or-earlier class devices that cannot run the required modern Node.js 64-bit stack.
What does the 2020 minimum-configuration forum post tell us?
It suggested Pi Zero/first-gen Pi-class CPU, about 512 MiB RAM and a few GiB storage, with 256 MiB potentially workable. This is useful historical community evidence but not a current official requirement.
What does SunFounder's 2025 tutorial require?
Its Raspberry Pi tutorial specifies Pi 3 or newer and an SD card with at least 8 GB. These are tutorial hardware choices, not universal Node-RED Server minimums, and the Pi 3 compatibility statement predates Node-RED 5's modern Node.js requirement.
Does Node-RED need an SSD?
Not as a universal requirement, but SSD is a better long-term choice for persistent /data, Projects and co-hosted databases. The 2024 hardware-suggestion thread also favors SSD/NVMe for a modern Pi-based multi-service setup.
Can ZimaBoard 2 832 run Node-RED?
Yes. Four N150 cores and 8 GB RAM are far beyond ordinary Node-RED home-automation needs. Add SSD storage as installed nodes, projects and co-hosted services grow.
What sources and further reading informed this Node-RED hardware guide?
The supplied 2024 Node-RED hardware-suggestion thread discusses modern Raspberry Pi 4/5 systems, SSD/NVMe and combined Node-RED/MySQL/Pi-hole/Mosquitto workloads, so it is useful as real-world stack context rather than a minimum specification. Localtonet's March 2026 self-hosting guide describes Node-RED as lightweight and discusses Raspberry Pi heap settings, but its Node.js 18+ statement is stale for Node-RED 5.x. The supplied 2020 minimum-configuration thread proposes Pi Zero/first-gen-Pi class CPU, 512 MiB RAM and a few GiB storage as community guidance, not official requirements. SunFounder's May 2025 tutorial uses Pi 3+ and an 8-GB SD card for its Raspberry Pi deployment, but this predates Node-RED 5's current platform constraints. Current upstream Node-RED 5 release/version documentation and the current ZimaOS manifest were checked separately and used as the authority for Node.js compatibility, package version, architecture and memory reservation.
