Layer 5 · self-hosting reality check
What it actually takes to self-host Node-RED
The docs say 256 MB. In practice you want 1 GB for a real flow set. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from Zapier alternatives, where Node-RED is one of the picks.
Wondering whether you need to at all? Is Zapier free? — what the free tier actually allows, and where the wall is.
| RAM — documented minimum | 256 MB |
|---|---|
| RAM — what it really needs | 1 GB for a real flow set |
| CPU | 1 vCPU; it runs happily on a Raspberry Pi |
| Disk | 5 GB |
| Monthly cost | $6–12/mo, or free on hardware you already have |
| Setup time | 20 minutes |
| How you install it | npm install -g node-red, or the official Docker image |
| Ongoing maintenance | Low, but contributed nodes are the risk surface. |
| Where it stops scaling | Hundreds of flows on modest hardware. It is single-process; heavy CPU work blocks the event loop. |
The thing that catches people out
Node-RED has no built-in authentication. Out of the box the editor is open to anyone who can reach the port, and people expose it to the internet without noticing because it works perfectly on a LAN. Enable `adminAuth` in settings.js before it leaves your network — an unsecured Node-RED instance is remote code execution by design, since a flow can run arbitrary JavaScript.
When not to self-host Node-RED
You need approvals, versioning and audit trails on your automations. Node-RED is a live-editing environment, not a managed workflow platform.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 5 self-hosting guides
- Self-hosting LibreOffice2 GB with a large spreadsheet open
- Self-hosting ONLYOFFICE6 GB for the Document Server with a handful of concurrent editors
- Self-hosting Collabora Online4 GB, and roughly 1 GB per 20 concurrent documents
- Self-hosting CryptPad2 GB for a small instance
- Self-hosting Mattermost4 GB for a team of 50 with PostgreSQL on the same box
- Self-hosting Rocket.Chat6 GB with MongoDB on the same machine
Common questions
- How much RAM does Node-RED actually need?
- 1 GB for a real flow set in practice. The documented minimum is 256 MB, which is the figure at which the process starts rather than the figure at which it works under real use. 1 vCPU; it runs happily on a Raspberry Pi alongside it.
- What does self-hosting Node-RED cost per month?
- $6–12/mo, or free on hardware you already have This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for low, but contributed nodes are the risk surface.
- How long does it take to set up Node-RED?
- 20 minutes, via npm install -g node-red, or the official Docker image.
- When should I NOT self-host Node-RED?
- You need approvals, versioning and audit trails on your automations. Node-RED is a live-editing environment, not a managed workflow platform.
- What is the most common mistake when self-hosting Node-RED?
- Node-RED has no built-in authentication. Out of the box the editor is open to anyone who can reach the port, and people expose it to the internet without noticing because it works perfectly on a LAN. Enable `adminAuth` in settings.js before it leaves your network — an unsecured Node-RED instance is remote code execution by design, since a flow can run arbitrary JavaScript.