[{"data":1,"prerenderedAt":1129},["ShallowReactive",2],{"blog-\u002Fblog\u002F2026\u002F04\u002Fwhy-simplicity-wins-in-iiot":3,"featureCatalog":199,"changelog-titles":594,"blog-all-for-related":1128},{"id":4,"title":5,"authors":6,"body":8,"cta":170,"date":174,"description":175,"extension":176,"features":177,"image":178,"lastUpdated":177,"meta":179,"navigation":189,"path":190,"release":177,"seo":191,"sitemap":192,"stem":193,"subtitle":194,"tags":195,"tldr":197,"video":177,"__hash__":198},"blog\u002Fblog\u002F2026\u002F04\u002Fwhy-simplicity-wins-in-iiot.md","The Real Cost of Over-Engineered Industrial Systems",[7],"sumit-shinde",{"type":9,"value":10,"toc":160},"minimark",[11,18,21,24,27,32,35,40,43,46,51,54,57,62,65,68,72,75,78,81,84,87,91,94,97,100,103,106,110,113,116,119,122,125,128,132,135,148,151,154,157],[12,13,14],"p",{},[15,16,17],"strong",{},"There is a system in your facility that your best engineer knows not to touch.",[12,19,20],{},"Not because it's dangerous. Because the last time someone touched it, a three-hour troubleshooting session ended with a call to an integrator who no longer works at the company that built it. The system came back up. Nobody knows exactly what fixed it. The incident report says \"configuration restored\" and leaves it there.",[12,22,23],{},"That system was delivered on time. It passed commissioning. The project manager closed it as a success. What it delivered, along with the data integration it was scoped to provide, was a permanent dependency on knowledge that exists nowhere formally and in fewer heads every year.",[12,25,26],{},"This is what over-engineering looks like from inside a facility that didn't make bad decisions. It looks like a system that works, that everyone is quietly glad isn't their responsibility, and that will eventually fail in a way nobody can diagnose quickly. The complexity that created it didn't arrive as a mistake. It arrived as a series of reasonable choices made by people who weren't going to be there when the choices compounded.",[28,29,31],"h2",{"id":30},"what-complexity-actually-costs-you","What Complexity Actually Costs You",[12,33,34],{},"The cost shows up in three places. None of them are in the project budget.",[12,36,37],{},[15,38,39],{},"Downtime that should take minutes takes hours.",[12,41,42],{},"A simple system fails in a way that matches its architecture. A Modbus timeout is diagnosable by anyone who understands the protocol. A failure inside a multi-layer stack, where data moves through a gateway, a middleware service, a message broker, and a cloud connector before it reaches its destination, has no obvious entry point. Every layer is a candidate. Every layer requires different tooling to inspect. And while the team works through them one at a time, production waits.",[12,44,45],{},"The failure itself is often minor. The diagnostic time is what costs. And diagnostic time scales directly with architectural complexity, not with the severity of the fault.",[12,47,48],{},[15,49,50],{},"The person who understands it becomes the system.",[12,52,53],{},"Every complex system eventually concentrates its operational knowledge in one or two people. Not by design. By attrition. The team that inherited the system learned the parts they needed to. The parts nobody needed to touch, nobody learned. Over time, the person who has touched the most parts becomes the single point of failure the system never documented.",[12,55,56],{},"When that person leaves, the system doesn't fail immediately. It just becomes untouchable. Problems get worked around. Upgrades get deferred. The system runs in a state of managed risk that everyone acknowledges privately and nobody escalates formally, because escalating it means admitting how fragile something critical has become.",[12,58,59],{},[15,60,61],{},"Modernization stops at the layer nobody understands.",[12,63,64],{},"Every facility has a modernization initiative. Cloud connectivity. Real-time analytics. Unified namespace. The vocabulary changes but the ambition is consistent. What doesn't change is the conversation that happens six weeks into the scoping exercise, when the architect traces the data path and hits the layer nobody has documentation for.",[12,66,67],{},"That layer doesn't get modernized. It gets routed around. The new system gets built on top of the old one, inheriting its limitations and adding its own. The budget meant to move the facility forward ends up funding infrastructure that looks new from the outside and runs on assumptions from 2017 underneath.",[28,69,71],{"id":70},"simple-systems-outlive-sophisticated-ones","Simple Systems Outlive Sophisticated Ones",[12,73,74],{},"Industrial systems are not software products. They don't get refactored on a two-week sprint cycle. They run. For years. Sometimes decades. Through shift changes, workforce turnover, firmware updates that nobody planned for, and organizational restructures that change who owns them without changing what they do.",[12,76,77],{},"That timeline is what makes complexity so expensive in operational technology. A sophisticated architecture in a software product gets maintained by the team that built it, updated continuously, and replaced when it no longer fits. A sophisticated architecture in a plant gets handed to whoever is there three years later, maintained defensively, and never replaced, because replacement means downtime and downtime means a conversation nobody wants to have.",[12,79,80],{},"The systems that survive this timeline are not the most capable ones. They're the most understood ones. The ones where the logic is visible, the failure modes are predictable, and the next engineer can read the configuration and understand what it does without needing to call the person who wrote it.",[12,82,83],{},"That property, legibility, is not a soft preference. It's a hard operational requirement that almost never appears in a project specification and almost always determines whether a system ages well or becomes the thing nobody touches.",[12,85,86],{},"Workforce turnover alone makes the case. The average tenure of an industrial automation engineer is somewhere between three and five years. The systems they build are expected to run for fifteen to twenty. Every system will be operated, maintained, and eventually modified by people who had no part in designing it. The question is whether it was built with that reality in mind, or whether it was built to impress the people in the room on the day it was commissioned.",[28,88,90],{"id":89},"simplicity-is-an-engineering-decision","Simplicity Is an Engineering Decision",[12,92,93],{},"Consider Modbus. It has been declared obsolete for thirty years. Richer protocols have been developed, standardized, and backed by industry consortia with considerably more resources than the original Modbus specification ever had. Modbus keeps running. Not because the industry failed to move on, but because for a significant class of problems, Modbus is exactly as capable as the problem requires and no more. That match between problem and solution is not a limitation. It's the definition of good engineering.",[12,95,96],{},"The instinct is to treat simplicity as the absence of something, less capability, less sophistication, the option you choose when budget runs out or when the team isn't skilled enough to operate something better. That instinct is wrong.",[12,98,99],{},"Simplicity in engineering is not what you start with. It's what you arrive at. It's the outcome of understanding a problem well enough to know what it doesn't require. That's a harder position to reach than adding another integration layer, and it's a harder position to defend in a project meeting where the vendor is presenting a roadmap. But facilities that get there build systems that outlast the people who designed them, systems that new engineers can inherit without a month of archaeology, and that fail in ways the overnight technician can diagnose without calling anyone.",[12,101,102],{},"If you're a plant manager or engineering lead looking at your current architecture, the useful question isn't \"what could this system do.\" It's \"what does this system need to do, and what is the simplest architecture that does it reliably.\" That question doesn't produce primitive infrastructure. It produces infrastructure your whole team can own, where new requirements can be added without excavating the past, and where five years from now the design looks like a deliberate decision rather than something that just accumulated.",[12,104,105],{},"The facilities with the best operational track records made a specific tradeoff early. They accepted less capability at design time in exchange for more resilience over time. They built systems their whole team could own, not systems only their best engineer could explain. That tradeoff looks conservative in a project meeting. It looks correct every year after.",[28,107,109],{"id":108},"what-a-well-matched-architecture-actually-looks-like","What a Well-Matched Architecture Actually Looks Like",[12,111,112],{},"A well-matched architecture is not a polite term for cheap. It is not a consolation for teams that couldn't get the budget for something better. It is a specific outcome, a system where every component earns its place, the stack matches the actual problem, and the team that operates it has complete visibility into how it works and why.",[12,114,115],{},"In practice it looks like this.",[12,117,118],{},"A facility has forty legacy devices on the floor. PLCs, drives, meters, sensors, most of them speaking Modbus, some speaking older serial protocols, none of them going anywhere soon because they're running processes that haven't changed and won't change. The facility needs that data upstream: a cloud historian, a SCADA system, an analytics platform the operations team has been waiting two years to get real data into.",[12,120,121],{},"The over-engineered answer replaces the devices, or layers a complex middleware platform across all of them, or implements a protocol migration that requires specialist involvement at every stage and produces an architecture the in-house team can monitor but not truly operate.",[12,123,124],{},"The right answer puts an edge gateway between the floor and everything above it. The gateway reads Modbus from the devices that have always spoken Modbus. It normalizes the data, applies context, and publishes it upstream over MQTT or OPC UA to whatever system needs it. The field devices keep running exactly as they always have. The modern infrastructure gets clean, structured data. The in-house team owns the entire stack because the entire stack is visible and configurable without a specialist on call.",[12,126,127],{},"That is not a compromise. It is the correct answer for that problem. It connects legacy infrastructure to modern systems without introducing dependencies the team can't manage, without requiring production downtime to implement, and without creating a layer that becomes untouchable eighteen months after the integrator leaves.",[28,129,131],{"id":130},"how-flowfuse-keeps-it-simple","How FlowFuse Keeps It Simple",[12,133,134],{},"The gateway architecture described above is not a new idea. Facilities have been running edge gateways for years. The problem has never been the concept. It has been the execution: gateways that are simple to deploy and complex to manage, that work correctly in isolation and become coordination problems at scale, that solve the connectivity challenge and create a new one around visibility, consistency, and control.",[12,136,137,142,143,147],{},[138,139,141],"a",{"href":140},"\u002F","FlowFuse"," is an Industrial Application Platform built around ",[138,144,146],{"href":145},"\u002Fnode-red\u002F","Node-RED"," at the edge. The FlowFuse Device Agent connects to the devices that have always been on the floor, Modbus, MQTT, OPC UA, serial protocols, and publishes structured data upstream to whatever system needs it. The flow is visible. The logic is readable. An engineer who has never touched the system before can open it and understand what it does without documentation that may or may not exist.",[12,149,150],{},"That last part matters more than any feature list. The single most expensive property of an industrial system is whether the team that inherits it can operate it confidently. FlowFuse is designed around that property. Flows are managed centrally, deployed consistently across every edge device in the facility using DevOps Pipelines, and monitored from a single place. When something changes, DevOps Pipelines push it across every device it needs to reach, with Snapshots providing version control and rollback, not through a manual process that depends on someone remembering which devices were updated and which weren't.",[12,152,153],{},"Where teams need to build faster or debug more confidently, FlowFuse Expert, the AI built into FlowFuse and the Node-RED editor, reduces friction at the design stage, before complexity has a chance to accumulate. It works in two ways. The Chat Interface, accessible directly within the Node-RED editor, supports flow-building assistance and live operational data queries via MCP tools. The AI in Node-RED works inside the editor itself: inline code completions, flow autocomplete, a function builder, a flow explainer, JSON generation, and CSS and HTML generation for FlowFuse Dashboard. It doesn't generate complete flows from scratch, but it assists meaningfully at each step, suggesting the next node, completing a function, explaining logic that was written by someone who's no longer there. The result is less time spent on archaeology and more time spent on the work that actually moves the facility forward.",[12,155,156],{},"The result is an architecture that connects legacy infrastructure to modern systems without adding the complexity that makes those connections fragile. The Modbus devices on the floor keep running. The cloud historian, the SCADA system, the analytics platform get the data they need in the format they expect. The in-house team owns the stack end to end because the stack was designed to be owned, not just operated.",[12,158,159],{},"The system nobody wants to touch is built by engineers who won't be there to maintain it. The system the next engineer is glad to inherit is built by engineers who understood the difference. That's the decision FlowFuse is designed to support.",{"title":161,"searchDepth":162,"depth":162,"links":163},"",4,[164,166,167,168,169],{"id":30,"depth":165,"text":31},2,{"id":70,"depth":165,"text":71},{"id":89,"depth":165,"text":90},{"id":108,"depth":165,"text":109},{"id":130,"depth":165,"text":131},{"type":171,"title":172,"description":173},"contact","Build Infrastructure That Ages Well","See how FlowFuse helps facilities connect legacy devices to modern systems, simply, visibly, and without creating the next layer nobody understands.","2026-04-08","Most industrial systems don't fail because of bad technology. They fail because of too much of it. Here's what over-engineered infrastructure is actually costing your facility, and what a different decision looks like.","md",null,"\u002Fblog\u002F2026\u002F04\u002Fimages\u002Fthe-real-cost-of-overengineered-systems.png",{"keywords":180,"excerpt":181},"industrial automation, industrial system design, operational technology, edge computing, IIoT, Modbus, MQTT, OPC UA, Node-RED, FlowFuse, legacy system integration, industrial data integration, edge gateway architecture, system complexity, maintainable systems",{"type":9,"value":182},[183,187],[12,184,185],{},[15,186,17],{},[12,188,20],{},true,"\u002Fblog\u002F2026\u002F04\u002Fwhy-simplicity-wins-in-iiot",{"title":5,"description":175},{"loc":190},"blog\u002F2026\u002F04\u002Fwhy-simplicity-wins-in-iiot","When the system nobody wants to touch becomes the system everything depends on",[196],"flowfuse","Over-engineered industrial systems don't fail because of bad intentions they fail because complexity accumulates through reasonable decisions made by people who won't be there to maintain them. The systems with the best operational track records prioritize legibility over capability built to be understood by the next engineer, not just the one who designed them.","_mOPSzr2Sv9LN5LkKBBttSW-omvmbX2Dh5UOkL4CNwk",{"id":200,"extension":201,"meta":202,"sections":203,"stem":592,"__hash__":593},"featureCatalog\u002Ffeature-catalog.yml","yml",{},[204,255,356,418,495,574],{"id":205,"title":206,"features":207},"ai-automation","AI & Automation",[208,218,228,238,244,250],{"id":209,"title":210,"description":211,"docsLink":212,"changelog":213,"tiers":217},"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",[214],{"url":215,"release":216},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner\u002F","2.28",{"edge":189,"hub":189,"fleet":189},{"id":219,"title":220,"description":221,"docsLink":222,"changelog":223,"subfeature":189,"showOnPricing":226,"tiers":227},"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",[224],{"url":225,"release":216},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context\u002F",false,{"edge":189,"hub":189,"fleet":189},{"id":229,"title":230,"description":231,"docsLink":232,"changelog":233,"subfeature":189,"showOnPricing":226,"tiers":237},"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",[234],{"url":235,"release":236},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building\u002F","2.30",{"edge":189,"hub":189,"fleet":189},{"id":239,"title":240,"description":241,"docsLink":242,"subfeature":189,"beta":189,"showOnPricing":226,"tiers":243},"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":189,"hub":189,"fleet":189},{"id":245,"title":246,"description":247,"docsLink":248,"tiers":249},"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":189,"hub":189,"fleet":189},{"id":251,"title":252,"description":253,"tiers":254},"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":189,"hub":189,"fleet":189},{"id":256,"title":257,"features":258},"build","Build",[259,265,271,281,287,293,297,303,309,317,323,327,331,340,348],{"id":260,"title":261,"description":262,"docsLink":263,"tiers":264},"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":189,"hub":226,"fleet":189},{"id":266,"title":267,"description":268,"docsLink":269,"tiers":270},"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":189,"hub":189,"fleet":189},{"id":272,"title":273,"description":274,"docsLink":275,"changelog":276,"tiers":280},"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",[277],{"url":278,"release":279},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation\u002F","2.33",{"edge":189,"hub":189,"fleet":189},{"id":282,"title":283,"description":284,"docsLink":285,"tiers":286},"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":189,"hub":189,"fleet":189},{"id":288,"title":289,"description":290,"docsLink":291,"showOnPricing":226,"tiers":292},"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":189,"hub":189,"fleet":189},{"id":294,"title":295,"showOnPricing":226,"tiers":296},"static-assets","Static Assets",{"edge":189,"hub":189,"fleet":189},{"id":298,"title":299,"description":300,"docsLink":301,"tiers":302},"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":189,"hub":189,"fleet":189},{"id":304,"title":305,"description":306,"docsLink":307,"tiers":308},"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":189,"hub":189,"fleet":189},{"id":310,"title":311,"description":312,"changelog":313,"subfeature":189,"showOnPricing":226,"tiers":316},"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.",[314],{"url":315,"release":279},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards\u002F",{"edge":189,"hub":189,"fleet":189},{"id":318,"title":319,"description":320,"docsLink":321,"tiers":322},"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":189,"hub":189,"fleet":189},{"id":324,"title":325,"subfeature":189,"showOnPricing":226,"tiers":326},"blueprints-ot-apps","Blueprints - OT APPS",{"edge":189,"hub":226,"fleet":189},{"id":328,"title":329,"subfeature":189,"showOnPricing":226,"tiers":330},"blueprints-it-apps","Blueprints - IT APPS",{"edge":226,"hub":189,"fleet":226},{"id":332,"title":333,"description":334,"changelog":335,"showOnPricing":226,"tiers":339},"immersive-editor-snapshots","Snapshot Details in Immersive Editor","View and manage snapshot details directly inside the immersive editor without leaving your editing session.",[336],{"url":337,"release":338},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor\u002F","2.29",{"edge":189,"hub":189,"fleet":189},{"id":341,"title":342,"description":343,"changelog":344,"showOnPricing":226,"tiers":347},"immersive-editor-drawer","Customisable Immersive Editor Drawer","Pin, move, resize, or full-screen the immersive editor drawer. Your preferences are remembered between sessions.",[345],{"url":346,"release":236},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer\u002F",{"edge":189,"hub":189,"fleet":189},{"id":349,"title":350,"description":351,"changelog":352,"showOnPricing":226,"tiers":355},"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.",[353],{"url":354,"release":338},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title\u002F",{"edge":189,"hub":189,"fleet":189},{"id":357,"title":358,"features":359},"deploy","Deploy",[360,366,375,381,387,393,399,405,410],{"id":361,"title":362,"description":363,"docsLink":364,"tiers":365},"hosted-instances","Cloud Instances","Run Node-RED instances managed and hosted by FlowFuse.","\u002Fdocs\u002Fuser\u002Fintroduction\u002F#creating-a-node-red-instance",{"edge":189,"hub":189,"fleet":189},{"id":367,"title":368,"description":369,"docsLink":370,"changelog":371,"tiers":374},"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",[372],{"url":373,"release":216},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options\u002F",{"edge":189,"hub":226,"fleet":189},{"id":376,"title":377,"description":378,"docsLink":379,"tiers":380},"custom-hostnames","Custom Hostnames","Access your Node-RED application via your own domain name.","\u002Fdocs\u002Fuser\u002Fcustom-hostnames\u002F",{"edge":226,"hub":189,"fleet":226},{"id":382,"title":383,"description":384,"docsLink":385,"tiers":386},"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":189,"hub":226,"fleet":189},{"id":388,"title":389,"description":390,"docsLink":391,"showOnPricing":226,"tiers":392},"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":189,"hub":189,"fleet":189},{"id":394,"title":395,"description":396,"docsLink":397,"tiers":398},"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":189,"hub":189,"fleet":189},{"id":400,"title":401,"description":402,"docsLink":403,"tiers":404},"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":226,"hub":189,"fleet":226},{"id":406,"title":407,"description":408,"docsLink":403,"subfeature":189,"showOnPricing":226,"tiers":409},"git-integration-github","GitHub","Push and pull snapshots to GitHub repositories through DevOps Pipeline Git Stages.",{"edge":226,"hub":189,"fleet":226},{"id":411,"title":412,"description":413,"docsLink":403,"changelog":414,"subfeature":189,"showOnPricing":226,"tiers":417},"git-integration-azure","Azure DevOps","Push and pull snapshots to Azure DevOps repositories through DevOps Pipeline Git Stages.",[415],{"url":416,"release":338},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops\u002F",{"edge":226,"hub":189,"fleet":226},{"id":419,"title":420,"features":421},"operate-maintain","Operate & Maintain",[422,428,434,439,447,451,455,460,466,472,477,483,487,491],{"id":423,"title":424,"description":425,"docsLink":426,"tiers":427},"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":189,"hub":189,"fleet":189},{"id":429,"title":430,"description":431,"docsLink":432,"subfeature":189,"showOnPricing":226,"tiers":433},"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":189,"hub":189,"fleet":189},{"id":435,"title":436,"description":437,"docsLink":432,"subfeature":189,"showOnPricing":226,"tiers":438},"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":189,"hub":189,"fleet":189},{"id":440,"title":441,"description":442,"changelog":443,"subfeature":189,"showOnPricing":226,"tiers":446},"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.",[444],{"url":445,"release":338},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer\u002F",{"edge":189,"hub":189,"fleet":189},{"id":448,"title":449,"subfeature":189,"showOnPricing":226,"tiers":450},"version-history-timeline","Version History Timeline",{"edge":189,"hub":189,"fleet":189},{"id":452,"title":453,"tiers":454},"unlimited-workflow-executions","Unlimited Workflow Executions",{"edge":189,"hub":189,"fleet":189},{"id":456,"title":457,"description":458,"tiers":459},"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":189,"hub":226,"fleet":189},{"id":461,"title":462,"description":463,"docsLink":464,"tiers":465},"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":189,"hub":226,"fleet":189},{"id":467,"title":468,"description":469,"docsLink":470,"tiers":471},"high-availability","High Availability","Leverage horizontal scaling for reliable and scalable processing of your data through Node-RED.","\u002Fdocs\u002Fuser\u002Fhigh-availability\u002F",{"edge":226,"hub":189,"fleet":226},{"id":473,"title":474,"description":475,"tiers":476},"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":189,"hub":189,"fleet":189},{"id":478,"title":479,"description":480,"docsLink":481,"subfeature":189,"showOnPricing":226,"tiers":482},"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":189,"hub":189,"fleet":189},{"id":484,"title":485,"subfeature":189,"showOnPricing":226,"tiers":486},"email-alerts","Email Alerts",{"edge":189,"hub":189,"fleet":189},{"id":488,"title":489,"showOnPricing":226,"tiers":490},"api-debug-length-limit","API\u002FDebug Length Limit",{"edge":189,"hub":189,"fleet":189},{"id":492,"title":493,"tiers":494},"protected-instances","Protected Instances",{"edge":226,"hub":189,"fleet":226},{"id":496,"title":497,"features":498},"govern-secure","Govern and Secure",[499,508,514,520,525,531,537,543,551,557,563,569],{"id":500,"title":501,"description":502,"docsLink":503,"changelog":504,"tiers":507},"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",[505],{"url":506,"release":279},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups\u002F",{"edge":189,"hub":189,"fleet":189},{"id":509,"title":510,"description":511,"docsLink":512,"tiers":513},"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":189,"hub":189,"fleet":189},{"id":515,"title":516,"description":517,"docsLink":518,"tiers":519},"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":226,"hub":189,"fleet":189},{"id":521,"title":522,"description":523,"tiers":524},"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":189,"hub":226,"fleet":226},{"id":526,"title":527,"description":528,"docsLink":529,"tiers":530},"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":189,"hub":189,"fleet":189},{"id":532,"title":533,"description":534,"docsLink":535,"tiers":536},"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":189,"hub":189,"fleet":189},{"id":538,"title":539,"description":540,"docsLink":541,"subfeature":189,"showOnPricing":226,"tiers":542},"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":189,"hub":189,"fleet":189},{"id":544,"title":545,"description":546,"changelog":547,"subfeature":189,"showOnPricing":226,"tiers":550},"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.",[548],{"url":549,"release":279},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats\u002F",{"edge":189,"hub":189,"fleet":189},{"id":552,"title":553,"description":554,"docsLink":555,"showOnPricing":226,"tiers":556},"team-members","Team Members","Invite multiple team members to collaborate on the same Node-RED flows.","\u002Fdocs\u002Fuser\u002Fteam\u002F#teams",{"edge":189,"hub":189,"fleet":189},{"id":558,"title":559,"description":560,"docsLink":561,"showOnPricing":226,"tiers":562},"endpoint-security","Endpoint Security","Secure HTTP endpoints for hosted Node-RED instances using FlowFuse credentials.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#security",{"edge":189,"hub":189,"fleet":189},{"id":564,"title":565,"description":566,"docsLink":567,"tiers":568},"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":226,"hub":189,"fleet":226},{"id":570,"title":571,"description":572,"tiers":573},"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":226,"hub":189,"fleet":226},{"id":575,"title":576,"features":577},"support","Support",[578,583,587],{"id":579,"title":580,"docsLink":581,"tiers":582},"installation-support","Installation Support","\u002Fdocs\u002Finstall\u002Fintroduction\u002F#do-you-need-help-installation-service",{"edge":189,"hub":189,"fleet":189},{"id":584,"title":585,"showOnPricing":226,"tiers":586},"live-chat-support","Live Chat Support",{"edge":189,"hub":189,"fleet":189},{"id":588,"title":589,"docsLink":590,"tiers":591},"enterprise-support","Enterprise Support","\u002Fdocs\u002Fpremium-support\u002F",{"edge":189,"hub":189,"fleet":189},"feature-catalog","0AnkhTIPCECCwP9NmbTWP5HvRYx4FTSao4lG93-HaWM",[595,598,601,604,607,610,612,615,618,621,624,626,629,632,635,638,641,644,647,650,653,656,659,662,665,668,671,674,677,680,683,686,689,692,695,698,701,704,707,710,713,716,719,722,725,728,731,734,737,739,742,745,748,751,754,757,760,762,765,768,771,774,777,779,782,785,788,791,794,797,800,803,806,809,811,814,817,820,823,826,829,832,835,838,841,844,847,850,853,855,858,861,864,867,870,873,876,879,882,885,888,891,894,897,900,903,906,909,911,914,917,920,923,926,929,932,934,937,940,943,946,949,952,955,958,961,964,967,970,973,976,979,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,1086,1089,1092,1095,1098,1101,1104,1107,1110,1113,1116,1119,1122,1125],{"path":596,"title":597},"\u002Fchangelog\u002F2023\u002F09\u002Fcustom-node-support","Custom Node Support",{"path":599,"title":600},"\u002Fchangelog\u002F2023\u002F09\u002Fdevops-actions","DevOps Pipeline with action selection",{"path":602,"title":603},"\u002Fchangelog\u002F2023\u002F09\u002Fintroduction-enterprise-tier","Introducing the Enterprise Tier",{"path":605,"title":606},"\u002Fchangelog\u002F2023\u002F09\u002Fpipeline-api","API Endpoint for DevOps Pipeline",{"path":608,"title":609},"\u002Fchangelog\u002F2023\u002F09\u002Fsnapshots-devices","Usability improvements to Device Management",{"path":611,"title":319},"\u002Fchangelog\u002F2023\u002F10\u002Fblueprints",{"path":613,"title":614},"\u002Fchangelog\u002F2023\u002F10\u002Fcertified-nodes","Certified Nodes",{"path":616,"title":617},"\u002Fchangelog\u002F2023\u002F10\u002Fdevice-snapshot-selection","Enhanced Snapshot Selection",{"path":619,"title":620},"\u002Fchangelog\u002F2023\u002F10\u002Fpath-bug-fix","Device Agent path bug fix",{"path":622,"title":623},"\u002Fchangelog\u002F2023\u002F10\u002Fresource-alerts","Resource Monitoring in Audit Log",{"path":625,"title":510},"\u002Fchangelog\u002F2023\u002F11\u002F2fa",{"path":627,"title":628},"\u002Fchangelog\u002F2023\u002F11\u002Fdefault-editor","Device Editor enabled by default",{"path":630,"title":631},"\u002Fchangelog\u002F2023\u002F11\u002Fdevices-in-pipelines","Devices in DevOps Pipelines",{"path":633,"title":634},"\u002Fchangelog\u002F2023\u002F11\u002Fproject-nodes-devices","Project Nodes for Devices",{"path":636,"title":637},"\u002Fchangelog\u002F2023\u002F12\u002Fbilling","No Credit Card required for billing",{"path":639,"title":640},"\u002Fchangelog\u002F2023\u002F12\u002Fblueprint-selection","Blueprint Selection Update",{"path":642,"title":643},"\u002Fchangelog\u002F2023\u002F12\u002Fdevice-groups","Device Groups",{"path":645,"title":646},"\u002Fchangelog\u002F2023\u002F12\u002Femail-alerting-node-red-crash","Email Alerts for Audit Log Events",{"path":648,"title":649},"\u002Fchangelog\u002F2023\u002F12\u002Fnode-red-updated","Node-RED 3.1.3 now available",{"path":651,"title":652},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-audit-log","Introducing the Device Auditlog Feature",{"path":654,"title":655},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-groups-snapshot","Device Groups - Automatic snapshot assignment",{"path":657,"title":658},"\u002Fchangelog\u002F2024\u002F01\u002Ffleet-mode","Renaming \"Default Device Mode\" to \"Fleet Mode\"",{"path":660,"title":661},"\u002Fchangelog\u002F2024\u002F01\u002Fhelm-v2","Helm Chart v2.0",{"path":663,"title":664},"\u002Fchangelog\u002F2024\u002F01\u002Fnew-blueprints","New Blueprints added",{"path":666,"title":667},"\u002Fchangelog\u002F2024\u002F01\u002Fsecurity-updates","Security Updates",{"path":669,"title":670},"\u002Fchangelog\u002F2024\u002F01\u002Fsso-team-membership","Managing Team Membership via SSO",{"path":672,"title":673},"\u002Fchangelog\u002F2024\u002F01\u002Fstreamlined-device-assignment","Streamlined Device assignment",{"path":675,"title":676},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-auto-snapshot","Device Auto Snapshots",{"path":678,"title":679},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-instance-audit-logs","Device Instance Audit Logging",{"path":681,"title":682},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-onboarding-improvements","Device Onboarding Improvements",{"path":684,"title":685},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-pricing-change","Pricing change for Devices",{"path":687,"title":688},"\u002Fchangelog\u002F2024\u002F02\u002Finstance-auto-snapshots","Instance Auto Snapshots",{"path":690,"title":691},"\u002Fchangelog\u002F2024\u002F02\u002Fpostgresql-upgrade","PostgreSQL Version update",{"path":693,"title":694},"\u002Fchangelog\u002F2024\u002F03\u002Fbearer-token-authentication","Bearer Token Authentication for Node-RED Instances",{"path":696,"title":697},"\u002Fchangelog\u002F2024\u002F03\u002Finstance-protection-mode","Instance Protection Mode",{"path":699,"title":700},"\u002Fchangelog\u002F2024\u002F03\u002Flimits-debug-payload","Configure HTTP Payload and Debug Message size",{"path":702,"title":703},"\u002Fchangelog\u002F2024\u002F03\u002Frestart-devices-remotly","Remote Device Restart",{"path":705,"title":706},"\u002Fchangelog\u002F2024\u002F04\u002Fcustom-nodes-on-devices","Custom Nodes Support on Devices",{"path":708,"title":709},"\u002Fchangelog\u002F2024\u002F04\u002Fdevice-auto-snapshot","Direct Dashboard Access",{"path":711,"title":712},"\u002Fchangelog\u002F2024\u002F04\u002Fimproving-device-groups","Improving Device Groups",{"path":714,"title":715},"\u002Fchangelog\u002F2024\u002F04\u002Fpricing-change","Pricing change Enterprise & Teams Tier",{"path":717,"title":718},"\u002Fchangelog\u002F2024\u002F04\u002Ftougher-rate-limiting","Tougher Rate Limiting on Public Routes",{"path":720,"title":721},"\u002Fchangelog\u002F2024\u002F05\u002Finstance-healthcheck","Customizing instance health-check settings",{"path":723,"title":724},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-blueprints","Blueprints added to Library",{"path":726,"title":727},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-flowviewer","Team Library - Flow Viewer",{"path":729,"title":730},"\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices","Managing Node-RED versions on Devices",{"path":732,"title":733},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements","Snapshot Improvements",{"path":735,"title":736},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements-pt3","Snapshot Upload",{"path":738,"title":736},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-upload",{"path":740,"title":741},"\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support","Running the Device Agent behind an HTTP proxy",{"path":743,"title":744},"\u002Fchangelog\u002F2024\u002F06\u002Flibrary-blueprints","Custom hostnames for your instances",{"path":746,"title":747},"\u002Fchangelog\u002F2024\u002F06\u002Fmultiline-env-vars","Multi-line Environment Variables",{"path":749,"title":750},"\u002Fchangelog\u002F2024\u002F06\u002Fsnapshot-flow-compare","Compare Snapshots flows",{"path":752,"title":753},"\u002Fchangelog\u002F2024\u002F07\u002Fapplications-search","Applications Search",{"path":755,"title":756},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-group-clear-snapshot","Device Groups Snapshots",{"path":758,"title":759},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-delete","Managing devices",{"path":761,"title":759},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-move",{"path":763,"title":764},"\u002Fchangelog\u002F2024\u002F07\u002Fedit-snapshots","Edit Snapshots",{"path":766,"title":767},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant","The FlowFuse Expert",{"path":769,"title":770},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant-json","FlowFuse Expert Writes JSON",{"path":772,"title":773},"\u002Fchangelog\u002F2024\u002F07\u002Fimmersive-editor","Immersive Editor Experience",{"path":775,"title":776},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-inbox","Notifications Inbox",{"path":778,"title":776},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-update",{"path":780,"title":781},"\u002Fchangelog\u002F2024\u002F07\u002Fpersistent-storage","Persistent Storage on FlowFuse Cloud",{"path":783,"title":784},"\u002Fchangelog\u002F2024\u002F07\u002Fsso","Single Sign On Updates",{"path":786,"title":787},"\u002Fchangelog\u002F2024\u002F08\u002Fbill-of-materials","Bill of Materials",{"path":789,"title":790},"\u002Fchangelog\u002F2024\u002F08\u002Fenterprise-license-update","Enforcing Enterprise Restrictions",{"path":792,"title":793},"\u002Fchangelog\u002F2024\u002F08\u002Fldap-sso-groups","LDAP Single Sign On Updates",{"path":795,"title":796},"\u002Fchangelog\u002F2024\u002F08\u002Fstatic-file-service-navigation-visibility","Static File Service Navigation and Visibility",{"path":798,"title":799},"\u002Fchangelog\u002F2024\u002F10\u002Fdevice-group-env-vars","Environment Variables for your Device Groups",{"path":801,"title":802},"\u002Fchangelog\u002F2024\u002F10\u002Fmqtt-service","MQTT Broker Service",{"path":804,"title":805},"\u002Fchangelog\u002F2024\u002F10\u002Fnotifications-bulk-actions","Managing Notifications",{"path":807,"title":808},"\u002Fchangelog\u002F2024\u002F10\u002Fsnapshot-download-upload-options","Snapshot Upload and Download Improvements",{"path":810,"title":449},"\u002Fchangelog\u002F2024\u002F10\u002Fversion-history-timeline",{"path":812,"title":813},"\u002Fchangelog\u002F2024\u002F11\u002Faudit-log-hierarchy","Audit logs show hierarchical events",{"path":815,"title":816},"\u002Fchangelog\u002F2024\u002F11\u002Fdevice-agent-release","Device Agent 3.0 released",{"path":818,"title":819},"\u002Fchangelog\u002F2024\u002F11\u002Fmqtt-topic-hierarchy","MQTT Topic Hierarchy view",{"path":821,"title":822},"\u002Fchangelog\u002F2024\u002F11\u002Fteam-search","Team-wide search",{"path":824,"title":825},"\u002Fchangelog\u002F2024\u002F12\u002Fdashboad-iframe","Allow Dashboards to be embedded in iFrames",{"path":827,"title":828},"\u002Fchangelog\u002F2024\u002F12\u002Fdevice-editor-cache","Device Editor Access Speed Up",{"path":830,"title":831},"\u002Fchangelog\u002F2024\u002F12\u002Fteam-bom-timeline","Team BOM and Pipeline Views",{"path":833,"title":834},"\u002Fchangelog\u002F2025\u002F01\u002Ffree-tier-onboarding","New Onboarding Tour for Free Tier Users",{"path":836,"title":837},"\u002Fchangelog\u002F2025\u002F01\u002Fhidden-env-vars","Hidden Environment Variables",{"path":839,"title":840},"\u002Fchangelog\u002F2025\u002F01\u002Fimproved-diagnostics","Improved Diagnostics",{"path":842,"title":843},"\u002Fchangelog\u002F2025\u002F01\u002Fteam-level-groups","Team level view of Groups",{"path":845,"title":846},"\u002Fchangelog\u002F2025\u002F02\u002Fadditional-device-version-history-events","New Remote Instances Version History Events",{"path":848,"title":849},"\u002Fchangelog\u002F2025\u002F02\u002Fbroker-error-feedback","Improved Broker Connection Feedback",{"path":851,"title":852},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-agent-updates","FlowFuse User Authentication on Remote Instances",{"path":854,"title":449},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-version-history-timeline",{"path":856,"title":857},"\u002Fchangelog\u002F2025\u002F02\u002Fexternal-brokers","External MQTT Brokers",{"path":859,"title":860},"\u002Fchangelog\u002F2025\u002F02\u002Fmqtt-schema-suggestions","MQTT Smart Schema Suggestions",{"path":862,"title":863},"\u002Fchangelog\u002F2025\u002F02\u002Fresend-and-extend-team-invitation-expiration","Re-send Team Invitations",{"path":865,"title":866},"\u002Fchangelog\u002F2025\u002F02\u002Fschema-docs","Personalized Schema Documentation",{"path":868,"title":869},"\u002Fchangelog\u002F2025\u002F02\u002Ftopic-hierarchy-search","Search & Filter for Topic Hierarchy List",{"path":871,"title":872},"\u002Fchangelog\u002F2025\u002F03\u002Fcontainer-tags","Changes to tags for flowfuse\u002Fnode-red",{"path":874,"title":875},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-groups","Multiple Device Groups in a pipeline",{"path":877,"title":878},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-local-login","Local Login for Remote Instances",{"path":880,"title":881},"\u002Fchangelog\u002F2025\u002F03\u002Ffree-tier","Free Tier now more accessible to all",{"path":883,"title":884},"\u002Fchangelog\u002F2025\u002F03\u002Fresource-notifications","Resource Alerts",{"path":886,"title":887},"\u002Fchangelog\u002F2025\u002F03\u002Fsnapshot-filter","Filtering Snapshots",{"path":889,"title":890},"\u002Fchangelog\u002F2025\u002F03\u002Fteam-npm-registry","NPM Package Hosting",{"path":892,"title":893},"\u002Fchangelog\u002F2025\u002F03\u002Ftopic-deletion","MQTT Topic Management",{"path":895,"title":896},"\u002Fchangelog\u002F2025\u002F04\u002Fdevice-provisioning","Remote Instance Provisioning",{"path":898,"title":899},"\u002Fchangelog\u002F2025\u002F04\u002Fgit-integration","Git Integration with Pipelines",{"path":901,"title":902},"\u002Fchangelog\u002F2025\u002F04\u002Finstance-log-browsing","Better Node-RED log handling",{"path":904,"title":905},"\u002Fchangelog\u002F2025\u002F05\u002Fimport-node-red-flows","Import Node-RED Flows During Remote Instance Setup",{"path":907,"title":908},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant","FlowFuse Expert just got smarter",{"path":910,"title":908},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant-2",{"path":912,"title":913},"\u002Fchangelog\u002F2025\u002F06\u002Fgit-integration","Pulling snapshots from Git with Pipelines",{"path":915,"title":916},"\u002Fchangelog\u002F2025\u002F06\u002Finstance-performance-memory","Memory Metrics in Instance Performance View",{"path":918,"title":919},"\u002Fchangelog\u002F2025\u002F06\u002Fnew-home-page","Introducing the New Home Page Experience",{"path":921,"title":922},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance","Team Performance Feature",{"path":924,"title":925},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance-view","Instance Performance View",{"path":927,"title":928},"\u002Fchangelog\u002F2025\u002F06\u002Fui-refresh","Navigation UI Refresh",{"path":930,"title":931},"\u002Fchangelog\u002F2025\u002F07\u002Fbrowse-node-red-flows","Browse for Node-RED Flows During Remote Instance Setup",{"path":933,"title":273},"\u002Fchangelog\u002F2025\u002F07\u002Fflowfuse-tables",{"path":935,"title":936},"\u002Fchangelog\u002F2025\u002F07\u002Fimport-blueprints","Import blueprints directly into your existing instances",{"path":938,"title":939},"\u002Fchangelog\u002F2025\u002F07\u002Fsimplified-applications-overview","Simplified Applications Page with Summary Tiles",{"path":941,"title":942},"\u002Fchangelog\u002F2025\u002F07\u002Fsmart-suggestions","Smart Suggestions",{"path":944,"title":945},"\u002Fchangelog\u002F2025\u002F07\u002Fteam-to-pro-plan-rename","Team Plan Renamed to Pro Plan",{"path":947,"title":948},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-hosted","Generate snapshot descriptions with AI",{"path":950,"title":951},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-remote","AI Snapshot Descriptions Now Work with Remote Instances",{"path":953,"title":954},"\u002Fchangelog\u002F2025\u002F08\u002Fdevice-performance","FlowFuse Remote Instance Performance Data",{"path":956,"title":957},"\u002Fchangelog\u002F2025\u002F08\u002Fdirect-sso","Direct SSO Login",{"path":959,"title":960},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-assistant","FlowFuse Expert documents your flows",{"path":962,"title":963},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-mqtt","FlowFuse MQTT",{"path":965,"title":966},"\u002Fchangelog\u002F2025\u002F08\u002Fhttp-cors","Configure HTTP CORS",{"path":968,"title":969},"\u002Fchangelog\u002F2025\u002F08\u002Fsubflow-export","Export SubFlow as Node-RED module",{"path":971,"title":972},"\u002Fchangelog\u002F2025\u002F08\u002Ftables-assistant","FlowFuse Tables with a little help from the Assistant",{"path":974,"title":975},"\u002Fchangelog\u002F2025\u002F09\u002Fexpose-saml-groups-to-dashboard","Allow SSO groups to be shared with the Node-RED Dashboard",{"path":977,"title":978},"\u002Fchangelog\u002F2025\u002F09\u002Finline-assist","FlowFuse Expert can help you write code",{"path":980,"title":981},"\u002Fchangelog\u002F2025\u002F09\u002Fretiring-flowforge-device-agent","No more @flowforge\u002Fflowforge-device-agent releases",{"path":983,"title":984},"\u002Fchangelog\u002F2025\u002F09\u002Frevised-instance-snapshot-ui","Streamlined Snapshot Management",{"path":986,"title":987},"\u002Fchangelog\u002F2025\u002F09\u002Fteam-broker-async-api","Capture Async API data from FlowFuse Team Broker",{"path":989,"title":990},"\u002Fchangelog\u002F2025\u002F10\u002Fapplication-level-rbac","Application-level access control for Enterprise teams",{"path":992,"title":993},"\u002Fchangelog\u002F2025\u002F10\u002Fbulk-device-group-assignment","Easier Access to Bulk Device Group Management",{"path":995,"title":996},"\u002Fchangelog\u002F2025\u002F10\u002Fduplicate-instances-across-applications","Duplicate Instances Across Different Applications",{"path":998,"title":999},"\u002Fchangelog\u002F2025\u002F10\u002Fimport-flows-on-instance-creation","Import flows during instance creation",{"path":1001,"title":1002},"\u002Fchangelog\u002F2025\u002F10\u002Fmcp-nodes","FlowFuse MCP Server Nodes",{"path":1004,"title":1005},"\u002Fchangelog\u002F2025\u002F10\u002Fonnx-nodes","FlowFuse AI Nodes",{"path":1007,"title":1008},"\u002Fchangelog\u002F2025\u002F10\u002Fsettings-page-device-group-management","Device Group Management from Settings Page",{"path":1010,"title":1011},"\u002Fchangelog\u002F2025\u002F11\u002Fff-expert-update","FlowFuse Expert Update",{"path":1013,"title":1014},"\u002Fchangelog\u002F2025\u002F11\u002Fminimum-nodejs-version","Node.js v20 Minimum Version Requirement",{"path":1016,"title":1017},"\u002Fchangelog\u002F2025\u002F11\u002Fsso-session","SSO control over Session life",{"path":1019,"title":1020},"\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights","FlowFuse Expert: Now with MCP-Powered Insights",{"path":1022,"title":1023},"\u002Fchangelog\u002F2025\u002F12\u002Fscheduled-maintenance","Scheduled Maintenance Mode",{"path":1025,"title":1026},"\u002Fchangelog\u002F2026\u002F01\u002Fdevice-agent-containers","Device Agent Docker Containers updated",{"path":1028,"title":1029},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-manage-palette","FlowFuse Expert: Enhanced Palette Integration",{"path":1031,"title":1032},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-nr-actions","FlowFuse Expert: Integration with Node-RED",{"path":1034,"title":1035},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-palette-queries","FlowFuse Expert: Palette Queries",{"path":1037,"title":1038},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-select-flows","FlowFuse Expert: Ask about your flows",{"path":1040,"title":1041},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-rbacs","FlowFuse Expert: MCP-Powered Insights with RBACs",{"path":1043,"title":1044},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-security","FlowFuse Expert: MCP-Powered Insights",{"path":1046,"title":1047},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options","Set Node.js Options for Remote Instances",{"path":1049,"title":1050},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context","FlowFuse Expert: Helping you make sense of your debug log",{"path":1052,"title":1053},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner","FlowFuse Expert: Never Miss an Update",{"path":1055,"title":1056},"\u002Fchangelog\u002F2026\u002F02\u002Fha-instance-rolling-restart","HA Hosted Instance Rolling Restart",{"path":1058,"title":1059},"\u002Fchangelog\u002F2026\u002F02\u002Fremote-instances-immersive-editor","Immersive Mode for Remote Instances",{"path":1061,"title":1062},"\u002Fchangelog\u002F2026\u002F02\u002Frestoring-snapshots-to-remote-instances","Restoring snapshots to developer-mode Remote Instances",{"path":1064,"title":1065},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops","Azure DevOps Pipeline support",{"path":1067,"title":1068},"\u002Fchangelog\u002F2026\u002F03\u002Fdeveloper-mode-in-immersive-editor","Developer Mode Now Accessible from the Immersive Editor",{"path":1070,"title":1071},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title","Embedded Editor Now Shows Active Tab",{"path":1073,"title":1074},"\u002Fchangelog\u002F2026\u002F03\u002Fmarch-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on March 28th, 2026",{"path":1076,"title":1077},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor","View Snapshot Details in the Immersive Editor",{"path":1079,"title":1080},"\u002Fchangelog\u002F2026\u002F04\u002Fexpert-action-links","FlowFuse expert action links",{"path":1082,"title":1083},"\u002Fchangelog\u002F2026\u002F04\u002Fhosted-instance-url-env-var","Hosted Instances know their own URL",{"path":1085,"title":342},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer",{"path":1087,"title":1088},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer","Richer snapshot comparison view",{"path":1090,"title":1091},"\u002Fchangelog\u002F2026\u002F05\u002Fai-opt-out","AI Feature Opt-Out for Teams",{"path":1093,"title":1094},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building","FlowFuse Expert Builds Your Application",{"path":1096,"title":1097},"\u002Fchangelog\u002F2026\u002F05\u002Fsingle-sso-provider","Single SSO provider for all users",{"path":1099,"title":1100},"\u002Fchangelog\u002F2026\u002F06\u002Fdark-mode","Dark Mode",{"path":1102,"title":1103},"\u002Fchangelog\u002F2026\u002F06\u002Fdevice-agent-v4-released","Device Agent v4 released",{"path":1105,"title":1106},"\u002Fchangelog\u002F2026\u002F06\u002Fgeneric-git-server-support","Connect Pipelines to Any Git Server",{"path":1108,"title":1109},"\u002Fchangelog\u002F2026\u002F06\u002Fjuly-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on July 11th, 2026",{"path":1111,"title":1112},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups","Application Roles from SSO Groups",{"path":1114,"title":1115},"\u002Fchangelog\u002F2026\u002F07\u002Fdevice-agent-onboarding","Getting started with FlowFuse straight from the terminal",{"path":1117,"title":1118},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-enhancements","FlowFuse Expert Enhancements",{"path":1120,"title":1121},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation","FlowFuse Expert Can Now Work With Your Tables",{"path":1123,"title":1124},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats","Team Scoped Personal Access Tokens",{"path":1126,"title":1127},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards","A Dedicated Home for Your Dashboards",[],1786105900532]