---
title: "Edge Device Management for Node-RED • FlowFuse"
description: "Edge device management for Node-RED. Deploy, manage, and roll back flows remotely without VPNs or inbound ports."
canonical_url: "https://flowfuse.com/platform/device-agent/"
meta:
  keywords: "Edge Device Management, OT Device Management, Device Provisioning, OT/IT Convergence, IoT Fleet Management, Industrial IoT Device Management"
  "og:description": "Edge device management for Node-RED. Deploy, manage, and roll back flows remotely without VPNs or inbound ports."
  "og:title": "Edge Device Management for Node-RED • FlowFuse"
---

> Index of every page on this site: [llms.txt](https://flowfuse.com/llms.txt)

# **Edge Device Management for **Node-RED

The FlowFuse Device Agent runs Node-RED on your edge hardware and connects it to FlowFuse. Open the editor anywhere, push the same flows to every machine in a group, and roll back between snapshots without a site visit, a VPN request, or a single inbound port.

> *"Without FlowFuse, I would be able to support maybe one production unit, but that's it. FlowFuse gives us the chance to deliver what the business asks us for while maintaining our small team size." *

*![Felix Reck](https://flowfuse.com/images/customer-headshots/felix-reck-walter-tools.png)**Felix Reck** · IT Application Manager, Walter Tools (formerly) [Walter Tools](https://flowfuse.com/customer-stories/scaling-industrial-iot-operations-while-maintaining-competitive-edge/)** scaled from 1 to 130+ instances with the same IT team.***

## Install the Device Agent from your terminal

Start where your hardware already is. Run the installer on the machine you want to bring online and it walks you through the rest, including creating a FlowFuse account if you don't have one yet.

`/bin/bash -c "$(curl -fsSL https://flowfuse.github.io/device-agent/get.sh)" && ./flowfuse-device-agent-installer`

Installing with npm or Docker instead? [The installation docs cover every route](https://flowfuse.com/docs/device-agent/install/overview/).

## What FlowFuse Edge Device Management Fixes

Node-RED is easy to run on one machine in front of you. The work starts when that machine is remote, the fleet grows, and every change has to reach production safely.

### **Getting to the machine costs a day**

Changing a flow on a remote machine can mean a VPN request, a jump host, or someone driving to the site.

The Device Agent makes an outbound connection to FlowFuse instead. Put the machine in [Developer Mode](https://flowfuse.com/docs/device-agent/quickstart/#developer-mode) and open its Node-RED editor in your browser, wherever the machine is running.

### **Every site ends up with its own version of the flow**

One engineer fixes a flow on site two. Someone else copies it to site five. Six months later, nobody is sure which version is running where.

Create a snapshot and set it as the target for a [device group](https://flowfuse.com/docs/user/device-groups/). Every device in the group runs that version, and new devices automatically receive the same target when they join.

### **200 machine updates, 200 chances to go wrong.**

Promote a snapshot along a [DevOps pipeline](https://flowfuse.com/docs/user/devops-pipelines/) (development, then test, then production) so a change only reaches the plant floor after it has run somewhere safe. If it still goes wrong, set the previous snapshot as the target and the fleet rolls back.

### **The connection drops, but the line doesn't**

A remote machine shouldn't stop doing its job because its connection to FlowFuse disappears.

Flows continue running on the device when its connection to FlowFuse is lost. The Device Agent reconnects automatically and picks up the target snapshot when connectivity is restored.

### **“What version is site 12 running?” shouldn't require a phone call**

When devices are spread across plants, answering a simple version question can mean asking someone at each site to check.

Registered machines show their online status, the snapshot they are running, and whether it matches the version assigned to them.

### **Security has to sign it off before anything goes to the plant**

IT and security teams need to know what an edge machine connects to before allowing it onto the network. The Device Agent is [Apache-2.0 open source](https://github.com/FlowFuse/device-agent), so your team can inspect how it works. It uses outbound connections to FlowFuse, with no inbound ports required for remote management.

## How the Device Agent Works

Three steps take you from a machine sitting on a bench to a Node-RED application running in production.

[Learn how to install the FlowFuse Device Agent](https://flowfuse.com/docs/device-agent/install/overview/)

**Step one**

### **Install and provision**

Run the installer on the machine. It installs the required components, registers the machine with your FlowFuse team, and configures the Device Agent as a service so it starts again after a reboot.

For larger deployments, use [bulk registration options](https://flowfuse.com/docs/device-agent/register/#bulk-registration) to provision multiple devices.

**Step two**

### **Build and test against the real hardware**

Developer Mode opens that device's Node-RED editor through FlowFuse. Build against the real PLC, sensors, and network, then take a snapshot when the application is ready.

**Step three**

### **Deploy the version you tested**

Set that snapshot as the target for one device or a group of hundreds. Devices update to the assigned version and stay there until you assign another target.

Use [DevOps pipelines](https://flowfuse.com/docs/user/devops-pipelines/) to move changes from development through testing and into production.

## Supported Hardware, Operating Systems, and Protocols

### **Hardware and operating systems**

LinuxWindowsmacOSDockerKubernetesArmx86Node.js 18, 20, 22, 24 [**Hardware setup guides**](https://flowfuse.com/docs/hardware/introduction/)

### **Industrial protocols and systems**

[**Modbus**](https://flowfuse.com/docs/flowfuse-nodes/edge/modbus/) [**OPC UA**](https://flowfuse.com/integrations/opcua/) [**MQTT**](https://flowfuse.com/blog/2024/06/how-to-use-mqtt-in-node-red/) [**S7**](https://flowfuse.com/docs/flowfuse-nodes/edge/s7/) [**EtherNet/IP**](https://flowfuse.com/blog/2025/10/using-ethernet-ip-with-flowfuse/) [**Serial**](https://flowfuse.com/blog/2025/07/connect-legacy-equipment-serial-flowfuse/) [**REST**](https://flowfuse.com/docs/node-red/integration-technologies/rest/) [**SQL**](https://flowfuse.com/docs/node-red/database/mysql/)5,000+ Node-RED nodes

## OT Device Management and IoT Fleet Management

Plant-floor applications rarely live in isolation. They connect PLCs, machines, databases, APIs, and other systems while IT teams need a consistent way to deploy and maintain them across sites.

![FlowFuse Edge: industrial edge connectivity](https://flowfuse.com/images/home/home-scada.png)

### **OT device management**

[FlowFuse Edge](https://flowfuse.com/product/edge/) helps OT teams connect PLCs, machines, and controllers and standardize industrial applications across sites.

![FlowFuse Fleet: device fleet management console](https://flowfuse.com/images/product/fleet.jpg)

### **IoT fleet management**

[FlowFuse Fleet](https://flowfuse.com/product/fleet/) provides tools for pushing flows, shipping updates, and rolling back applications across distributed devices.

## **Pick the machine that’s inconvenient to visit**

Install the Device Agent on that one and watch it appear in FlowFuse. It is one command, and it costs nothing to find out.

[**Install the Device Agent**](https://flowfuse.com/platform/device-agent/#install-from-your-terminal) [**Talk to Us**](https://flowfuse.com/book-demo/)

## Frequently Asked Questions

###

###

###

###

###

###

###

```json
{"@context":"https://schema.org","@graph":[{"@id":"https://flowfuse.com/#website","@type":"WebSite","description":"FlowFuse builds your first industrial solution with your team, proves it at one plant, then helps you roll it out to every plant, faster each time.","inLanguage":"en","name":"FlowFuse","url":"https://flowfuse.com/","alternateName":["FlowForge","Flow Fuse"],"publisher":{"@id":"https://flowfuse.com/#identity"}},{"@id":"https://flowfuse.com/platform/device-agent/#webpage","description":"Edge device management for Node-RED. Deploy, manage, and roll back flows remotely without VPNs or inbound ports.","name":"Edge Device Management for Node-RED","url":"https://flowfuse.com/platform/device-agent/","@type":["WebPage","FAQPage"],"isPartOf":{"@id":"https://flowfuse.com/#website"},"mainEntity":[{"@id":"https://flowfuse.com/platform/device-agent/#/schema/question/1"},{"@id":"https://flowfuse.com/platform/device-agent/#/schema/question/2"},{"@id":"https://flowfuse.com/platform/device-agent/#/schema/question/3"},{"@id":"https://flowfuse.com/platform/device-agent/#/schema/question/4"},{"@id":"https://flowfuse.com/platform/device-agent/#/schema/question/5"},{"@id":"https://flowfuse.com/platform/device-agent/#/schema/question/6"},{"@id":"https://flowfuse.com/platform/device-agent/#/schema/question/7"}],"potentialAction":[{"@type":"ReadAction","target":["https://flowfuse.com/platform/device-agent/"]}],"primaryImageOfPage":{"@id":"https://flowfuse.com/#logo"}},{"@id":"https://flowfuse.com/#identity","@type":"Organization","legalName":"FlowFuse Inc.","name":"FlowFuse","url":"https://flowfuse.com","alternateName":["FlowForge","Flow Fuse"],"logo":{"@id":"https://flowfuse.com/#logo"},"sameAs":["https://twitter.com/FlowFuseinc","https://github.com/FlowFuse","https://www.linkedin.com/company/flowfuse/","https://www.facebook.com/FlowFuse/","https://www.youtube.com/channel/UCbBzP8NZbv3WDtlt4UouA-g"]},{"@id":"https://flowfuse.com/platform/device-agent/#/schema/question/1","@type":"Question","inLanguage":"en","name":"How much does the Device Agent cost?","acceptedAnswer":{"@type":"Answer","text":"The Device Agent is free, and open-source. Depending on which offering/hosting of FlowFuse you choose there may be charges for the FlowFuse service itself, you can find out more on our pricing page."}},{"@id":"https://flowfuse.com/platform/device-agent/#/schema/question/2","@type":"Question","inLanguage":"en","name":"Can I run the Device Agent in a closed network?","acceptedAnswer":{"@type":"Answer","text":"Yes, you can, although it does need to be able to connect to your FlowFuse (Cloud or your self-hosted instance) in order to receive updates and deploy new flows. Once they're deployed though, the device agent will keep your flows running even if it loses connection to the internet."}},{"@id":"https://flowfuse.com/platform/device-agent/#/schema/question/3","@type":"Question","inLanguage":"en","name":"How do I deploy to thousands of devices at once?","acceptedAnswer":{"@type":"Answer","text":"With FlowFuse, you can use Provisioning Tokens to register large numbers of devices. This will automatically register each device in the FlowFuse Editor and save you a lot of clicking."}},{"@id":"https://flowfuse.com/platform/device-agent/#/schema/question/4","@type":"Question","inLanguage":"en","name":"I've installed the Device Agent on my device, how do I access the Node-RED Editor?","acceptedAnswer":{"@type":"Answer","text":"The key advantage of the device agent is that it allows you to access the Node-RED editor from FlowFuse directly. Simply navigate to the device in the FlowFuse UI, and click on the \"Open Editor\" button. Once you've made your changes, within FlowFuse you can then rollout those flows to hundreds of other devices in just a few clicks."}},{"@id":"https://flowfuse.com/platform/device-agent/#/schema/question/5","@type":"Question","inLanguage":"en","name":"What's the difference between \"Fleet Mode\" and \"Developer Mode\"","acceptedAnswer":{"@type":"Answer","text":"\"Fleet Mode\" allows you to deploy a single Snapshot to multiple devices at once. The Device will have a \"Target Snapshot\", and whenever that is set, your device will automatically update.\n\n\"Developer Mode\" on the other hand opens a tunnel to your device, allowing you to edit the flows on that device directly. This is useful for debugging flows, or testing new flows on live hardware, before distributing them out to the rest of your fleet."}},{"@id":"https://flowfuse.com/platform/device-agent/#/schema/question/6","@type":"Question","inLanguage":"en","name":"What are the system requirements for the Device Agent? Will it run on my hardware?","acceptedAnswer":{"@type":"Answer","text":"Device Agent supports Node.js 18, 20, 22, and 24, and is designed to work with a wide range of devices. If you're unsure if your device is supported, please do get in touch."}},{"@id":"https://flowfuse.com/platform/device-agent/#/schema/question/7","@type":"Question","inLanguage":"en","name":"Can I run the Device Agent as a service?","acceptedAnswer":{"@type":"Answer","text":"Yes, the Device Agent is designed to run as a service on your device, we have an example written up for a Raspberry Pi here."}},{"@id":"https://flowfuse.com/#logo","@type":"ImageObject","caption":"FlowFuse","contentUrl":"https://flowfuse.com/handbook/images/logos/ff-logo--square--dark.png","inLanguage":"en","url":"https://flowfuse.com/handbook/images/logos/ff-logo--square--dark.png"}]}
```

## Sitemap

See the full [sitemap](https://flowfuse.com/sitemap.md) for all pages.
