Node-RED
Flow-based programming tool from the Node.js Foundation lineage, wiring together APIs, services and physical hardware on anything down to a Raspberry Pi
Quick Overview
| Company | OpenJS Foundation (originated at IBM UK) |
|---|---|
| Category | Automation & Integration |
| Headquarters | Hursley, United Kingdom, Open Source |
| Founded | 2013 |
| EU Presence | Originated in the UK; vendor-neutral foundation project |
| Data Location | Wherever you run it |
| Open Source | Yes (Apache 2.0) |
| GDPR Compliant | Yes - no vendor processing |
| Self-Hosting | Yes - the only deployment model |
| Main Features | Visual flow editor, 4,000+ community nodes, MQTT and Modbus support, runs on Raspberry Pi, JavaScript function nodes, dashboard UI |
| Pricing | Free and open source |
| Best For | IoT, industrial automation, home automation and lightweight API glue |
| Replaces | Zapier, IFTTT, industrial SCADA glue |
Detailed Review
Node-RED came out of IBM's Hursley laboratory in the UK and is now an OpenJS Foundation project. It is a visual flow editor where you drag nodes onto a canvas and wire them together — but unlike the SaaS automation tools, it runs entirely on your own hardware and costs nothing.
Its centre of gravity is different too. Where Make connects SaaS applications, Node-RED is at its strongest connecting things: sensors, controllers, MQTT brokers, industrial equipment and local services.
Hardware and Protocols
MQTT, Modbus, serial, GPIO and a long list of industrial and consumer protocols are covered by community nodes. That is why Node-RED turns up embedded in industrial gateways, building management systems and a very large number of home automation setups.
It runs comfortably on a Raspberry Pi, which means the automation can sit physically next to the equipment it controls, with no dependency on an internet connection or a cloud service.
Four Thousand Community Nodes
The library covers databases, cloud services, messaging platforms, AI models and an enormous range of hardware. Quality varies, as it does in any community catalogue, but the breadth means most integration problems have an existing starting point.
The function node lets you drop into JavaScript whenever the visual approach becomes awkward, which keeps flows from becoming unmaintainable puzzles.
No Vendor at All
There is no company, no subscription and no account. For GDPR purposes you remain the sole controller and processor — there is no third party to assess, no data processing agreement to negotiate and nothing to migrate away from if a vendor changes direction.
Limitations to Consider
Node-RED has no built-in multi-user collaboration, versioning or approval workflow, so team use needs discipline and external Git integration. Community node quality is uneven and some are unmaintained. Its SaaS integrations are weaker and less polished than Make's or n8n's, and there is no vendor to call when something breaks in production.
Who Should Use Node-RED
IoT and industrial automation projects, building management, home automation and any situation where the automation needs to run locally on modest hardware without a cloud dependency or a subscription.
Pros and Cons
Pros
- Runs on a Raspberry Pi or industrial gateway
- Excellent hardware and protocol support
- 4,000+ community nodes
- Completely free, no vendor at all
- JavaScript function nodes for flexibility
Cons
- No built-in team collaboration or versioning
- Uneven community node quality
- Weaker SaaS integrations than Make or n8n
Alternatives to Node-RED
Other European automation & integration worth comparing before you decide:
n8n
Germany · Source-available workflow automation you can fully self-host
Make
Czech Republic · Visual scenario builder with more than 2,000 integrations
Kestra
France · Declarative orchestration for data and infrastructure workflows
Locoia
Germany · Integration and automation platform for mid-market operations
See all European automation & integration or compare them directly against Zapier on our alternatives page.
Frequently Asked Questions
Connecting hardware and local services: MQTT, Modbus, GPIO, serial devices and industrial equipment. It is the strongest option in this category for IoT and automation that must run locally.
For hardware and self-hosted use cases, comfortably. For SaaS-to-SaaS integration its connectors are less polished than Make's or n8n's, so those are usually the better fit.
No. Node-RED is Apache 2.0 licensed with no company, subscription or account behind it. You provide the hardware and that is the whole cost.
With discipline. It has no built-in multi-user editing, versioning or approvals, so teams typically add Git integration and agree conventions. For collaborative business automation, n8n is better structured.