Node-RED started in 2013 as a side project by Nick O'Leary and Dave Conway-Jones at IBM's Emerging Technology Services group, originally as a proof-of-concept for visualizing MQTT topic mappings. It quickly grew into a general-purpose tool for building event-driven applications and was open-sourced in September 2013. The project moved to the JS Foundation in 2016 and now lives under the OpenJS Foundation. Its browser-based flow editor lets users wire together input, processing, and output nodes visually — flows are stored as JSON, making them easy to version control, share, and import. Custom JavaScript functions can be written directly in the editor using a built-in code editor with syntax highlighting.
The lightweight Node.js runtime takes advantage of JavaScript's event-driven, non-blocking model, which makes Node-RED equally at home on a Raspberry Pi at the network edge as in a cloud deployment. The community has published over 5,000 nodes and flows covering industrial protocols (Modbus, OPC-UA, Siemens S7, BACnet), messaging systems (MQTT, Kafka, AMQP), cloud services (AWS, Azure, Google Cloud), databases, and increasingly AI/LLM integrations including OpenAI API nodes for chat, embeddings, image generation, and real-time audio. Several PLC and IoT hardware vendors have adopted Node-RED as a standard component in their platforms, and the tool has strong adoption in industrial IoT, home automation, and prototyping use cases.
The latest stable release is v4.1.8 with active development continuing in 2026. FlowFuse, co-founded by Node-RED creator Nick O'Leary, provides an enterprise layer adding collaborative development, remote deployment management, DevOps pipelines, and cloud hosting for teams that need production-grade Node-RED at scale. For the agentic AI ecosystem, Node-RED serves as a visual integration bridge — its flows can orchestrate LLM calls, tool use, and data transformations alongside traditional automation, making it valuable for teams building AI-augmented workflows that also need to connect to legacy systems, industrial hardware, or custom APIs that newer agent-focused platforms do not natively support.