n8n vs Node-RED (2026): Which Flow Tool Fits Your Project

n8n vs Node-RED comes down to what the flow talks to: pick Node-RED when it sits next to devices and speaks MQTT, Modbus, TCP or serial, and pick n8n when it connects business apps, APIs and AI models. They overlap on HTTP, webhooks and MQTT, which is why plenty of setups run both: Node-RED at the edge, n8n behind it.

A documentation-based comparison, not a benchmark: nothing here was speed-tested. Versions, licences, node lists and prices were checked on 11 October 2026 against nodered.org and its docs on supported Node.js versions, security and context, the Node-RED 5.0.8 release and its source, the npm registry entries for the packages named below, FlowFuse pricing, the n8n pricing page, n8n's licence FAQ and docs, and the node list in the source of n8n 2.42.6.

Both tools draw a flow as boxes joined by wires, and that resemblance hides how different they are. Node-RED is a small always-on program that pushes messages between nodes as events arrive. n8n is a workflow engine that starts a run when a trigger fires, saves what happened, and bills or counts by the run. This page gives you a decision table by job, the head-to-head facts, a map from the Node-RED palette to n8n nodes, and the places where Node-RED still wins. It is part of our n8n hub.

n8n vs Node-RED: which one for which job?

Find the job in the first column. If your project spans two rows with different answers, read that as a sign you need both tools, not a compromise.

Node-RED vs n8n head to head

The rows that decide most projects are the unit of work, the protocols in core and the licence. Price rarely does: both can be run for the cost of a server.

A note on the version row. n8n's 3.0 breaking-changes page already describes 3.0 as released and says self-hosted n8n needs a Docker-based deployment, with npm installs no longer supported. On 11 October 2026 the newest stable release on GitHub, npm and Docker Hub was still 2.42.6, so that is the version compared here.

What Node-RED is built for

Node-RED calls itself "low-code programming for event-driven applications". It began as a side project at IBM in 2013, was open-sourced the same year, and is now an OpenJS Foundation project under Apache 2.0. Version 5.0.8 shipped on 8 October 2026; the 5.x line needs Node.js 22 or later and the project recommends Node 24.

A Node-RED flow is deployed once and then stays live. A message arrives from an MQTT topic, an HTTP endpoint or a timer, and passes from node to node as a msg object. There is no run to count and no quota to meter. That model suits device work, where readings arrive constantly and most of them need nothing more than a unit conversion and a threshold check.

• Protocols in the box. The 5.0.8 core palette has MQTT, HTTP, WebSocket, TCP and UDP nodes, next to function, switch, change, template, delay, trigger, filter and exec.
• Industrial and hardware packages. The Node-RED library, which nodered.org puts at over 5,000 nodes and flows, includes node-red-contrib-modbus (Modbus TCP, UDP and serial), node-red-contrib-opcua, node-red-contrib-s7 for Siemens PLCs, node-red-node-serialport and node-red-node-pi-gpio.
• Runs on small hardware. The Raspberry Pi guide installs it with one script on any Debian-based system and registers it as a service on port 1880. The same page notes that Node 24 has no 32-bit builds, so the oldest ARMv6 boards are out.
• Dashboards. FlowFuse Dashboard (the @flowfuse/node-red-dashboard package, Apache 2.0) adds forms, buttons, gauges and charts. The older node-red-dashboard package is marked as no longer maintained on npm.

Its limits are the other side of being small. The docs say plainly that the editor is not secured by default, which "is only suitable if you are running on a trusted network"; you add users and permissions in the settings file. Context data lives in memory and is cleared on restart unless you switch on file storage. Git-backed projects have to be enabled in settings. And because there is no run, there is no list of past runs to open: you watch a flow through the Debug sidebar and node status.

Price, checked October 2026: Node-RED itself is free. If you want it hosted and managed for a team or a fleet, FlowFuse lists three plans (Edge, Hub and Fleet), each with a "Contact Us" button instead of a price.

What n8n is built for

n8n is workflow automation for the business side. Every workflow begins with a trigger, each firing is one execution, and each execution is saved with the data every node received and returned. You can open a failed run, see which node broke and retry it, and point every workflow at an error workflow that alerts you.

• Apps with stored credentials. The core package for 2.42.6 registers 444 nodes and triggers, most of them business apps, plus 125 AI nodes. Logins and API keys are saved once as credentials and reused.
• AI built in. The AI Agent node takes a chat model, memory and tools as sub-nodes, and MCP client and server nodes connect it to outside tools.
• Some device reach. The MQTT Trigger and MQTT nodes cover the broker; AMQP, Kafka, RabbitMQ and Redis triggers cover queues; a Home Assistant node covers smart-home hubs. There is no core TCP, UDP, WebSocket, serial or Modbus node.
• Locked down by default. Since n8n 2.0 the Execute Command and Local File Trigger nodes are disabled unless you turn them on, per the 2.0 breaking changes. Good for a shared server, awkward for a box that is meant to run shell commands.

Price, checked October 2026: the self-hosted Community Edition has no licence fee and no execution cap. n8n Cloud Starter is €20 a month billed annually for 2,500 executions and Pro is €50 for 10,000; the trial gives 1,000 executions with no card. Our n8n pricing guide has every tier, and what self-hosted n8n really costs covers the server side.

Pick n8n if, pick Node-RED if

n8n vs Node-RED for IoT: use both, in this order

For IoT the honest answer is rarely one or the other. Node-RED belongs beside the devices and n8n belongs beside the people. The join is an MQTT broker or a webhook, and the rule is that Node-RED sends events, not readings.

On the n8n side, the MQTT Trigger takes a list of topics and has three options worth knowing: JSON Parse Body turns the payload into an object, Only Message drops the topic wrapper, and Parallel Processing is on by default. If you hand off by webhook instead, protect the URL; our n8n webhook guide covers header auth. For the wider picture, with Home Assistant, protocols and priced starter setups, see IoT automation in 2026.

Migration map: Node-RED palette to n8n nodes

If a Node-RED flow has drifted into business automation, calling CRMs and sending emails through HTTP nodes, it is a candidate for a move. This is the map. The left column is the Node-RED 5.0.8 core palette; the middle column uses the node names in n8n 2.42.6.

The mental shift is from one msg to a list of items. A Node-RED Function node receives a message and returns a message. An n8n Code node receives every item from the previous node and returns an array of items, each with its data under json. Most rewrites are a few lines:

// Node-RED Function node
msg.payload = { celsius: (msg.payload.f - 32) * 5 / 9 };
return msg;

// n8n Code node, mode: Run Once for All Items
return $input.all().map(item => ({
  json: { celsius: (item.json.f - 32) * 5 / 9 },
}));

Both snippets follow each project's documented pattern; they were checked against the docs and not executed for this article.

Where Node-RED still wins

A move to n8n is not an upgrade in every direction. These are the cases where staying put is the right call:

The licence item deserves a second look if you build for clients. Apache 2.0 places no limits on how Node-RED is used or resold. n8n's licence FAQ allows building and maintaining automations for clients on your own instance, and using n8n behind the scenes in your product, but not hosting it as a service where clients build workflows, white-labelling it, or letting end users configure workflows through your product.

Alternatives worth a look

• Home Assistant automations. For a home or a small shop, its own rules may cover the device side without Node-RED at all.
• Apache NiFi. When the job is moving large volumes of data between systems with back pressure and provenance, see n8n vs NiFi.
• Power Automate. If the business tools are Microsoft 365, read n8n vs Power Automate before choosing the n8n half of the pair.
• Other workflow tools. n8n alternatives compares twelve options, Node-RED included, on licence, hosting and price.

One more route opens up when the thing you are wiring together is something customers would log in to: a monitoring portal, an alert service, a small dashboard product. That is application work. Our AI SaaS Builder program has no Node-RED or n8n lessons; it covers the app itself, with Supabase for data, auth and realtime subscriptions, the Claude API for the AI feature, deployment on Vercel and Stripe billing.

n8n vs Node-RED: FAQ