[{"data":1,"prerenderedAt":1177},["ShallowReactive",2],{"blog-\u002Fblog\u002F2026\u002F02\u002Fmodbus-tcp-vs-modbus-rtu":3,"featureCatalog":247,"changelog-titles":642,"blog-all-for-related":1176},{"id":4,"title":5,"authors":6,"body":8,"cta":220,"date":224,"description":225,"extension":226,"features":227,"image":228,"lastUpdated":227,"meta":229,"navigation":236,"path":237,"release":227,"seo":238,"sitemap":239,"stem":240,"subtitle":241,"tags":242,"tldr":245,"video":227,"__hash__":246},"blog\u002Fblog\u002F2026\u002F02\u002Fmodbus-tcp-vs-modbus-rtu.md","Modbus TCP vs Modbus RTU: Reliability, Latency, and Failure Modes",[7],"sumit-shinde",{"type":9,"value":10,"toc":205},"minimark",[11,21,24,27,32,35,38,41,48,51,55,58,61,64,67,73,76,79,83,86,91,94,97,100,106,110,113,116,119,125,141,144,148,151,154,163,166,170,173,176,179,182,186,189,192,195,198],[12,13,14,15,20],"p",{},"Modbus shipped in 1979. It has outlasted every protocol that was meant to replace it, survived the transition from relay logic to microprocessors and modern SCADA systems, and is still running production lines today. That kind of longevity does not happen by accident. It exists because the protocol is simple, deterministic, and unambiguous, at least in its original form, a point I have discussed in more detail in a ",[16,17,19],"a",{"href":18},"\u002Fblog\u002F2026\u002F01\u002Fwhy-modbus-still-exist\u002F","separate article",".",[12,22,23],{},"Then TCP came along. The data model stayed the same, identical function codes and identical register maps. But the assumptions underneath changed completely, including expectations about the network, failure modes, and what happens when things go wrong. The industry gained real capability, but it also inherited an entirely new class of problems, ones that look nothing like the challenges Modbus engineers spent forty-seven years learning to solve.",[12,25,26],{},"That gap is what most people miss. And it is exactly what this post is about.",[28,29,31],"h2",{"id":30},"they-are-not-the-same-protocol-in-different-clothes","They Are Not the Same Protocol in Different Clothes",[12,33,34],{},"Modbus RTU runs over serial. That sounds simple until you consider what serial actually means in practice: one master, multiple slaves, one conversation at a time. The master initiates every transaction, the slave responds, and nothing else happens on the wire until that exchange completes.",[12,36,37],{},"The physical layer is almost always RS-485 in industrial installations, a differential pair that can run hundreds of meters, tolerate significant electrical noise, and connect up to 247 devices on a single bus.",[12,39,40],{},"That architecture imposes hard constraints. Only one device can transmit at a time. Timing between bytes within a frame matters: RTU uses silence on the line to mark frame boundaries, so a gap of 3.5 character times signals the end of one message and the start of the next. Get the baud rate wrong, introduce a noisy cable that stretches a byte, or misconfigure inter-character timing, and the frame parser loses its place. The message is silently discarded. No retransmission, no acknowledgment, just a timeout.",[12,42,43],{},[44,45],"img",{"alt":46,"src":47,"title":46},"Image showing Modbus RTU on RS-485 and Modbus TCP on Ethernet.","\u002Fblog\u002F2026\u002F02\u002Fimages\u002Fmodbus-rtu-and-tcp-physical-layer.png",[12,49,50],{},"Modbus TCP moves the same application layer onto Ethernet and wraps it in a TCP socket. The serial constraints disappear. Multiple masters can coexist, transactions can be pipelined, and the physical layer handles collision detection and retransmission. What you gain in flexibility, you trade for a different set of assumptions. TCP guarantees delivery, but not timing. A retransmission storm on a busy network can stretch response times in ways that RTU, for all its limitations, never would.",[28,52,54],{"id":53},"latency-what-the-numbers-actually-mean-on-the-floor","Latency: What the Numbers Actually Mean on the Floor",[12,56,57],{},"RTU latency is predictable almost to the microsecond. That sounds like a strength until you realize how slow predictable can be.",[12,59,60],{},"At 9600 baud, a typical Modbus RTU transaction (request plus response) takes 50 to 100 milliseconds per device. Move to 115200 baud and that drops under 10 milliseconds. But you are still polling sequentially. Ten devices at 9600 baud means your slowest sensor gets updated once per second at best. Add more devices and the math gets worse in a straight line.",[12,62,63],{},"That ceiling matters. A real-world example: a water treatment plant running 32 RTU devices on a single RS-485 bus at 9600 baud had a worst-case poll cycle of nearly four seconds. When the control engineer needed tighter feedback on a pH dosing loop, the only options were to reduce the device count on that segment, split the bus, or increase baud rate, all of which required physical work on a running system.",[12,65,66],{},"Modbus TCP removes the baud rate ceiling and adds pipelining. A well-configured TCP master can have multiple transactions in flight simultaneously. On a lightly loaded Ethernet network, round trip times under 2 milliseconds are routine. For many applications, that is enough to stop thinking about latency altogether.",[12,68,69],{},[44,70],{"alt":71,"src":72,"title":71},"Chart comparing Modbus RTU polling latency with Modbus TCP network latency","\u002Fblog\u002F2026\u002F02\u002Fimages\u002Fmodbus-rtu-tcp-latency.png",[12,74,75],{},"The catch is that Ethernet latency is not flat. It varies with network load, switch queue depth, and the TCP stack on the device side. Most of the time the numbers look excellent. Under the wrong conditions, they do not. A PLC with a modest embedded TCP stack, hit with traffic from a network scan or a broadcast storm, can stretch its response time by an order of magnitude. RTU would have delivered the same response time it always does.",[12,77,78],{},"RTU offers better worst-case latency. TCP offers better average latency. In industrial control, worst-case is usually what you design for.",[28,80,82],{"id":81},"failure-modes-what-breaks-how-it-breaks-and-whether-you-will-know","Failure Modes: What Breaks, How It Breaks, and Whether You Will Know",[12,84,85],{},"This is where the two protocols diverge most sharply, and where choosing wrong costs the most.",[87,88,90],"h3",{"id":89},"rtu-failures-are-loud-and-physical","RTU Failures Are Loud and Physical",[12,92,93],{},"RTU failures tend to be physical. A corroded terminal block. A cable run too close to a variable frequency drive. A termination resistor missing from one end of the bus. The symptoms are usually obvious: CRC errors climb, devices stop responding, the master logs timeouts.",[12,95,96],{},"What RTU rarely does is fail silently. Framing errors and timeouts are visible. The master knows a transaction failed. The application layer gets a clear signal that something is wrong, even if locating the fault takes time.",[12,98,99],{},"Locating it is the hard part. RS-485 is a shared medium, which means a single bad connection can drag down every device on the segment. Isolating which node is responsible requires methodical disconnection or a bus analyzer. Neither is fast at 2 AM with a line down.",[12,101,102],{},[103,104,105],"strong",{},"But at least you know it is down.",[87,107,109],{"id":108},"tcp-failures-are-quiet-and-strange","TCP Failures Are Quiet and Strange",[12,111,112],{},"TCP failures are quieter and more varied. The physical layer is more robust: Ethernet cable is forgiving, switches regenerate signals, and a single bad port does not take down the network. But the failure surface is much broader.",[12,114,115],{},"A device can be electrically healthy and passing traffic, yet still behave badly. Connection state gets out of sync. A TCP socket on a cheap embedded device does not close cleanly after a timeout, leaving the master waiting on a half-open connection that looks alive but delivers nothing. A managed switch renegotiating link speed during a firmware update introduces 30 seconds of elevated latency that looks, from the application's perspective, like a slow device.",[12,117,118],{},"The worst TCP failures are the ones that are almost working. Partial connectivity. Occasional dropped transactions. Response times elevated but not elevated enough to trip a timeout threshold.",[12,120,121],{},[44,122],{"alt":123,"src":124,"title":123},"Half-open TCP socket failure where the master waits on a connection that never responds.","\u002Fblog\u002F2026\u002F02\u002Fimages\u002Fmodbus-tcp-open-connection-failure.png",[12,126,127,128,134,135,140],{},"RFC 793 formally defines the half-open state: when one end of a TCP connection crashes or closes without notifying the other, the remaining side may wait indefinitely on a connection that appears alive and delivers nothing (",[16,129,133],{"href":130,"rel":131},"https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc793",[132],"nofollow","RFC 793, Section 3.4","). Rockwell Automation's troubleshooting documentation describes how conditions like duplex mismatches during switch replacement can produce exactly this pattern: performance that degrades quietly and stays within configured thresholds (",[16,136,139],{"href":137,"rel":138},"https:\u002F\u002Fliterature.rockwellautomation.com\u002Fidc\u002Fgroups\u002Fliterature\u002Fdocuments\u002Fat\u002Fenet-at003_-en-p.pdf",[132],"Rockwell Automation, ENET-AT003",").",[12,142,143],{},"RTU tends to fall over cleanly. TCP tends to degrade quietly. Degraded is harder to catch than broken.",[87,145,147],{"id":146},"tcp-introduces-a-failure-mode-that-rtu-never-had-security","TCP Introduces a Failure Mode That RTU Never Had: Security",[12,149,150],{},"Modbus has no authentication. On a serial bus, that is usually acceptable, because physical access to the wire implies physical access to the facility. On an Ethernet network, that assumption collapses entirely.",[12,152,153],{},"Modbus TCP devices reachable from a corporate network, or worse from the internet, will respond to commands from anyone who sends them. No credentials. No audit trail. No way to distinguish a legitimate master from an attacker with a laptop and a Modbus client.",[12,155,156,157,162],{},"This is not theoretical. Shodan regularly turns up Modbus TCP devices with publicly routable IP addresses. ICS security assessments routinely find Modbus exposed on flat networks shared with corporate IT. The clearest demonstration of what that exposure enables is ",[16,158,161],{"href":159,"rel":160},"https:\u002F\u002Fwww.dragos.com\u002Fblog\u002Fprotect-against-frostygoop-ics-malware-targeting-operational-technology\u002F",[132],"FrostyGoop",", malware discovered by Dragos in 2024 and the first ever to use Modbus TCP to cause direct physical impact. Attackers targeted a district energy company in Lviv, Ukraine supplying heat to over 600 apartment buildings, port 502 was open to the internet, no network compromise required, and remediation took nearly two days while residents endured sub-zero temperatures. No credentials were needed. Modbus provided none to ask for.",[12,164,165],{},"RTU is not inherently secure either, but attacking it requires being physically present on the wire. TCP removes that requirement entirely.",[28,167,169],{"id":168},"choosing-between-them","Choosing Between Them",[12,171,172],{},"Most engineers do not choose between RTU and TCP from a blank slate. They inherit a system, get handed a specification, or discover that the device they need only supports one of them. The real decision is narrower: whether what is already in place is appropriate for what the system now needs to do.",[12,174,175],{},"RTU is the right answer when device count is small, cable runs are already there, polling rates are modest, and nothing outside the cabinet needs to reach the network. Those conditions describe a large percentage of working industrial installations. Changing a system that meets all of them adds risk for no operational benefit.",[12,177,178],{},"TCP makes sense when you need to integrate field devices with higher-level systems like SCADA, historians, or MES, when device count or poll rate has grown beyond what serial can comfortably handle, or when the network already exists and adding serial infrastructure would cost more than it saves. It also makes sense when you need multiple masters, which serial cannot support without external arbitration hardware.",[12,180,181],{},"The hybrid case is a serial network running reliably for fifteen years, with a gateway at the head end converting RTU to TCP for the SCADA system. It is more common than either pure scenario, and more sensible than it looks on paper. The gateway adds a failure point, but it also insulates field devices from the corporate network. That insulation is worth keeping. Replacing it to simplify the architecture is usually not the right trade.",[28,183,185],{"id":184},"what-to-actually-do-differently-based-on-this","What to Actually Do Differently Based on This",[12,187,188],{},"If you are deploying RTU: use the highest baud rate the cable length and device count will reliably support, do not leave devices at 9600 baud out of habit; document your bus topology, because when something fails at night the person troubleshooting will not be you; and install proper termination resistors at both ends of every RS-485 segment, since this causes more problems than almost anything else.",[12,190,191],{},"If you are deploying TCP: isolate Modbus devices on a dedicated VLAN or network segment and never put them on the corporate LAN; configure short TCP timeouts and explicit connection retry logic in your master, because half-open connections will happen; and log poll latency over time, since degradation that stays inside timeout thresholds will not alarm and you have to trend it.",[12,193,194],{},"If you are maintaining a hybrid gateway architecture, resist the urge to rationalize it away. It is doing work.",[12,196,197],{},"The two protocols make different guarantees, fail differently, and require different diagnostic skills when something goes wrong. Understanding that distinction before the system is designed costs nothing. Understanding it for the first time during an incident costs considerably more.",[12,199,200,201,20],{},"For a practical guide to connecting Modbus PLCs, alongside OPC UA, EtherNet\u002FIP, and Siemens S7, to MQTT, cloud, and enterprise systems, see the ",[16,202,204],{"href":203},"\u002Flanding\u002Fplc\u002F","FlowFuse PLC integration overview",{"title":206,"searchDepth":207,"depth":207,"links":208},"",4,[209,211,212,218,219],{"id":30,"depth":210,"text":31},2,{"id":53,"depth":210,"text":54},{"id":81,"depth":210,"text":82,"children":213},[214,216,217],{"id":89,"depth":215,"text":90},3,{"id":108,"depth":215,"text":109},{"id":146,"depth":215,"text":147},{"id":168,"depth":210,"text":169},{"id":184,"depth":210,"text":185},{"type":221,"title":222,"description":223},"sign-up","Stop Debugging Modbus at 2 AM","FlowFuse supports both Modbus RTU and TCP across the full OT\u002FIT stack, with the monitoring, logging, and fleet management to catch problems before they take down the line.","2026-02-20","A practical engineering guide to choosing between Modbus RTU and Modbus TCP, covering real latency numbers, failure modes that hide in plain sight, and how each protocol behaves when things go wrong.","md",null,"\u002Fblog\u002F2026\u002F02\u002Fimages\u002Fmodbus-rtu-vs-tcp.png",{"excerpt":230},{"type":9,"value":231},[232],[12,233,14,234,20],{},[16,235,19],{"href":18},true,"\u002Fblog\u002F2026\u002F02\u002Fmodbus-tcp-vs-modbus-rtu",{"title":5,"description":225},{"loc":237},"blog\u002F2026\u002F02\u002Fmodbus-tcp-vs-modbus-rtu","What nobody tells you until the line goes down",[243,244],"flowfuse","modbus","Modbus RTU and Modbus TCP share the same data model but make entirely different assumptions about the network, failure modes, and latency. RTU failures are loud and physical while TCP failures tend to degrade silently, and TCP's exposure on Ethernet introduces security risks that serial never had choosing between them requires understanding these tradeoffs, not just swapping protocols.","y-25aIBJGcvYRgGZOfNqRDo_pDdLwv9zD29rHZeI9_0",{"id":248,"extension":249,"meta":250,"sections":251,"stem":640,"__hash__":641},"featureCatalog\u002Ffeature-catalog.yml","yml",{},[252,303,404,466,543,622],{"id":253,"title":254,"features":255},"ai-automation","AI & Automation",[256,266,276,286,292,298],{"id":257,"title":258,"description":259,"docsLink":260,"changelog":261,"tiers":265},"flowfuse-expert-ai","FlowFuse Expert AI","Build industrial apps with agents, and query the state of the factory with an agent. Adapt your current hardware and machines so agentic work can be done against them, without ripping and replacing what's already on the plant floor.","\u002Fdocs\u002Fuser\u002Fexpert\u002F",[262],{"url":263,"release":264},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner\u002F","2.28",{"edge":236,"hub":236,"fleet":236},{"id":267,"title":268,"description":269,"docsLink":270,"changelog":271,"subfeature":236,"showOnPricing":274,"tiers":275},"flowfuse-expert-support-mode","Support Mode","Chat-based assistance for FlowFuse and Node-RED, including Node-RED instance management through natural language.","\u002Fdocs\u002Fuser\u002Fexpert\u002Fchat\u002F#support-mode",[272],{"url":273,"release":264},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context\u002F",false,{"edge":236,"hub":236,"fleet":236},{"id":277,"title":278,"description":279,"docsLink":280,"changelog":281,"subfeature":236,"showOnPricing":274,"tiers":285},"flowfuse-expert-application-building","Application Building","Describe what you want to build and FlowFuse Expert assembles it on your workspace, adding tabs, wiring nodes, and configuring properties.","\u002Fdocs\u002Fuser\u002Fexpert\u002Fchat\u002F",[282],{"url":283,"release":284},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building\u002F","2.30",{"edge":236,"hub":236,"fleet":236},{"id":287,"title":288,"description":289,"docsLink":290,"subfeature":236,"beta":236,"showOnPricing":274,"tiers":291},"flowfuse-expert-insights-mode","Insights Mode","Connects FlowFuse Expert to MCP servers in your Node-RED instances, enabling real-time data queries and actions through a single chat interface.","\u002Fdocs\u002Fuser\u002Fexpert\u002Fchat\u002F#insights-mode",{"edge":236,"hub":236,"fleet":236},{"id":293,"title":294,"description":295,"docsLink":296,"tiers":297},"mcp-servers","Agentic Operations","Expose your Node-RED flows as tools an AI agent can call directly, so agents can query the state of the factory or trigger actions without custom integration work.","\u002Fnode-red\u002Fflowfuse\u002Fmcp\u002F",{"edge":236,"hub":236,"fleet":236},{"id":299,"title":300,"description":301,"tiers":302},"onnx-integration","ONNX Integration","Run trained machine learning models directly in your flows, including on edge hardware, without sending data out to an external inference service.",{"edge":236,"hub":236,"fleet":236},{"id":304,"title":305,"features":306},"build","Build",[307,313,319,329,335,341,345,351,357,365,371,375,379,388,396],{"id":308,"title":309,"description":310,"docsLink":311,"tiers":312},"edge-development","Edge Development","Develop and test Node-RED flows directly on edge devices with a remote editor proxy.","\u002Fdocs\u002Fdevice-agent\u002Fquickstart\u002F",{"edge":236,"hub":274,"fleet":236},{"id":314,"title":315,"description":316,"docsLink":317,"tiers":318},"private-npm-registry","Custom Node-RED Nodes","Create and manage your own private npm registry for Node-RED nodes, so you can share custom nodes across your team and devices without publishing them publicly.","\u002Fdocs\u002Fuser\u002Fcustom-npm-packages\u002F",{"edge":236,"hub":236,"fleet":236},{"id":320,"title":321,"description":322,"docsLink":323,"changelog":324,"tiers":328},"flowfuse-tables","FlowFuse Tables","A managed PostgreSQL database for every application, so you can store and query structured data without standing up and maintaining your own database.","\u002Fdocs\u002Fuser\u002Fff-tables\u002F",[325],{"url":326,"release":327},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation\u002F","2.33",{"edge":236,"hub":236,"fleet":236},{"id":330,"title":331,"description":332,"docsLink":333,"tiers":334},"persistent-files","File Storage","Store and retrieve files from your Node-RED flows, with automatic replication and backup across your devices and hosted instances.","\u002Fdocs\u002Finstall\u002Ffile-storage\u002F",{"edge":236,"hub":236,"fleet":236},{"id":336,"title":337,"description":338,"docsLink":339,"showOnPricing":274,"tiers":340},"persistent-context","Persistent Context","In-memory values defined in a Node-RED flow persist across project restarts and upgrades.","\u002Fdocs\u002Fuser\u002Fpersistent-context\u002F",{"edge":236,"hub":236,"fleet":236},{"id":342,"title":343,"showOnPricing":274,"tiers":344},"static-assets","Static Assets",{"edge":236,"hub":236,"fleet":236},{"id":346,"title":347,"description":348,"docsLink":349,"tiers":350},"team-library","Team Library","Set up standard nodes and flows that can be shared with all team members across your organisation.","\u002Fdocs\u002Fuser\u002Fshared-library\u002F",{"edge":236,"hub":236,"fleet":236},{"id":352,"title":353,"description":354,"docsLink":355,"tiers":356},"personalised-multi-user-dashboards","Personalised Multi-User Dashboards","Build applications that provide unique data to each logged-in user using personalised multi-user dashboards.","https:\u002F\u002Fdashboard.flowfuse.com\u002Fuser\u002Fmulti-tenancy.html",{"edge":236,"hub":236,"fleet":236},{"id":358,"title":359,"description":360,"changelog":361,"subfeature":236,"showOnPricing":274,"tiers":364},"dashboards-view","Dashboards View","Browse and open every dashboard across your team from a dedicated Dashboards view, at both team and application level, without leaving FlowFuse.",[362],{"url":363,"release":327},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards\u002F",{"edge":236,"hub":236,"fleet":236},{"id":366,"title":367,"description":368,"docsLink":369,"tiers":370},"blueprints-converge","Blueprints","Ready-made starting points for your apps, from cross-team Converge templates to OT and IT specific blueprints.","\u002Fdocs\u002Fuser\u002Fconcepts\u002F#blueprint",{"edge":236,"hub":236,"fleet":236},{"id":372,"title":373,"subfeature":236,"showOnPricing":274,"tiers":374},"blueprints-ot-apps","Blueprints - OT APPS",{"edge":236,"hub":274,"fleet":236},{"id":376,"title":377,"subfeature":236,"showOnPricing":274,"tiers":378},"blueprints-it-apps","Blueprints - IT APPS",{"edge":274,"hub":236,"fleet":274},{"id":380,"title":381,"description":382,"changelog":383,"showOnPricing":274,"tiers":387},"immersive-editor-snapshots","Snapshot Details in Immersive Editor","View and manage snapshot details directly inside the immersive editor without leaving your editing session.",[384],{"url":385,"release":386},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor\u002F","2.29",{"edge":236,"hub":236,"fleet":236},{"id":389,"title":390,"description":391,"changelog":392,"showOnPricing":274,"tiers":395},"immersive-editor-drawer","Customisable Immersive Editor Drawer","Pin, move, resize, or full-screen the immersive editor drawer. Your preferences are remembered between sessions.",[393],{"url":394,"release":284},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer\u002F",{"edge":236,"hub":236,"fleet":236},{"id":397,"title":398,"description":399,"changelog":400,"showOnPricing":274,"tiers":403},"embedded-editor-tab-title","Embedded Editor Browser Tab Title","The browser tab title updates to reflect the active Node-RED canvas tab when working in the embedded editor.",[401],{"url":402,"release":386},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title\u002F",{"edge":236,"hub":236,"fleet":236},{"id":405,"title":406,"features":407},"deploy","Deploy",[408,414,423,429,435,441,447,453,458],{"id":409,"title":410,"description":411,"docsLink":412,"tiers":413},"hosted-instances","Cloud Instances","Run Node-RED instances managed and hosted by FlowFuse.","\u002Fdocs\u002Fuser\u002Fintroduction\u002F#creating-a-node-red-instance",{"edge":236,"hub":236,"fleet":236},{"id":415,"title":416,"description":417,"docsLink":418,"changelog":419,"tiers":422},"edge-devices","Edge Instances","Deploy and mange your Node-RED instances on edge PLCs and gateways, with full visibility and control from the cloud.","\u002Fdocs\u002Fdevice-agent\u002Fintroduction\u002F",[420],{"url":421,"release":264},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options\u002F",{"edge":236,"hub":274,"fleet":236},{"id":424,"title":425,"description":426,"docsLink":427,"tiers":428},"custom-hostnames","Custom Hostnames","Access your Node-RED application via your own domain name.","\u002Fdocs\u002Fuser\u002Fcustom-hostnames\u002F",{"edge":274,"hub":236,"fleet":274},{"id":430,"title":431,"description":432,"docsLink":433,"tiers":434},"mqtt-broker","MQTT Broker","Manage and create MQTT clients to transport data for efficient messaging and communication within your applications.","\u002Fdocs\u002Fuser\u002Fteambroker\u002F",{"edge":236,"hub":274,"fleet":236},{"id":436,"title":437,"description":438,"docsLink":439,"showOnPricing":274,"tiers":440},"project-nodes","Project Nodes aka seamless project comms","FlowFuse Project Nodes enable the passing of data and messages between your Node-RED projects.","\u002Fdocs\u002Fuser\u002Fprojectnodes\u002F",{"edge":236,"hub":236,"fleet":236},{"id":442,"title":443,"description":444,"docsLink":445,"tiers":446},"devops-pipelines","DevOps Pipelines","Set up different environments for development, testing, and production Node-RED instances to support a full software delivery lifecycle.","\u002Fdocs\u002Fuser\u002Fdevops-pipelines\u002F",{"edge":236,"hub":236,"fleet":236},{"id":448,"title":449,"description":450,"docsLink":451,"tiers":452},"git-integration","Git Integration","Back up your flows to a remote Git repository through a DevOps Pipeline. Supports GitHub and Azure DevOps repositories.","\u002Fdocs\u002Fuser\u002Fdevops-pipelines\u002F#git-repository-stage",{"edge":274,"hub":236,"fleet":274},{"id":454,"title":455,"description":456,"docsLink":451,"subfeature":236,"showOnPricing":274,"tiers":457},"git-integration-github","GitHub","Push and pull snapshots to GitHub repositories through DevOps Pipeline Git Stages.",{"edge":274,"hub":236,"fleet":274},{"id":459,"title":460,"description":461,"docsLink":451,"changelog":462,"subfeature":236,"showOnPricing":274,"tiers":465},"git-integration-azure","Azure DevOps","Push and pull snapshots to Azure DevOps repositories through DevOps Pipeline Git Stages.",[463],{"url":464,"release":386},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops\u002F",{"edge":274,"hub":236,"fleet":274},{"id":467,"title":468,"features":469},"operate-maintain","Operate & Maintain",[470,476,482,487,495,499,503,508,514,520,525,531,535,539],{"id":471,"title":472,"description":473,"docsLink":474,"tiers":475},"snapshots","Snapshots & Version History","Automatic snapshots on remote devices and hosted instances, plus a full version history timeline so you can roll back to any prior state.","\u002Fdocs\u002Fuser\u002Fsnapshots\u002F",{"edge":236,"hub":236,"fleet":236},{"id":477,"title":478,"description":479,"docsLink":480,"subfeature":236,"showOnPricing":274,"tiers":481},"auto-snapshot-remote","Auto Snapshot (Remote)","Automatically capture a snapshot every time a remote instance is deployed, so you always have a recoverable history of what was running on each device.","\u002Fdocs\u002Fuser\u002Fsnapshots\u002F#auto-snapshots",{"edge":236,"hub":236,"fleet":236},{"id":483,"title":484,"description":485,"docsLink":480,"subfeature":236,"showOnPricing":274,"tiers":486},"auto-snapshot-hosted","Auto Snapshot (Hosted)","Automatically capture a snapshot every time a hosted instance is deployed, so you always have a recoverable history of what was running.",{"edge":236,"hub":236,"fleet":236},{"id":488,"title":489,"description":490,"changelog":491,"subfeature":236,"showOnPricing":274,"tiers":494},"snapshot-comparison","Snapshot Comparison","Compare two snapshots side-by-side with a navigable diff view. Step through every changed, added, or deleted node and see property and code diffs.",[492],{"url":493,"release":386},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer\u002F",{"edge":236,"hub":236,"fleet":236},{"id":496,"title":497,"subfeature":236,"showOnPricing":274,"tiers":498},"version-history-timeline","Version History Timeline",{"edge":236,"hub":236,"fleet":236},{"id":500,"title":501,"tiers":502},"unlimited-workflow-executions","Unlimited Workflow Executions",{"edge":236,"hub":236,"fleet":236},{"id":504,"title":505,"description":506,"tiers":507},"device-fleet-updates","Device Fleet Updates","Connect to edge devices to quickly assess and update logic. Debug one device and roll out improvements to your fleet in minutes, securely without requiring full device access for your whole organisation.",{"edge":236,"hub":274,"fleet":236},{"id":509,"title":510,"description":511,"docsLink":512,"tiers":513},"device-group-management","Device Group Management","Logically group devices assigned to an application and integrate device groups into your DevOps Pipeline for coordinated fleet updates.","\u002Fdocs\u002Fuser\u002Fdevice-groups\u002F",{"edge":236,"hub":274,"fleet":236},{"id":515,"title":516,"description":517,"docsLink":518,"tiers":519},"high-availability","High Availability","Leverage horizontal scaling for reliable and scalable processing of your data through Node-RED.","\u002Fdocs\u002Fuser\u002Fhigh-availability\u002F",{"edge":274,"hub":236,"fleet":274},{"id":521,"title":522,"description":523,"tiers":524},"performance-monitoring","Performance Monitoring & Alerts","Track CPU, memory, and event loop performance across your instances and devices, with email alerts when something needs your attention.",{"edge":236,"hub":236,"fleet":236},{"id":526,"title":527,"description":528,"docsLink":529,"subfeature":236,"showOnPricing":274,"tiers":530},"instance-monitoring","Instance Monitoring","Enable alerts to be sent via email when your Node-RED instances encounter issues.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#alerts",{"edge":236,"hub":236,"fleet":236},{"id":532,"title":533,"subfeature":236,"showOnPricing":274,"tiers":534},"email-alerts","Email Alerts",{"edge":236,"hub":236,"fleet":236},{"id":536,"title":537,"showOnPricing":274,"tiers":538},"api-debug-length-limit","API\u002FDebug Length Limit",{"edge":236,"hub":236,"fleet":236},{"id":540,"title":541,"tiers":542},"protected-instances","Protected Instances",{"edge":274,"hub":236,"fleet":274},{"id":544,"title":545,"features":546},"govern-secure","Govern and Secure",[547,556,562,568,573,579,585,591,599,605,611,617],{"id":548,"title":549,"description":550,"docsLink":551,"changelog":552,"tiers":555},"single-sign-on","Single Sign-On (SSO)","Configure FlowFuse to work with your own SSO provider, allowing users to access FlowFuse with a single set of login credentials.","\u002Fdocs\u002Fadmin\u002Fsso\u002F",[553],{"url":554,"release":327},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups\u002F",{"edge":236,"hub":236,"fleet":236},{"id":557,"title":558,"description":559,"docsLink":560,"tiers":561},"two-factor-authentication","Two-Factor Authentication","Two-factor authentication adds an extra layer of security to your FlowFuse account.","\u002Fdocs\u002Fuser\u002Fuser-settings\u002F#two-factor-authentication",{"edge":236,"hub":236,"fleet":236},{"id":563,"title":564,"description":565,"docsLink":566,"tiers":567},"certified-nodes-it","Certified Nodes - IT","IT certified node bundle includes: Redis, MQTT, HTTP Request, AI nodes (Gemini, Claude, ChatGPT, Ollama), MCP Server","\u002Fblog\u002F2025\u002F07\u002Fcertified-nodes-v2\u002F",{"edge":274,"hub":236,"fleet":236},{"id":569,"title":570,"description":571,"tiers":572},"certified-nodes-ot","Certified OT Connections - OPC-UA, Modbus, etc.","OT certified node bundle includes: OPC-UA, Modbus TCP & RTU, RTSP, EtherNet\u002FIP, AI nodes (Gemini, Claude, ChatGPT, Ollama), MCP Server",{"edge":236,"hub":274,"fleet":274},{"id":574,"title":575,"description":576,"docsLink":577,"tiers":578},"audit-log","Audit Log","Keep track of everything going on in your Node-RED instances and FlowFuse. Audit Logs provide details on what actions have taken place, when they happened, and who did them.","\u002Fdocs\u002Fuser\u002Flogs\u002F#audit-log",{"edge":236,"hub":236,"fleet":236},{"id":580,"title":581,"description":582,"docsLink":583,"tiers":584},"role-based-access-control","Role-Based Access Control","Control who can do what at both the team and application level, from viewers to admins.","\u002Fdocs\u002Fuser\u002Frole-based-access-control\u002F",{"edge":236,"hub":236,"fleet":236},{"id":586,"title":587,"description":588,"docsLink":589,"subfeature":236,"showOnPricing":274,"tiers":590},"application-level-rbac","Application-Level RBAC","Fine-grained access control per application, allowing team members to have different permission levels across different applications without requiring separate teams.","\u002Fdocs\u002Fuser\u002Frole-based-access-control\u002F#application-level-rbac",{"edge":236,"hub":236,"fleet":236},{"id":592,"title":593,"description":594,"changelog":595,"subfeature":236,"showOnPricing":274,"tiers":598},"scoped-personal-access-tokens","Scoped Personal Access Tokens","Restrict a Personal Access Token to specific teams, limit it to read-only operations, or control whether it carries admin privileges.",[596],{"url":597,"release":327},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats\u002F",{"edge":236,"hub":236,"fleet":236},{"id":600,"title":601,"description":602,"docsLink":603,"showOnPricing":274,"tiers":604},"team-members","Team Members","Invite multiple team members to collaborate on the same Node-RED flows.","\u002Fdocs\u002Fuser\u002Fteam\u002F#teams",{"edge":236,"hub":236,"fleet":236},{"id":606,"title":607,"description":608,"docsLink":609,"showOnPricing":274,"tiers":610},"endpoint-security","Endpoint Security","Secure HTTP endpoints for hosted Node-RED instances using FlowFuse credentials.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#security",{"edge":236,"hub":236,"fleet":236},{"id":612,"title":613,"description":614,"docsLink":615,"tiers":616},"baa-for-hipaa","BAA for HIPAA","FlowFuse can sign a Business Associate Agreement to ensure proper safeguarding of protected health information handled on your behalf.","\u002Fhandbook\u002Fsales\u002Fsubscription-agreement-1.5\u002F",{"edge":274,"hub":236,"fleet":274},{"id":618,"title":619,"description":620,"tiers":621},"sbom","Software Bill of Materials","A complete list of all software components used in your Node-RED instances and hosted applications, including version numbers and license information.",{"edge":274,"hub":236,"fleet":274},{"id":623,"title":624,"features":625},"support","Support",[626,631,635],{"id":627,"title":628,"docsLink":629,"tiers":630},"installation-support","Installation Support","\u002Fdocs\u002Finstall\u002Fintroduction\u002F#do-you-need-help-installation-service",{"edge":236,"hub":236,"fleet":236},{"id":632,"title":633,"showOnPricing":274,"tiers":634},"live-chat-support","Live Chat Support",{"edge":236,"hub":236,"fleet":236},{"id":636,"title":637,"docsLink":638,"tiers":639},"enterprise-support","Enterprise Support","\u002Fdocs\u002Fpremium-support\u002F",{"edge":236,"hub":236,"fleet":236},"feature-catalog","0AnkhTIPCECCwP9NmbTWP5HvRYx4FTSao4lG93-HaWM",[643,646,649,652,655,658,660,663,666,669,672,674,677,680,683,686,689,692,695,698,701,704,707,710,713,716,719,722,725,728,731,734,737,740,743,746,749,752,755,758,761,764,767,770,773,776,779,782,785,787,790,793,796,799,802,805,808,810,813,816,819,822,825,827,830,833,836,839,842,845,848,851,854,857,859,862,865,868,871,874,877,880,883,886,889,892,895,898,901,903,906,909,912,915,918,921,924,927,930,933,936,939,942,945,948,951,954,957,959,962,965,968,971,974,977,980,982,985,988,991,994,997,1000,1003,1006,1009,1012,1015,1018,1021,1024,1027,1030,1033,1036,1039,1042,1045,1048,1051,1054,1057,1060,1063,1066,1069,1072,1075,1078,1081,1084,1087,1090,1093,1096,1099,1102,1105,1108,1111,1114,1117,1120,1123,1126,1129,1132,1134,1137,1140,1143,1146,1149,1152,1155,1158,1161,1164,1167,1170,1173],{"path":644,"title":645},"\u002Fchangelog\u002F2023\u002F09\u002Fcustom-node-support","Custom Node Support",{"path":647,"title":648},"\u002Fchangelog\u002F2023\u002F09\u002Fdevops-actions","DevOps Pipeline with action selection",{"path":650,"title":651},"\u002Fchangelog\u002F2023\u002F09\u002Fintroduction-enterprise-tier","Introducing the Enterprise Tier",{"path":653,"title":654},"\u002Fchangelog\u002F2023\u002F09\u002Fpipeline-api","API Endpoint for DevOps Pipeline",{"path":656,"title":657},"\u002Fchangelog\u002F2023\u002F09\u002Fsnapshots-devices","Usability improvements to Device Management",{"path":659,"title":367},"\u002Fchangelog\u002F2023\u002F10\u002Fblueprints",{"path":661,"title":662},"\u002Fchangelog\u002F2023\u002F10\u002Fcertified-nodes","Certified Nodes",{"path":664,"title":665},"\u002Fchangelog\u002F2023\u002F10\u002Fdevice-snapshot-selection","Enhanced Snapshot Selection",{"path":667,"title":668},"\u002Fchangelog\u002F2023\u002F10\u002Fpath-bug-fix","Device Agent path bug fix",{"path":670,"title":671},"\u002Fchangelog\u002F2023\u002F10\u002Fresource-alerts","Resource Monitoring in Audit Log",{"path":673,"title":558},"\u002Fchangelog\u002F2023\u002F11\u002F2fa",{"path":675,"title":676},"\u002Fchangelog\u002F2023\u002F11\u002Fdefault-editor","Device Editor enabled by default",{"path":678,"title":679},"\u002Fchangelog\u002F2023\u002F11\u002Fdevices-in-pipelines","Devices in DevOps Pipelines",{"path":681,"title":682},"\u002Fchangelog\u002F2023\u002F11\u002Fproject-nodes-devices","Project Nodes for Devices",{"path":684,"title":685},"\u002Fchangelog\u002F2023\u002F12\u002Fbilling","No Credit Card required for billing",{"path":687,"title":688},"\u002Fchangelog\u002F2023\u002F12\u002Fblueprint-selection","Blueprint Selection Update",{"path":690,"title":691},"\u002Fchangelog\u002F2023\u002F12\u002Fdevice-groups","Device Groups",{"path":693,"title":694},"\u002Fchangelog\u002F2023\u002F12\u002Femail-alerting-node-red-crash","Email Alerts for Audit Log Events",{"path":696,"title":697},"\u002Fchangelog\u002F2023\u002F12\u002Fnode-red-updated","Node-RED 3.1.3 now available",{"path":699,"title":700},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-audit-log","Introducing the Device Auditlog Feature",{"path":702,"title":703},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-groups-snapshot","Device Groups - Automatic snapshot assignment",{"path":705,"title":706},"\u002Fchangelog\u002F2024\u002F01\u002Ffleet-mode","Renaming \"Default Device Mode\" to \"Fleet Mode\"",{"path":708,"title":709},"\u002Fchangelog\u002F2024\u002F01\u002Fhelm-v2","Helm Chart v2.0",{"path":711,"title":712},"\u002Fchangelog\u002F2024\u002F01\u002Fnew-blueprints","New Blueprints added",{"path":714,"title":715},"\u002Fchangelog\u002F2024\u002F01\u002Fsecurity-updates","Security Updates",{"path":717,"title":718},"\u002Fchangelog\u002F2024\u002F01\u002Fsso-team-membership","Managing Team Membership via SSO",{"path":720,"title":721},"\u002Fchangelog\u002F2024\u002F01\u002Fstreamlined-device-assignment","Streamlined Device assignment",{"path":723,"title":724},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-auto-snapshot","Device Auto Snapshots",{"path":726,"title":727},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-instance-audit-logs","Device Instance Audit Logging",{"path":729,"title":730},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-onboarding-improvements","Device Onboarding Improvements",{"path":732,"title":733},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-pricing-change","Pricing change for Devices",{"path":735,"title":736},"\u002Fchangelog\u002F2024\u002F02\u002Finstance-auto-snapshots","Instance Auto Snapshots",{"path":738,"title":739},"\u002Fchangelog\u002F2024\u002F02\u002Fpostgresql-upgrade","PostgreSQL Version update",{"path":741,"title":742},"\u002Fchangelog\u002F2024\u002F03\u002Fbearer-token-authentication","Bearer Token Authentication for Node-RED Instances",{"path":744,"title":745},"\u002Fchangelog\u002F2024\u002F03\u002Finstance-protection-mode","Instance Protection Mode",{"path":747,"title":748},"\u002Fchangelog\u002F2024\u002F03\u002Flimits-debug-payload","Configure HTTP Payload and Debug Message size",{"path":750,"title":751},"\u002Fchangelog\u002F2024\u002F03\u002Frestart-devices-remotly","Remote Device Restart",{"path":753,"title":754},"\u002Fchangelog\u002F2024\u002F04\u002Fcustom-nodes-on-devices","Custom Nodes Support on Devices",{"path":756,"title":757},"\u002Fchangelog\u002F2024\u002F04\u002Fdevice-auto-snapshot","Direct Dashboard Access",{"path":759,"title":760},"\u002Fchangelog\u002F2024\u002F04\u002Fimproving-device-groups","Improving Device Groups",{"path":762,"title":763},"\u002Fchangelog\u002F2024\u002F04\u002Fpricing-change","Pricing change Enterprise & Teams Tier",{"path":765,"title":766},"\u002Fchangelog\u002F2024\u002F04\u002Ftougher-rate-limiting","Tougher Rate Limiting on Public Routes",{"path":768,"title":769},"\u002Fchangelog\u002F2024\u002F05\u002Finstance-healthcheck","Customizing instance health-check settings",{"path":771,"title":772},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-blueprints","Blueprints added to Library",{"path":774,"title":775},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-flowviewer","Team Library - Flow Viewer",{"path":777,"title":778},"\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices","Managing Node-RED versions on Devices",{"path":780,"title":781},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements","Snapshot Improvements",{"path":783,"title":784},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements-pt3","Snapshot Upload",{"path":786,"title":784},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-upload",{"path":788,"title":789},"\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support","Running the Device Agent behind an HTTP proxy",{"path":791,"title":792},"\u002Fchangelog\u002F2024\u002F06\u002Flibrary-blueprints","Custom hostnames for your instances",{"path":794,"title":795},"\u002Fchangelog\u002F2024\u002F06\u002Fmultiline-env-vars","Multi-line Environment Variables",{"path":797,"title":798},"\u002Fchangelog\u002F2024\u002F06\u002Fsnapshot-flow-compare","Compare Snapshots flows",{"path":800,"title":801},"\u002Fchangelog\u002F2024\u002F07\u002Fapplications-search","Applications Search",{"path":803,"title":804},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-group-clear-snapshot","Device Groups Snapshots",{"path":806,"title":807},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-delete","Managing devices",{"path":809,"title":807},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-move",{"path":811,"title":812},"\u002Fchangelog\u002F2024\u002F07\u002Fedit-snapshots","Edit Snapshots",{"path":814,"title":815},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant","The FlowFuse Expert",{"path":817,"title":818},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant-json","FlowFuse Expert Writes JSON",{"path":820,"title":821},"\u002Fchangelog\u002F2024\u002F07\u002Fimmersive-editor","Immersive Editor Experience",{"path":823,"title":824},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-inbox","Notifications Inbox",{"path":826,"title":824},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-update",{"path":828,"title":829},"\u002Fchangelog\u002F2024\u002F07\u002Fpersistent-storage","Persistent Storage on FlowFuse Cloud",{"path":831,"title":832},"\u002Fchangelog\u002F2024\u002F07\u002Fsso","Single Sign On Updates",{"path":834,"title":835},"\u002Fchangelog\u002F2024\u002F08\u002Fbill-of-materials","Bill of Materials",{"path":837,"title":838},"\u002Fchangelog\u002F2024\u002F08\u002Fenterprise-license-update","Enforcing Enterprise Restrictions",{"path":840,"title":841},"\u002Fchangelog\u002F2024\u002F08\u002Fldap-sso-groups","LDAP Single Sign On Updates",{"path":843,"title":844},"\u002Fchangelog\u002F2024\u002F08\u002Fstatic-file-service-navigation-visibility","Static File Service Navigation and Visibility",{"path":846,"title":847},"\u002Fchangelog\u002F2024\u002F10\u002Fdevice-group-env-vars","Environment Variables for your Device Groups",{"path":849,"title":850},"\u002Fchangelog\u002F2024\u002F10\u002Fmqtt-service","MQTT Broker Service",{"path":852,"title":853},"\u002Fchangelog\u002F2024\u002F10\u002Fnotifications-bulk-actions","Managing Notifications",{"path":855,"title":856},"\u002Fchangelog\u002F2024\u002F10\u002Fsnapshot-download-upload-options","Snapshot Upload and Download Improvements",{"path":858,"title":497},"\u002Fchangelog\u002F2024\u002F10\u002Fversion-history-timeline",{"path":860,"title":861},"\u002Fchangelog\u002F2024\u002F11\u002Faudit-log-hierarchy","Audit logs show hierarchical events",{"path":863,"title":864},"\u002Fchangelog\u002F2024\u002F11\u002Fdevice-agent-release","Device Agent 3.0 released",{"path":866,"title":867},"\u002Fchangelog\u002F2024\u002F11\u002Fmqtt-topic-hierarchy","MQTT Topic Hierarchy view",{"path":869,"title":870},"\u002Fchangelog\u002F2024\u002F11\u002Fteam-search","Team-wide search",{"path":872,"title":873},"\u002Fchangelog\u002F2024\u002F12\u002Fdashboad-iframe","Allow Dashboards to be embedded in iFrames",{"path":875,"title":876},"\u002Fchangelog\u002F2024\u002F12\u002Fdevice-editor-cache","Device Editor Access Speed Up",{"path":878,"title":879},"\u002Fchangelog\u002F2024\u002F12\u002Fteam-bom-timeline","Team BOM and Pipeline Views",{"path":881,"title":882},"\u002Fchangelog\u002F2025\u002F01\u002Ffree-tier-onboarding","New Onboarding Tour for Free Tier Users",{"path":884,"title":885},"\u002Fchangelog\u002F2025\u002F01\u002Fhidden-env-vars","Hidden Environment Variables",{"path":887,"title":888},"\u002Fchangelog\u002F2025\u002F01\u002Fimproved-diagnostics","Improved Diagnostics",{"path":890,"title":891},"\u002Fchangelog\u002F2025\u002F01\u002Fteam-level-groups","Team level view of Groups",{"path":893,"title":894},"\u002Fchangelog\u002F2025\u002F02\u002Fadditional-device-version-history-events","New Remote Instances Version History Events",{"path":896,"title":897},"\u002Fchangelog\u002F2025\u002F02\u002Fbroker-error-feedback","Improved Broker Connection Feedback",{"path":899,"title":900},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-agent-updates","FlowFuse User Authentication on Remote Instances",{"path":902,"title":497},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-version-history-timeline",{"path":904,"title":905},"\u002Fchangelog\u002F2025\u002F02\u002Fexternal-brokers","External MQTT Brokers",{"path":907,"title":908},"\u002Fchangelog\u002F2025\u002F02\u002Fmqtt-schema-suggestions","MQTT Smart Schema Suggestions",{"path":910,"title":911},"\u002Fchangelog\u002F2025\u002F02\u002Fresend-and-extend-team-invitation-expiration","Re-send Team Invitations",{"path":913,"title":914},"\u002Fchangelog\u002F2025\u002F02\u002Fschema-docs","Personalized Schema Documentation",{"path":916,"title":917},"\u002Fchangelog\u002F2025\u002F02\u002Ftopic-hierarchy-search","Search & Filter for Topic Hierarchy List",{"path":919,"title":920},"\u002Fchangelog\u002F2025\u002F03\u002Fcontainer-tags","Changes to tags for flowfuse\u002Fnode-red",{"path":922,"title":923},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-groups","Multiple Device Groups in a pipeline",{"path":925,"title":926},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-local-login","Local Login for Remote Instances",{"path":928,"title":929},"\u002Fchangelog\u002F2025\u002F03\u002Ffree-tier","Free Tier now more accessible to all",{"path":931,"title":932},"\u002Fchangelog\u002F2025\u002F03\u002Fresource-notifications","Resource Alerts",{"path":934,"title":935},"\u002Fchangelog\u002F2025\u002F03\u002Fsnapshot-filter","Filtering Snapshots",{"path":937,"title":938},"\u002Fchangelog\u002F2025\u002F03\u002Fteam-npm-registry","NPM Package Hosting",{"path":940,"title":941},"\u002Fchangelog\u002F2025\u002F03\u002Ftopic-deletion","MQTT Topic Management",{"path":943,"title":944},"\u002Fchangelog\u002F2025\u002F04\u002Fdevice-provisioning","Remote Instance Provisioning",{"path":946,"title":947},"\u002Fchangelog\u002F2025\u002F04\u002Fgit-integration","Git Integration with Pipelines",{"path":949,"title":950},"\u002Fchangelog\u002F2025\u002F04\u002Finstance-log-browsing","Better Node-RED log handling",{"path":952,"title":953},"\u002Fchangelog\u002F2025\u002F05\u002Fimport-node-red-flows","Import Node-RED Flows During Remote Instance Setup",{"path":955,"title":956},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant","FlowFuse Expert just got smarter",{"path":958,"title":956},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant-2",{"path":960,"title":961},"\u002Fchangelog\u002F2025\u002F06\u002Fgit-integration","Pulling snapshots from Git with Pipelines",{"path":963,"title":964},"\u002Fchangelog\u002F2025\u002F06\u002Finstance-performance-memory","Memory Metrics in Instance Performance View",{"path":966,"title":967},"\u002Fchangelog\u002F2025\u002F06\u002Fnew-home-page","Introducing the New Home Page Experience",{"path":969,"title":970},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance","Team Performance Feature",{"path":972,"title":973},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance-view","Instance Performance View",{"path":975,"title":976},"\u002Fchangelog\u002F2025\u002F06\u002Fui-refresh","Navigation UI Refresh",{"path":978,"title":979},"\u002Fchangelog\u002F2025\u002F07\u002Fbrowse-node-red-flows","Browse for Node-RED Flows During Remote Instance Setup",{"path":981,"title":321},"\u002Fchangelog\u002F2025\u002F07\u002Fflowfuse-tables",{"path":983,"title":984},"\u002Fchangelog\u002F2025\u002F07\u002Fimport-blueprints","Import blueprints directly into your existing instances",{"path":986,"title":987},"\u002Fchangelog\u002F2025\u002F07\u002Fsimplified-applications-overview","Simplified Applications Page with Summary Tiles",{"path":989,"title":990},"\u002Fchangelog\u002F2025\u002F07\u002Fsmart-suggestions","Smart Suggestions",{"path":992,"title":993},"\u002Fchangelog\u002F2025\u002F07\u002Fteam-to-pro-plan-rename","Team Plan Renamed to Pro Plan",{"path":995,"title":996},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-hosted","Generate snapshot descriptions with AI",{"path":998,"title":999},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-remote","AI Snapshot Descriptions Now Work with Remote Instances",{"path":1001,"title":1002},"\u002Fchangelog\u002F2025\u002F08\u002Fdevice-performance","FlowFuse Remote Instance Performance Data",{"path":1004,"title":1005},"\u002Fchangelog\u002F2025\u002F08\u002Fdirect-sso","Direct SSO Login",{"path":1007,"title":1008},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-assistant","FlowFuse Expert documents your flows",{"path":1010,"title":1011},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-mqtt","FlowFuse MQTT",{"path":1013,"title":1014},"\u002Fchangelog\u002F2025\u002F08\u002Fhttp-cors","Configure HTTP CORS",{"path":1016,"title":1017},"\u002Fchangelog\u002F2025\u002F08\u002Fsubflow-export","Export SubFlow as Node-RED module",{"path":1019,"title":1020},"\u002Fchangelog\u002F2025\u002F08\u002Ftables-assistant","FlowFuse Tables with a little help from the Assistant",{"path":1022,"title":1023},"\u002Fchangelog\u002F2025\u002F09\u002Fexpose-saml-groups-to-dashboard","Allow SSO groups to be shared with the Node-RED Dashboard",{"path":1025,"title":1026},"\u002Fchangelog\u002F2025\u002F09\u002Finline-assist","FlowFuse Expert can help you write code",{"path":1028,"title":1029},"\u002Fchangelog\u002F2025\u002F09\u002Fretiring-flowforge-device-agent","No more @flowforge\u002Fflowforge-device-agent releases",{"path":1031,"title":1032},"\u002Fchangelog\u002F2025\u002F09\u002Frevised-instance-snapshot-ui","Streamlined Snapshot Management",{"path":1034,"title":1035},"\u002Fchangelog\u002F2025\u002F09\u002Fteam-broker-async-api","Capture Async API data from FlowFuse Team Broker",{"path":1037,"title":1038},"\u002Fchangelog\u002F2025\u002F10\u002Fapplication-level-rbac","Application-level access control for Enterprise teams",{"path":1040,"title":1041},"\u002Fchangelog\u002F2025\u002F10\u002Fbulk-device-group-assignment","Easier Access to Bulk Device Group Management",{"path":1043,"title":1044},"\u002Fchangelog\u002F2025\u002F10\u002Fduplicate-instances-across-applications","Duplicate Instances Across Different Applications",{"path":1046,"title":1047},"\u002Fchangelog\u002F2025\u002F10\u002Fimport-flows-on-instance-creation","Import flows during instance creation",{"path":1049,"title":1050},"\u002Fchangelog\u002F2025\u002F10\u002Fmcp-nodes","FlowFuse MCP Server Nodes",{"path":1052,"title":1053},"\u002Fchangelog\u002F2025\u002F10\u002Fonnx-nodes","FlowFuse AI Nodes",{"path":1055,"title":1056},"\u002Fchangelog\u002F2025\u002F10\u002Fsettings-page-device-group-management","Device Group Management from Settings Page",{"path":1058,"title":1059},"\u002Fchangelog\u002F2025\u002F11\u002Fff-expert-update","FlowFuse Expert Update",{"path":1061,"title":1062},"\u002Fchangelog\u002F2025\u002F11\u002Fminimum-nodejs-version","Node.js v20 Minimum Version Requirement",{"path":1064,"title":1065},"\u002Fchangelog\u002F2025\u002F11\u002Fsso-session","SSO control over Session life",{"path":1067,"title":1068},"\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights","FlowFuse Expert: Now with MCP-Powered Insights",{"path":1070,"title":1071},"\u002Fchangelog\u002F2025\u002F12\u002Fscheduled-maintenance","Scheduled Maintenance Mode",{"path":1073,"title":1074},"\u002Fchangelog\u002F2026\u002F01\u002Fdevice-agent-containers","Device Agent Docker Containers updated",{"path":1076,"title":1077},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-manage-palette","FlowFuse Expert: Enhanced Palette Integration",{"path":1079,"title":1080},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-nr-actions","FlowFuse Expert: Integration with Node-RED",{"path":1082,"title":1083},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-palette-queries","FlowFuse Expert: Palette Queries",{"path":1085,"title":1086},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-select-flows","FlowFuse Expert: Ask about your flows",{"path":1088,"title":1089},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-rbacs","FlowFuse Expert: MCP-Powered Insights with RBACs",{"path":1091,"title":1092},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-security","FlowFuse Expert: MCP-Powered Insights",{"path":1094,"title":1095},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options","Set Node.js Options for Remote Instances",{"path":1097,"title":1098},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context","FlowFuse Expert: Helping you make sense of your debug log",{"path":1100,"title":1101},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner","FlowFuse Expert: Never Miss an Update",{"path":1103,"title":1104},"\u002Fchangelog\u002F2026\u002F02\u002Fha-instance-rolling-restart","HA Hosted Instance Rolling Restart",{"path":1106,"title":1107},"\u002Fchangelog\u002F2026\u002F02\u002Fremote-instances-immersive-editor","Immersive Mode for Remote Instances",{"path":1109,"title":1110},"\u002Fchangelog\u002F2026\u002F02\u002Frestoring-snapshots-to-remote-instances","Restoring snapshots to developer-mode Remote Instances",{"path":1112,"title":1113},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops","Azure DevOps Pipeline support",{"path":1115,"title":1116},"\u002Fchangelog\u002F2026\u002F03\u002Fdeveloper-mode-in-immersive-editor","Developer Mode Now Accessible from the Immersive Editor",{"path":1118,"title":1119},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title","Embedded Editor Now Shows Active Tab",{"path":1121,"title":1122},"\u002Fchangelog\u002F2026\u002F03\u002Fmarch-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on March 28th, 2026",{"path":1124,"title":1125},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor","View Snapshot Details in the Immersive Editor",{"path":1127,"title":1128},"\u002Fchangelog\u002F2026\u002F04\u002Fexpert-action-links","FlowFuse expert action links",{"path":1130,"title":1131},"\u002Fchangelog\u002F2026\u002F04\u002Fhosted-instance-url-env-var","Hosted Instances know their own URL",{"path":1133,"title":390},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer",{"path":1135,"title":1136},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer","Richer snapshot comparison view",{"path":1138,"title":1139},"\u002Fchangelog\u002F2026\u002F05\u002Fai-opt-out","AI Feature Opt-Out for Teams",{"path":1141,"title":1142},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building","FlowFuse Expert Builds Your Application",{"path":1144,"title":1145},"\u002Fchangelog\u002F2026\u002F05\u002Fsingle-sso-provider","Single SSO provider for all users",{"path":1147,"title":1148},"\u002Fchangelog\u002F2026\u002F06\u002Fdark-mode","Dark Mode",{"path":1150,"title":1151},"\u002Fchangelog\u002F2026\u002F06\u002Fdevice-agent-v4-released","Device Agent v4 released",{"path":1153,"title":1154},"\u002Fchangelog\u002F2026\u002F06\u002Fgeneric-git-server-support","Connect Pipelines to Any Git Server",{"path":1156,"title":1157},"\u002Fchangelog\u002F2026\u002F06\u002Fjuly-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on July 11th, 2026",{"path":1159,"title":1160},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups","Application Roles from SSO Groups",{"path":1162,"title":1163},"\u002Fchangelog\u002F2026\u002F07\u002Fdevice-agent-onboarding","Getting started with FlowFuse straight from the terminal",{"path":1165,"title":1166},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-enhancements","FlowFuse Expert Enhancements",{"path":1168,"title":1169},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation","FlowFuse Expert Can Now Work With Your Tables",{"path":1171,"title":1172},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats","Team Scoped Personal Access Tokens",{"path":1174,"title":1175},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards","A Dedicated Home for Your Dashboards",[],1786105898852]