Skip to content
Book a Demo
software
Data Management
use cases
Industrial Automation, Network & Device Management
Licensing
3rd party

Node-Red

Low-code programming for event-driven applications

The easiest way to collect, transform and visualize real-time data. Node-RED’s goal is to enable anyone to build applications that collect, transform and visualize their data; building flows that can automate their world. Its low-code nature makes it accessible to users of any background, whether for home automation, industrial control systems or anything in between.

Learn more: https://nodered.org/

Contact us to add to Neeve
Benefits of Node-RED on Neeve
Through this unique partnership, Node-RED can run within the container environment on Neeve Secure Edge, making it cloud-managed and configurable—all within a fully managed service. For mission-critical logic and automation, the container can run across highly available and redundant edge clusters for increased resiliency.
Simplified Maintenance: Utilize a managed hardware solution with cloud-managed Node-RED instances.
Agile Logic Development: Rapidly deploy and iterate on data transformations and logic without complex CI/CD overhead.
Secure Integration: Access and normalize real-time data from disparate OT devices and cloud APIs through a single secure gateway.
Standardized Automation: Standardize logic sequences across the entire portfolio using the Neeve-managed Node-RED environment.
Improved Resiliency: Leverage “edge cloud” clustered compute infrastructure to ensure high availability for event-driven flows.
Architecture
By default, Node-RED does not have authentication enabled. In the Neeve Marketplace, ensure admin Auth is configured via environment variables or a mounted settings.
Deployment model: Singleton (One pod). Multiple replicas are generally avoided unless using a shared state/database back-end, as flows are stored locally.
Workload: Event-driven; memory usage scales with the number of active flows and message throughput.
Components: Node.js runtime, Web-based Flow Editor, Dashboard (optional UI).
Data flows: * TCP 1880: Web Editor and Dashboard UI.
Various: Depends on nodes (MQTT, HTTP, BACnet, TCP/UDP).
Failure domains: Single instance. If the pod fails, active timers or stateful flows (e.g., “join” nodes) reset.