Node-RED

This Node-RED review covers what the tool is used for, its key features, what Node-RED costs, how FlowFuse fits in, where it shines and falls short, and how it compares with other automation tools. Node-RED is low-code programming for event-driven applications: you drag nodes onto a canvas in the browser-based Node-RED editor and wire them together into flows that collect, transform and visualize data. Nick O'Leary and Dave Conway-Jones built it at IBM Emerging Technology in 2013 for wiring together hardware devices, APIs and online services for the Internet of Things. IBM open-sourced it and contributed the Node-RED project to the JS Foundation in 2016, and it is maintained today under the OpenJS Foundation (Wikipedia).

What is Node-RED used for?

Node-RED is used wherever events from one system need to trigger actions in another. Common use cases:

• Home automation: many Home Assistant users run Node-RED as an add-on to build automations that are easier to follow as a visual flow than as YAML.
• Industrial IoT: reading PLC and sensor data over protocols such as MQTT, Modbus and OPC UA, then sending it to dashboards, databases or the cloud.
• Integrating APIs and online services: HTTP endpoints, webhooks and small REST APIs built as flows.
• Prototyping and data pipelines: collect data from several data sources, transform it with function nodes and store or visualize it.

Companies in industries such as manufacturing, energy and logistics run Node-RED applications in production, and hobbyists run it on a Raspberry Pi at home.

Key features

• Browser-based flow editor: drag and drop nodes, wire them together, and deploy with one click.
• 5,000+ community nodes and flows: the Node-RED community library covers databases, cloud services, hardware and protocols (nodered.org).
• Function nodes and subflows: write JavaScript functions when a built-in node is not enough, and package repeated logic as subflows, so you are never stuck at the edge of low code.
• Runs anywhere: on your own machine, in Docker, on a Raspberry Pi or other hardware devices, or in the cloud on FlowFuse, AWS or Azure.
• Event-driven runtime: built on Node.js, so it handles many small events with little overhead.
• Flows as JSON: export, import and share flows, and keep them in version control.

Node-RED pricing

Node-RED itself is free. It is open source under the Apache License 2.0, with no paid tier, seat limits or usage fees (Wikipedia). Your costs are the hardware or server it runs on and the time to install, secure and maintain it.

The paid option is FlowFuse, a platform for running Node-RED at scale. The difference is simple: Node-RED is the open-source runtime and editor, FlowFuse adds hosting, team management and support around it. FlowFuse's co-founder and CTO is Nick O'Leary, the co-creator of Node-RED, and the company invests in the open-source project. FlowFuse sells Edge, Hub and Fleet products for teams that need multi-user access, device fleet management, DevOps pipelines and support. Its pricing page lists no public prices as of September 2026: you contact sales, and there is a free trial. FlowFuse can also be self-hosted with Docker or Kubernetes.

The cost surprise to check is operations. Free software still needs someone to patch it, secure the editor with a login, back up flows and monitor the instances. For a few flows at home that is small. For dozens of instances across sites it is real work, which is the gap FlowFuse sells into.

Getting started with Node-RED: install, port and security

To start, install Node.js and run npm install -g --unsafe-perm node-red, or use the official Docker image, then open the editor in a browser on port 1880. The official Node-RED website has install guides for Raspberry Pi, Docker and the main cloud platforms, and IBM still publishes Node-RED tutorials and sample projects on IBM Developer (IBM). The editor has no login by default, so the first security step on any shared network is to enable adminAuth with a username and password, and to put the editor behind HTTPS. The Node-RED community forum and the flow library are the places to look for an answer when a flow goes wrong.

Node-RED dashboards

The original node-red-dashboard was formally deprecated on 27 June 2024 because it was built on the retired AngularJS framework; it can still be installed, but it gets no new development (FlowFuse). Its successor is Dashboard 2.0, the open-source @flowfuse/node-red-dashboard package, with responsive layouts, new widgets and multi-user support. For a new project, start with Dashboard 2.0.

Is Node-RED still used? Development, community and beginners

Node-RED is actively maintained: version 5.0.7 was released on 8 September 2026, development happens in the open on GitHub, and the Node-RED community forum answers most questions. It is good for beginners who want to automate things without writing a full program, because each step is a visible node. The learning curve comes later, when flows grow large and you need JavaScript, error handling and a clean structure. Small, well-named flows and subflows keep it manageable.

Where Node-RED shines — and where it falls short

Strengths:

• Free and open source, with no vendor lock-in.
• Very strong for IoT, edge devices and industrial protocols.
• A huge community and library of nodes.
• Runs on anything from a Raspberry Pi to a Kubernetes cluster.

Trade-offs:

• Large flows become hard to read and test.
• Multi-user editing, access control and fleet management need extra work or FlowFuse.
• Not a SaaS: you host, secure and update it yourself.
• Fewer ready-made business-app connectors than hosted automation tools.

How Node-RED compares

Each alternative below solves a similar integration problem with a different trade-off between hosting, cost and connectors.

• n8n: self-hostable workflow automation with more business-app integrations and a fair-code license.
• Zapier: hosted automation for SaaS apps, no servers to run, priced per task.
• Make: hosted visual scenarios for business apps, priced by operations.
• Microsoft Power Automate: automation inside Microsoft 365, with desktop RPA.
• Pipedream: code-first workflows for developers.
• IFTTT: simple consumer and smart-home applets.

Is Node-RED worth it?

Yes for IoT, edge and home automation projects, and for teams that want a free, self-hosted way to wire devices and APIs together. It is less of a fit for business teams that want a hosted tool with hundreds of SaaS connectors and no servers to manage; Zapier, Make or n8n suit them better. For industrial rollouts across many sites, budget for FlowFuse or your own operations work. If you want help building or scaling Node-RED flows, the low-code agencies and developers on LowCodeDevs can take it on.

Sources

• Node-RED: the project site, nodes library and where it runs.
• Node-RED, Wikipedia: history, license, current release and FlowFuse.
• FlowFuse pricing: products, trial and self-hosting.
• Node-RED Dashboard formally deprecated, FlowFuse: Dashboard 1.0 and Dashboard 2.0.
• What is Node-RED?, FlowFuse: use cases and deployment (written by the commercial Node-RED company).