[{"data":1,"prerenderedAt":1452},["ShallowReactive",2],{"blog-\u002Fblog\u002F2026\u002F03\u002Fwhy-opcua-is-not-replacing-modbus-yet":3,"featureCatalog":522,"changelog-titles":917,"blog-all-for-related":1451},{"id":4,"title":5,"authors":6,"body":8,"cta":500,"date":504,"description":505,"extension":506,"features":507,"image":508,"lastUpdated":507,"meta":509,"navigation":511,"path":512,"release":507,"seo":513,"sitemap":514,"stem":515,"subtitle":516,"tags":517,"tldr":507,"video":507,"__hash__":521},"blog\u002Fblog\u002F2026\u002F03\u002Fwhy-opcua-is-not-replacing-modbus-yet.md","Why OPC UA Is Not Replacing Modbus (Yet)",[7],"sumit-shinde",{"type":9,"value":10,"toc":487},"minimark",[11,18,23,26,35,38,50,53,58,61,64,67,285,288,292,295,298,301,346,349,352,355,359,362,365,368,371,374,378,381,384,387,390,393,396,400,403,406,409,412,415,418,422,425,428,431,434,437,440,444,447,450,453,456,459,462,465,469,472,475,478,481,484],[12,13,14],"p",{},[15,16,17],"strong",{},"Everyone in industrial automation agrees: OPC UA is the future. The specs are richer. The security is real. The semantic modeling is genuinely elegant. The industry consortia say so. The whitepapers say so. Vendors say so constantly, especially the ones selling OPC UA stacks.",[12,19,20],{},[15,21,22],{},"Modbus is still winning.",[12,24,25],{},"Not in keynotes. Not in roadmaps. On the factory floor, in new device datasheets, in RFQs sent out this quarter, Modbus keeps showing up where OPC UA was supposed to have taken over by now.",[12,27,28,29,34],{},"In January, we wrote about ",[30,31,33],"a",{"href":32},"\u002Fblog\u002F2026\u002F01\u002Fwhy-modbus-still-exist\u002F","why Modbus refuses to die",", the installed base, the zero-cost implementation, the vendor neutrality, the brutal simplicity that makes it work at 3 AM when nothing else will. That piece hit a nerve. The responses fell into two camps: engineers who nodded along because they live this every day, and architects who pushed back insisting OPC UA adoption is accelerating.",[12,36,37],{},"Both camps are right. And that's exactly the problem.",[12,39,40,41,45,46,49],{},"OPC UA isn't losing because it's a bad protocol. It's losing ground in places it should dominate because the gap between what OPC UA ",[42,43,44],"em",{},"can"," do and what most facilities ",[42,47,48],{},"need"," done remains wider than the standards bodies want to admit. Capability isn't the same as adoption. A Ferrari doesn't win in a parking lot.",[12,51,52],{},"This isn't a eulogy for OPC UA. It's a sober look at the structural reasons why a protocol with every technical advantage on paper hasn't delivered the displacement its advocates have been predicting for fifteen years, and what would actually need to change for the \"yet\" in that title to disappear.",[54,55,57],"h2",{"id":56},"the-promise-vs-the-reality","The Promise vs. The Reality",[12,59,60],{},"OPC UA was ratified in 2008. That's eighteen years ago. The pitch was compelling: a unified, secure, semantically rich protocol that would finally bring industrial automation into the modern era. The OPC Foundation had vendor backing. The specification was thorough. The vision was clear.",[12,62,63],{},"Optimistic predictions followed. The expectation in many quarters was that by the mid-2010s OPC UA would be the dominant machine-level protocol, that Modbus would be a legacy concern by 2020, and that the transition would be essentially complete by the middle of this decade. Those expectations reflected genuine enthusiasm for the protocol's capabilities, not sourced forecasts, but they shaped investment decisions and roadmaps across the industry nonetheless.",[12,65,66],{},"None of that happened.",[12,68,69,70,284],{},"The ",[30,71,75,76,283],{"href":72,"rel":73},"https:\u002F\u002Fwww.futuremarketreport.com\u002Findustry-report\u002Fmodbus-communication-module-market",[74],"nofollow","Modbus TCP market was valued at ",[77,78,81,181],"span",{"className":79},[80],"katex",[77,82,85],{"className":83},[84],"katex-mathml",[86,87,89],"math",{"xmlns":88},"http:\u002F\u002Fwww.w3.org\u002F1998\u002FMath\u002FMathML",[90,91,92,176],"semantics",{},[93,94,95,99,103,106,109,111,113,116,119,121,123,126,128,130,133,135,138,140,143,145,148,151,154,157,159,161,163,165,167,169,171,173],"mrow",{},[96,97,98],"mn",{},"1.35",[100,101,102],"mi",{},"b",[100,104,105],{},"i",[100,107,108],{},"l",[100,110,108],{},[100,112,105],{},[100,114,115],{},"o",[100,117,118],{},"n",[100,120,105],{},[100,122,118],{},[96,124,125],{},"2024",[100,127,30],{},[100,129,118],{},[100,131,132],{},"d",[100,134,105],{},[100,136,137],{},"s",[100,139,12],{},[100,141,142],{},"r",[100,144,115],{},[100,146,147],{},"j",[100,149,150],{},"e",[100,152,153],{},"c",[100,155,156],{},"t",[100,158,150],{},[100,160,132],{},[100,162,156],{},[100,164,115],{},[100,166,142],{},[100,168,150],{},[100,170,30],{},[100,172,153],{},[100,174,175],{},"h",[177,178,180],"annotation",{"encoding":179},"application\u002Fx-tex","1.35 billion in 2024 and is projected to reach ",[77,182,186],{"className":183,"ariaHidden":185},[184],"katex-html","true",[77,187,190,195,199,204,208,211,214,217,221,224,228,231,234,237,240,244,247,251,255,258,261,264,267,271,274,277,280],{"className":188},[189],"base",[77,191],{"className":192,"style":194},[193],"strut","height:0.8889em;vertical-align:-0.1944em;",[77,196,98],{"className":197},[198],"mord",[77,200,203],{"className":201},[198,202],"mathnormal","bi",[77,205,108],{"className":206,"style":207},[198,202],"margin-right:0.0197em;",[77,209,108],{"className":210,"style":207},[198,202],[77,212,105],{"className":213},[198,202],[77,215,115],{"className":216},[198,202],[77,218,220],{"className":219},[198,202],"nin",[77,222,125],{"className":223},[198],[77,225,227],{"className":226},[198,202],"an",[77,229,132],{"className":230},[198,202],[77,232,105],{"className":233},[198,202],[77,235,137],{"className":236},[198,202],[77,238,12],{"className":239},[198,202],[77,241,142],{"className":242,"style":243},[198,202],"margin-right:0.0278em;",[77,245,115],{"className":246},[198,202],[77,248,147],{"className":249,"style":250},[198,202],"margin-right:0.0572em;",[77,252,254],{"className":253},[198,202],"ec",[77,256,156],{"className":257},[198,202],[77,259,150],{"className":260},[198,202],[77,262,132],{"className":263},[198,202],[77,265,156],{"className":266},[198,202],[77,268,270],{"className":269,"style":243},[198,202],"or",[77,272,150],{"className":273},[198,202],[77,275,30],{"className":276},[198,202],[77,278,153],{"className":279},[198,202],[77,281,175],{"className":282},[198,202],"2.55 billion by 2032",". That isn't legacy drag. That's active investment. New Modbus devices are being designed, manufactured, purchased, and installed in 2026, not as fallback options, but as deliberate first choices. Meanwhile, OPC UA adoption, while genuinely growing, remains concentrated in specific layers of the automation stack: SCADA systems, MES integrations, and IT\u002FOT gateways. At the field device level, Modbus still dominates.",[12,286,287],{},"The gap between expectation and reality isn't a failure of OPC UA's design. The protocol does what it promises. The gap exists because adoption in industrial automation doesn't follow software industry timelines. A protocol doesn't win by being technically superior. It wins by becoming the path of least resistance across every layer of the ecosystem simultaneously: device manufacturers, integrators, maintenance teams, procurement departments, and plant managers all have to move together. That has never happened with OPC UA, and understanding why requires looking at each layer honestly.",[54,289,291],{"id":290},"the-complexity-tax-nobody-talks-about","The Complexity Tax Nobody Talks About",[12,293,294],{},"OPC UA's biggest competitor isn't Modbus. It's its own specification.",[12,296,297],{},"The full OPC UA specification runs across fourteen separate documents. A developer picking up Modbus for the first time can read the entire protocol specification over a weekend and ship a working implementation by Monday. A developer picking up OPC UA faces months of study before they can confidently build something production-ready.",[12,299,300],{},"This isn't an unfair criticism. It's the honest cost of doing more. Modbus reads and writes registers. OPC UA models information, manages sessions, handles subscriptions, enforces security policies, and describes data with rich metadata. That capability has a price, paid in implementation time, developer hours, and operational complexity.",[12,302,303,304,345],{},"For device manufacturers, the math is punishing. A Modbus RTU interface costs roughly ",[77,305,307,326],{"className":306},[80],[77,308,310],{"className":309},[84],[86,311,312],{"xmlns":88},[90,313,314,323],{},[93,315,316,319,321],{},[96,317,318],{},"5",[100,320,156],{},[100,322,115],{},[177,324,325],{"encoding":179},"5 to ",[77,327,329],{"className":328,"ariaHidden":185},[184],[77,330,332,336,339,342],{"className":331},[189],[77,333],{"className":334,"style":335},[193],"height:0.6444em;",[77,337,318],{"className":338},[198],[77,340,156],{"className":341},[198,202],[77,343,115],{"className":344},[198,202],"10 in silicon and a few days of firmware work. A proper OPC UA server, implemented correctly with certificate management, secure channels, and a meaningful information model, requires a capable processor, sufficient memory, and weeks of engineering time. For a sensor company shipping into a price-sensitive market, that difference doesn't show up as a line item in the spec sheet. It shows up in whether the product gets built at all.",[12,347,348],{},"Certificate management alone has quietly killed more OPC UA deployments than any technical limitation. Certificates expire. They need to be provisioned, rotated, and trusted across every client and server. In an IT environment with dedicated security teams, this is manageable. In a plant where the automation engineer also handles PLC programming, HMI design, and network troubleshooting, it becomes an ongoing burden that nobody budgeted for and nobody wants to own.",[12,350,351],{},"The OPC Foundation recognized this. Companion specifications like OPC UA FX and the Field Level Communications initiative are genuine attempts to bring the protocol closer to the field device layer. Progress is real but slow, and in the meantime, device manufacturers continue defaulting to Modbus because it ships today without a compliance checklist.",[12,353,354],{},"Complexity isn't a dealbreaker when the problem demands it. Nobody complains that OPC UA is too complex when it's modeling an entire production line in a SCADA system. The complexity tax only becomes fatal when the problem is simple and a simpler tool is sitting right there, already understood by the team, already working.",[54,356,358],{"id":357},"the-skills-gap-on-the-floor","The Skills Gap on the Floor",[12,360,361],{},"Protocols don't run themselves. People configure them, troubleshoot them, and fix them at 2 AM when production is down. And the people doing that work in most manufacturing facilities today learned Modbus, not OPC UA.",[12,363,364],{},"This isn't a generational complaint. It's a workforce reality with direct operational consequences. The automation technician who has spent fifteen years on a plant floor can read a Modbus register map the way a mechanic reads an engine. They know register 40023 on device 12 is the motor temperature. They know what value triggers an alarm. They know how to pull up a protocol analyzer and spot the problem in minutes.",[12,366,367],{},"Ask that same technician to troubleshoot an OPC UA subscription that stopped delivering updates and the confidence evaporates. Is it a certificate issue? A session timeout? A misconfigured sampling interval? A namespace problem? The diagnostic path is longer, the tooling is more complex, and the required knowledge base is fundamentally different. The problem gets escalated, production stays down longer, and the experience gets filed away as evidence that OPC UA is unreliable. The protocol isn't unreliable. The skills to operate it confidently just aren't evenly distributed yet.",[12,369,370],{},"Training helps but doesn't solve the structural problem. OPC UA expertise is concentrated in system integrators and automation vendors, not in the maintenance teams who keep plants running day to day. Facilities that have gone deep on OPC UA often find themselves dependent on a small number of people who truly understand the stack, creating exactly the kind of single point of failure that conservative plant managers spend their careers avoiding.",[12,372,373],{},"The skills gap will close eventually. Engineering curricula are adding industrial networking content. Younger engineers are entering the field with broader protocol exposure. But eventually in industrial automation means a decade, not a release cycle. The plants being designed today will be maintained by the workforce that exists today, and that workforce is fluent in Modbus in a way it simply isn't in OPC UA yet.",[54,375,377],{"id":376},"the-hardware-reality","The Hardware Reality",[12,379,380],{},"Modbus RTU was designed in 1979 for the hardware constraints of 1979, worth noting that Modbus TCP, the networked variant that dominates modern installations, didn't arrive until 1999. But the original serial protocol's frugality is what set the expectation, and the ecosystem never abandoned it.",[12,382,383],{},"A bare-minimum Modbus RTU slave implementation can run on an 8-bit microcontroller with around 10KB of flash and 1.5KB of RAM. A robust, production-grade implementation with full error handling and edge-case coverage needs more, typically several times that, but the floor is still extremely low compared to almost any alternative. Device manufacturers building sensors, meters, drives, and actuators work within tight BOM constraints where every dollar multiplies across thousands of units. Modbus fits inside the microcontroller they were already using. It adds no hardware cost and minimal firmware complexity.",[12,385,386],{},"OPC UA has a different story. A properly implemented OPC UA server needs a real processor capable of running a TCP\u002FIP stack, handling cryptographic operations, and managing runtime memory requirements. Lightweight stacks like open62541 have brought the floor down meaningfully, a constrained OPC UA server can run in under 100KB of flash with careful implementation, but that still represents a significant step up from a Modbus RTU slave, and a full-featured server with a rich information model typically requires several hundred kilobytes of RAM or more.",[12,388,389],{},"The OPC Foundation's work on OPC UA FX targets exactly this problem, aiming to bring the protocol down to devices with 256KB of flash and 64KB of RAM. That's genuine progress. It's also still an order of magnitude more resource-intensive than a minimal Modbus implementation on equivalent hardware, and FX-capable devices are only beginning to reach the market.",[12,391,392],{},"For established device categories the cost difference compounds quickly. A manufacturer selling thousands of flow meters into water treatment, oil and gas, and chemical processing isn't just buying components. They're buying tooling, certifications, and support infrastructure built around specific hardware platforms. Changing the processor family to support OPC UA means requalifying the entire product, retesting for environmental and EMC compliance, and retraining field service teams. The protocol upgrade triggers a full product redesign, and the business case rarely pencils out when the existing Modbus version is selling reliably into a market that hasn't asked for OPC UA.",[12,394,395],{},"Until OPC UA can run comfortably on the same class of hardware Modbus runs on today, at comparable cost and without requiring a platform redesign, the field device market will continue defaulting to Modbus. Not because engineers prefer old technology, but because the economics of building physical hardware into conservative industrial markets leave very little room for protocol idealism.",[54,397,399],{"id":398},"where-opc-ua-actually-wins","Where OPC UA Actually Wins",[12,401,402],{},"This isn't a one-sided argument. OPC UA dominates in specific contexts and deserves the credit it gets there. Conflating the two is how bad architecture decisions get made in both directions.",[12,404,405],{},"At the SCADA and MES layer, OPC UA is the right answer. When you need to aggregate data from hundreds of heterogeneous devices and feed it into manufacturing execution systems, historian databases, and enterprise analytics platforms, Modbus gives you registers with no context. OPC UA gives you structured, self-describing data with units, ranges, relationships, and meaning baked in. At scale, that semantic layer saves thousands of engineering hours.",[12,407,408],{},"Security requirements close the conversation quickly. The moment a system needs to be accessible from outside the plant network, Modbus is disqualified. Not because it can't be hardened with compensating controls, but because its security model is nonexistent by design. OPC UA with TLS encryption, certificate-based authentication, and role-based access control provides the foundation connected industrial systems actually need.",[12,410,411],{},"Large equipment builders and machine OEMs increasingly ship with OPC UA as the primary integration interface, for good reason. A packaging line, CNC machining center, or industrial robot is a complex asset with hundreds of meaningful data points. OPC UA companion specifications from industry groups like OMAC, EUROMAP, and the VDMA define standardized information models for entire equipment categories. A machine built to the PackML OPC UA companion spec integrates with any PackML-aware SCADA system without custom mapping work. That interoperability has real commercial value.",[12,413,414],{},"Greenfield installations with modern hardware and no legacy constraints are where arguments for Modbus at the field level are weakest. When the BOM can absorb the hardware cost and the team has OPC UA skills, there is no compelling reason to default to a register-based polling protocol from 1979.",[12,416,417],{},"The pattern is consistent. OPC UA wins where complexity is justified by the problem, where security is non-negotiable, and where people and hardware resources exist to implement it properly. Those conditions describe the upper layers of the automation stack and modern greenfield projects. They do not yet describe the majority of the field device layer, and that distinction is exactly why the \"yet\" still belongs in this article's title.",[54,419,421],{"id":420},"the-gateway-middle-ground","The Gateway Middle Ground",[12,423,424],{},"The industry didn't wait for OPC UA to win. It built a workaround and quietly made it the standard architecture.",[12,426,427],{},"Edge gateways now sit at the boundary between the field device layer and everything above it, speaking Modbus to the equipment that has always spoken Modbus and presenting OPC UA, MQTT, or REST to the systems that need structured, secure data. It isn't a temporary fix pending full OPC UA adoption. For most facilities, it is the architecture, and it works well enough that the pressure to replace Modbus at the source has largely evaporated.",[12,429,430],{},"This reflects how industrial modernization actually happens. Plants don't replace working equipment to adopt better protocols. They add intelligence at the edge and leave the field devices alone. A Modbus temperature transmitter installed in 2008 keeps transmitting exactly as it always has. The gateway reads its registers, maps the raw value to a properly typed OPC UA node with engineering units and metadata attached, and publishes it upstream. The transmitter never knows the difference. The SCADA system gets clean, contextualized data. Nobody touched the wiring.",[12,432,433],{},"The business case is straightforward. Replacing field devices across a large facility to gain native OPC UA at the source costs millions of dollars, requires production downtime, and delivers no improvement in the process being controlled. Adding an edge gateway costs thousands, takes days to deploy, and delivers the same data quality improvement. The ROI calculation ends quickly.",[12,435,436],{},"FlowFuse is built around exactly this architecture. Node-RED flows running on the edge read Modbus registers from legacy field devices, apply context and normalization, and publish structured data over MQTT or OPC UA to cloud systems, historians, and analytics platforms. The Modbus equipment keeps running. The modern data infrastructure gets what it needs. The migration happens at the connectivity layer rather than the device layer, which is the only migration path that makes economic sense for most operational facilities.",[12,438,439],{},"The gateway middle ground isn't a compromise born of failure. It's a pragmatic recognition that the automation stack has always been heterogeneous and always will be. New protocols don't replace old ones in industrial environments. They get added on top, and the translation layer between them becomes the most important piece of architecture in the building.",[54,441,443],{"id":442},"what-would-actually-accelerate-opc-ua-adoption","What Would Actually Accelerate OPC UA Adoption",[12,445,446],{},"Diagnosing why OPC UA hasn't replaced Modbus is useful. Identifying what would actually change the trajectory is more useful. Not wishlist thinking, but a realistic assessment of the specific friction points that, if addressed, would move the needle in ways that eighteen years of industry advocacy has not.",[12,448,449],{},"The most immediate lever is simplification at the implementation level. Device manufacturers make platform decisions years before products ship. Every year that lightweight OPC UA profiles remain incomplete or poorly supported by silicon vendors is another product generation that defaults to Modbus. Finalizing FX profiles, getting them supported in major embedded toolchains, and making reference implementations genuinely production-ready would lower the barrier in ways that specification documents alone cannot.",[12,451,452],{},"Certificate management needs to be solved, not documented. The current approach requires automation engineers to operate like IT security professionals in environments where that expertise simply does not exist. Automated certificate lifecycle management, built into OPC UA servers and clients by default, would remove one of the most common reasons deployments stall or fail after going live. Several vendors are working on this. It needs to become a baseline expectation, not a premium feature.",[12,454,455],{},"Open source needs to catch up. Modbus has dozens of mature, well-documented stacks across every embedded platform imaginable. OPC UA open source options have improved, open62541 in particular has become a credible foundation, but the ecosystem remains thinner and less consistent in quality and maintenance overall. A developer evaluating both protocols reaches for the option with better community support and lower risk of hitting an undocumented edge case six months before launch. Closing that gap requires sustained investment from the OPC Foundation, major vendors, and the broader industrial open source community.",[12,457,458],{},"Interoperability between vendor implementations remains more aspirational than actual. Passing certification does not guarantee seamless interoperability across every feature combination two products might use together. Tightening conformance requirements and expanding interoperability testing infrastructure would give integrators the confidence that OPC UA devices from different manufacturers actually work together reliably, the way Modbus devices have for forty years.",[12,460,461],{},"Finally, the total cost of ownership narrative needs to be addressed honestly. OPC UA advocates often present the protocol's benefits without fully accounting for implementation costs, support burden, and skills investment. Facilities that have been oversold and then struggled become skeptics who push back on the next modernization proposal. Engineers trust data and specifics. Give them that.",[12,463,464],{},"None of these changes are impossible. Some are already in progress. But progress in industrial standards moves at the pace of the least motivated stakeholder, and the least motivated stakeholders are the ones who have something that works today.",[54,466,468],{"id":467},"conclusion-the-yet-has-a-deadline-but-nobody-knows-it","Conclusion: The \"Yet\" Has a Deadline, But Nobody Knows It",[12,470,471],{},"OPC UA will win. That part isn't in dispute.",[12,473,474],{},"The semantic modeling is too useful to ignore forever. The security requirements of connected industrial systems are too real to patch around indefinitely. The demand for self-describing, context-rich data will only grow as analytics, AI, and remote operations become standard expectations. The protocol that delivers all of that is OPC UA, not Modbus.",[12,476,477],{},"But winning eventually and winning now are two entirely different things. Fieldbus was supposed to replace 4-20mA. It did, mostly, over thirty years. Industrial Ethernet was supposed to eliminate serial communication. Serial communication is still everywhere. Better technology wins in industrial automation on a timeline set by depreciation schedules, workforce transitions, and the risk tolerance of people whose primary job is keeping production running. Those timelines are measured in decades and they do not compress because a standards body publishes a roadmap.",[12,479,480],{},"The \"yet\" in this article's title has a deadline. The honest answer, based on everything the industry has demonstrated about how protocol transitions actually unfold, is that it is further away than the whitepapers suggest and closer than the Modbus installed base makes it feel.",[12,482,483],{},"Plan accordingly. Build the gateway layer. Invest in OPC UA skills before you need them urgently. Specify OPC UA where the problem justifies it today. And stop expecting the field device layer to look like the SCADA layer anytime soon.",[12,485,486],{},"Modbus will be there when you get back.",{"title":488,"searchDepth":489,"depth":489,"links":490},"",4,[491,493,494,495,496,497,498,499],{"id":56,"depth":492,"text":57},2,{"id":290,"depth":492,"text":291},{"id":357,"depth":492,"text":358},{"id":376,"depth":492,"text":377},{"id":398,"depth":492,"text":399},{"id":420,"depth":492,"text":421},{"id":442,"depth":492,"text":443},{"id":467,"depth":492,"text":468},{"type":501,"title":502,"description":503},"demo","Bridge Modbus and OPC UA Without Ripping Out Your Infrastructure","FlowFuse connects your legacy Modbus devices to modern SCADA, cloud, and analytics systems using Node-RED at the edge. No hardware replacement. No production downtime. Just the data your modern systems need from the equipment already running your plant.","2026-03-30","OPC UA has every technical advantage. Modbus is still winning. Here's why the replacement hasn't happened and what would actually change that.","md",null,"\u002Fblog\u002F2026\u002F03\u002Fimages\u002Fopcua-is-not-replacing-modbus-yet.png",{"keywords":510},"opc ua, modbus, industrial automation, protocol comparison, field devices, scada, mes, industrial protocols, gateway architecture, edge computing, node-red, mqtt, industrial security, certificate management, interoperability",true,"\u002Fblog\u002F2026\u002F03\u002Fwhy-opcua-is-not-replacing-modbus-yet",{"title":5,"description":505},{"loc":512},"blog\u002F2026\u002F03\u002Fwhy-opcua-is-not-replacing-modbus-yet","Why your next device will still ship with Modbus, and what OPC UA needs to fix before that changes",[518,519,520],"flowfuse","opcua","modbus","wHB8H3jAx3Any4qeYIbyPmGlS31dSdROyzc35bJ-Gk0",{"id":523,"extension":524,"meta":525,"sections":526,"stem":915,"__hash__":916},"featureCatalog\u002Ffeature-catalog.yml","yml",{},[527,578,679,741,818,897],{"id":528,"title":529,"features":530},"ai-automation","AI & Automation",[531,541,551,561,567,573],{"id":532,"title":533,"description":534,"docsLink":535,"changelog":536,"tiers":540},"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",[537],{"url":538,"release":539},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner\u002F","2.28",{"edge":511,"hub":511,"fleet":511},{"id":542,"title":543,"description":544,"docsLink":545,"changelog":546,"subfeature":511,"showOnPricing":549,"tiers":550},"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",[547],{"url":548,"release":539},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context\u002F",false,{"edge":511,"hub":511,"fleet":511},{"id":552,"title":553,"description":554,"docsLink":555,"changelog":556,"subfeature":511,"showOnPricing":549,"tiers":560},"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",[557],{"url":558,"release":559},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building\u002F","2.30",{"edge":511,"hub":511,"fleet":511},{"id":562,"title":563,"description":564,"docsLink":565,"subfeature":511,"beta":511,"showOnPricing":549,"tiers":566},"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":511,"hub":511,"fleet":511},{"id":568,"title":569,"description":570,"docsLink":571,"tiers":572},"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":511,"hub":511,"fleet":511},{"id":574,"title":575,"description":576,"tiers":577},"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":511,"hub":511,"fleet":511},{"id":579,"title":580,"features":581},"build","Build",[582,588,594,604,610,616,620,626,632,640,646,650,654,663,671],{"id":583,"title":584,"description":585,"docsLink":586,"tiers":587},"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":511,"hub":549,"fleet":511},{"id":589,"title":590,"description":591,"docsLink":592,"tiers":593},"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":511,"hub":511,"fleet":511},{"id":595,"title":596,"description":597,"docsLink":598,"changelog":599,"tiers":603},"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",[600],{"url":601,"release":602},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation\u002F","2.33",{"edge":511,"hub":511,"fleet":511},{"id":605,"title":606,"description":607,"docsLink":608,"tiers":609},"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":511,"hub":511,"fleet":511},{"id":611,"title":612,"description":613,"docsLink":614,"showOnPricing":549,"tiers":615},"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":511,"hub":511,"fleet":511},{"id":617,"title":618,"showOnPricing":549,"tiers":619},"static-assets","Static Assets",{"edge":511,"hub":511,"fleet":511},{"id":621,"title":622,"description":623,"docsLink":624,"tiers":625},"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":511,"hub":511,"fleet":511},{"id":627,"title":628,"description":629,"docsLink":630,"tiers":631},"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":511,"hub":511,"fleet":511},{"id":633,"title":634,"description":635,"changelog":636,"subfeature":511,"showOnPricing":549,"tiers":639},"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.",[637],{"url":638,"release":602},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards\u002F",{"edge":511,"hub":511,"fleet":511},{"id":641,"title":642,"description":643,"docsLink":644,"tiers":645},"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":511,"hub":511,"fleet":511},{"id":647,"title":648,"subfeature":511,"showOnPricing":549,"tiers":649},"blueprints-ot-apps","Blueprints - OT APPS",{"edge":511,"hub":549,"fleet":511},{"id":651,"title":652,"subfeature":511,"showOnPricing":549,"tiers":653},"blueprints-it-apps","Blueprints - IT APPS",{"edge":549,"hub":511,"fleet":549},{"id":655,"title":656,"description":657,"changelog":658,"showOnPricing":549,"tiers":662},"immersive-editor-snapshots","Snapshot Details in Immersive Editor","View and manage snapshot details directly inside the immersive editor without leaving your editing session.",[659],{"url":660,"release":661},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor\u002F","2.29",{"edge":511,"hub":511,"fleet":511},{"id":664,"title":665,"description":666,"changelog":667,"showOnPricing":549,"tiers":670},"immersive-editor-drawer","Customisable Immersive Editor Drawer","Pin, move, resize, or full-screen the immersive editor drawer. Your preferences are remembered between sessions.",[668],{"url":669,"release":559},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer\u002F",{"edge":511,"hub":511,"fleet":511},{"id":672,"title":673,"description":674,"changelog":675,"showOnPricing":549,"tiers":678},"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.",[676],{"url":677,"release":661},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title\u002F",{"edge":511,"hub":511,"fleet":511},{"id":680,"title":681,"features":682},"deploy","Deploy",[683,689,698,704,710,716,722,728,733],{"id":684,"title":685,"description":686,"docsLink":687,"tiers":688},"hosted-instances","Cloud Instances","Run Node-RED instances managed and hosted by FlowFuse.","\u002Fdocs\u002Fuser\u002Fintroduction\u002F#creating-a-node-red-instance",{"edge":511,"hub":511,"fleet":511},{"id":690,"title":691,"description":692,"docsLink":693,"changelog":694,"tiers":697},"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",[695],{"url":696,"release":539},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options\u002F",{"edge":511,"hub":549,"fleet":511},{"id":699,"title":700,"description":701,"docsLink":702,"tiers":703},"custom-hostnames","Custom Hostnames","Access your Node-RED application via your own domain name.","\u002Fdocs\u002Fuser\u002Fcustom-hostnames\u002F",{"edge":549,"hub":511,"fleet":549},{"id":705,"title":706,"description":707,"docsLink":708,"tiers":709},"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":511,"hub":549,"fleet":511},{"id":711,"title":712,"description":713,"docsLink":714,"showOnPricing":549,"tiers":715},"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":511,"hub":511,"fleet":511},{"id":717,"title":718,"description":719,"docsLink":720,"tiers":721},"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":511,"hub":511,"fleet":511},{"id":723,"title":724,"description":725,"docsLink":726,"tiers":727},"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":549,"hub":511,"fleet":549},{"id":729,"title":730,"description":731,"docsLink":726,"subfeature":511,"showOnPricing":549,"tiers":732},"git-integration-github","GitHub","Push and pull snapshots to GitHub repositories through DevOps Pipeline Git Stages.",{"edge":549,"hub":511,"fleet":549},{"id":734,"title":735,"description":736,"docsLink":726,"changelog":737,"subfeature":511,"showOnPricing":549,"tiers":740},"git-integration-azure","Azure DevOps","Push and pull snapshots to Azure DevOps repositories through DevOps Pipeline Git Stages.",[738],{"url":739,"release":661},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops\u002F",{"edge":549,"hub":511,"fleet":549},{"id":742,"title":743,"features":744},"operate-maintain","Operate & Maintain",[745,751,757,762,770,774,778,783,789,795,800,806,810,814],{"id":746,"title":747,"description":748,"docsLink":749,"tiers":750},"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":511,"hub":511,"fleet":511},{"id":752,"title":753,"description":754,"docsLink":755,"subfeature":511,"showOnPricing":549,"tiers":756},"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":511,"hub":511,"fleet":511},{"id":758,"title":759,"description":760,"docsLink":755,"subfeature":511,"showOnPricing":549,"tiers":761},"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":511,"hub":511,"fleet":511},{"id":763,"title":764,"description":765,"changelog":766,"subfeature":511,"showOnPricing":549,"tiers":769},"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.",[767],{"url":768,"release":661},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer\u002F",{"edge":511,"hub":511,"fleet":511},{"id":771,"title":772,"subfeature":511,"showOnPricing":549,"tiers":773},"version-history-timeline","Version History Timeline",{"edge":511,"hub":511,"fleet":511},{"id":775,"title":776,"tiers":777},"unlimited-workflow-executions","Unlimited Workflow Executions",{"edge":511,"hub":511,"fleet":511},{"id":779,"title":780,"description":781,"tiers":782},"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":511,"hub":549,"fleet":511},{"id":784,"title":785,"description":786,"docsLink":787,"tiers":788},"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":511,"hub":549,"fleet":511},{"id":790,"title":791,"description":792,"docsLink":793,"tiers":794},"high-availability","High Availability","Leverage horizontal scaling for reliable and scalable processing of your data through Node-RED.","\u002Fdocs\u002Fuser\u002Fhigh-availability\u002F",{"edge":549,"hub":511,"fleet":549},{"id":796,"title":797,"description":798,"tiers":799},"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":511,"hub":511,"fleet":511},{"id":801,"title":802,"description":803,"docsLink":804,"subfeature":511,"showOnPricing":549,"tiers":805},"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":511,"hub":511,"fleet":511},{"id":807,"title":808,"subfeature":511,"showOnPricing":549,"tiers":809},"email-alerts","Email Alerts",{"edge":511,"hub":511,"fleet":511},{"id":811,"title":812,"showOnPricing":549,"tiers":813},"api-debug-length-limit","API\u002FDebug Length Limit",{"edge":511,"hub":511,"fleet":511},{"id":815,"title":816,"tiers":817},"protected-instances","Protected Instances",{"edge":549,"hub":511,"fleet":549},{"id":819,"title":820,"features":821},"govern-secure","Govern and Secure",[822,831,837,843,848,854,860,866,874,880,886,892],{"id":823,"title":824,"description":825,"docsLink":826,"changelog":827,"tiers":830},"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",[828],{"url":829,"release":602},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups\u002F",{"edge":511,"hub":511,"fleet":511},{"id":832,"title":833,"description":834,"docsLink":835,"tiers":836},"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":511,"hub":511,"fleet":511},{"id":838,"title":839,"description":840,"docsLink":841,"tiers":842},"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":549,"hub":511,"fleet":511},{"id":844,"title":845,"description":846,"tiers":847},"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":511,"hub":549,"fleet":549},{"id":849,"title":850,"description":851,"docsLink":852,"tiers":853},"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":511,"hub":511,"fleet":511},{"id":855,"title":856,"description":857,"docsLink":858,"tiers":859},"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":511,"hub":511,"fleet":511},{"id":861,"title":862,"description":863,"docsLink":864,"subfeature":511,"showOnPricing":549,"tiers":865},"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":511,"hub":511,"fleet":511},{"id":867,"title":868,"description":869,"changelog":870,"subfeature":511,"showOnPricing":549,"tiers":873},"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.",[871],{"url":872,"release":602},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats\u002F",{"edge":511,"hub":511,"fleet":511},{"id":875,"title":876,"description":877,"docsLink":878,"showOnPricing":549,"tiers":879},"team-members","Team Members","Invite multiple team members to collaborate on the same Node-RED flows.","\u002Fdocs\u002Fuser\u002Fteam\u002F#teams",{"edge":511,"hub":511,"fleet":511},{"id":881,"title":882,"description":883,"docsLink":884,"showOnPricing":549,"tiers":885},"endpoint-security","Endpoint Security","Secure HTTP endpoints for hosted Node-RED instances using FlowFuse credentials.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#security",{"edge":511,"hub":511,"fleet":511},{"id":887,"title":888,"description":889,"docsLink":890,"tiers":891},"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":549,"hub":511,"fleet":549},{"id":893,"title":894,"description":895,"tiers":896},"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":549,"hub":511,"fleet":549},{"id":898,"title":899,"features":900},"support","Support",[901,906,910],{"id":902,"title":903,"docsLink":904,"tiers":905},"installation-support","Installation Support","\u002Fdocs\u002Finstall\u002Fintroduction\u002F#do-you-need-help-installation-service",{"edge":511,"hub":511,"fleet":511},{"id":907,"title":908,"showOnPricing":549,"tiers":909},"live-chat-support","Live Chat Support",{"edge":511,"hub":511,"fleet":511},{"id":911,"title":912,"docsLink":913,"tiers":914},"enterprise-support","Enterprise Support","\u002Fdocs\u002Fpremium-support\u002F",{"edge":511,"hub":511,"fleet":511},"feature-catalog","0AnkhTIPCECCwP9NmbTWP5HvRYx4FTSao4lG93-HaWM",[918,921,924,927,930,933,935,938,941,944,947,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,1062,1065,1068,1071,1074,1077,1080,1083,1085,1088,1091,1094,1097,1100,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,1176,1178,1181,1184,1187,1190,1193,1196,1199,1202,1205,1208,1211,1214,1217,1220,1223,1226,1229,1232,1234,1237,1240,1243,1246,1249,1252,1255,1257,1260,1263,1266,1269,1272,1275,1278,1281,1284,1287,1290,1293,1296,1299,1302,1305,1308,1311,1314,1317,1320,1323,1326,1329,1332,1335,1338,1341,1344,1347,1350,1353,1356,1359,1362,1365,1368,1371,1374,1377,1380,1383,1386,1389,1392,1395,1398,1401,1404,1407,1409,1412,1415,1418,1421,1424,1427,1430,1433,1436,1439,1442,1445,1448],{"path":919,"title":920},"\u002Fchangelog\u002F2023\u002F09\u002Fcustom-node-support","Custom Node Support",{"path":922,"title":923},"\u002Fchangelog\u002F2023\u002F09\u002Fdevops-actions","DevOps Pipeline with action selection",{"path":925,"title":926},"\u002Fchangelog\u002F2023\u002F09\u002Fintroduction-enterprise-tier","Introducing the Enterprise Tier",{"path":928,"title":929},"\u002Fchangelog\u002F2023\u002F09\u002Fpipeline-api","API Endpoint for DevOps Pipeline",{"path":931,"title":932},"\u002Fchangelog\u002F2023\u002F09\u002Fsnapshots-devices","Usability improvements to Device Management",{"path":934,"title":642},"\u002Fchangelog\u002F2023\u002F10\u002Fblueprints",{"path":936,"title":937},"\u002Fchangelog\u002F2023\u002F10\u002Fcertified-nodes","Certified Nodes",{"path":939,"title":940},"\u002Fchangelog\u002F2023\u002F10\u002Fdevice-snapshot-selection","Enhanced Snapshot Selection",{"path":942,"title":943},"\u002Fchangelog\u002F2023\u002F10\u002Fpath-bug-fix","Device Agent path bug fix",{"path":945,"title":946},"\u002Fchangelog\u002F2023\u002F10\u002Fresource-alerts","Resource Monitoring in Audit Log",{"path":948,"title":833},"\u002Fchangelog\u002F2023\u002F11\u002F2fa",{"path":950,"title":951},"\u002Fchangelog\u002F2023\u002F11\u002Fdefault-editor","Device Editor enabled by default",{"path":953,"title":954},"\u002Fchangelog\u002F2023\u002F11\u002Fdevices-in-pipelines","Devices in DevOps Pipelines",{"path":956,"title":957},"\u002Fchangelog\u002F2023\u002F11\u002Fproject-nodes-devices","Project Nodes for Devices",{"path":959,"title":960},"\u002Fchangelog\u002F2023\u002F12\u002Fbilling","No Credit Card required for billing",{"path":962,"title":963},"\u002Fchangelog\u002F2023\u002F12\u002Fblueprint-selection","Blueprint Selection Update",{"path":965,"title":966},"\u002Fchangelog\u002F2023\u002F12\u002Fdevice-groups","Device Groups",{"path":968,"title":969},"\u002Fchangelog\u002F2023\u002F12\u002Femail-alerting-node-red-crash","Email Alerts for Audit Log Events",{"path":971,"title":972},"\u002Fchangelog\u002F2023\u002F12\u002Fnode-red-updated","Node-RED 3.1.3 now available",{"path":974,"title":975},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-audit-log","Introducing the Device Auditlog Feature",{"path":977,"title":978},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-groups-snapshot","Device Groups - Automatic snapshot assignment",{"path":980,"title":981},"\u002Fchangelog\u002F2024\u002F01\u002Ffleet-mode","Renaming \"Default Device Mode\" to \"Fleet Mode\"",{"path":983,"title":984},"\u002Fchangelog\u002F2024\u002F01\u002Fhelm-v2","Helm Chart v2.0",{"path":986,"title":987},"\u002Fchangelog\u002F2024\u002F01\u002Fnew-blueprints","New Blueprints added",{"path":989,"title":990},"\u002Fchangelog\u002F2024\u002F01\u002Fsecurity-updates","Security Updates",{"path":992,"title":993},"\u002Fchangelog\u002F2024\u002F01\u002Fsso-team-membership","Managing Team Membership via SSO",{"path":995,"title":996},"\u002Fchangelog\u002F2024\u002F01\u002Fstreamlined-device-assignment","Streamlined Device assignment",{"path":998,"title":999},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-auto-snapshot","Device Auto Snapshots",{"path":1001,"title":1002},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-instance-audit-logs","Device Instance Audit Logging",{"path":1004,"title":1005},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-onboarding-improvements","Device Onboarding Improvements",{"path":1007,"title":1008},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-pricing-change","Pricing change for Devices",{"path":1010,"title":1011},"\u002Fchangelog\u002F2024\u002F02\u002Finstance-auto-snapshots","Instance Auto Snapshots",{"path":1013,"title":1014},"\u002Fchangelog\u002F2024\u002F02\u002Fpostgresql-upgrade","PostgreSQL Version update",{"path":1016,"title":1017},"\u002Fchangelog\u002F2024\u002F03\u002Fbearer-token-authentication","Bearer Token Authentication for Node-RED Instances",{"path":1019,"title":1020},"\u002Fchangelog\u002F2024\u002F03\u002Finstance-protection-mode","Instance Protection Mode",{"path":1022,"title":1023},"\u002Fchangelog\u002F2024\u002F03\u002Flimits-debug-payload","Configure HTTP Payload and Debug Message size",{"path":1025,"title":1026},"\u002Fchangelog\u002F2024\u002F03\u002Frestart-devices-remotly","Remote Device Restart",{"path":1028,"title":1029},"\u002Fchangelog\u002F2024\u002F04\u002Fcustom-nodes-on-devices","Custom Nodes Support on Devices",{"path":1031,"title":1032},"\u002Fchangelog\u002F2024\u002F04\u002Fdevice-auto-snapshot","Direct Dashboard Access",{"path":1034,"title":1035},"\u002Fchangelog\u002F2024\u002F04\u002Fimproving-device-groups","Improving Device Groups",{"path":1037,"title":1038},"\u002Fchangelog\u002F2024\u002F04\u002Fpricing-change","Pricing change Enterprise & Teams Tier",{"path":1040,"title":1041},"\u002Fchangelog\u002F2024\u002F04\u002Ftougher-rate-limiting","Tougher Rate Limiting on Public Routes",{"path":1043,"title":1044},"\u002Fchangelog\u002F2024\u002F05\u002Finstance-healthcheck","Customizing instance health-check settings",{"path":1046,"title":1047},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-blueprints","Blueprints added to Library",{"path":1049,"title":1050},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-flowviewer","Team Library - Flow Viewer",{"path":1052,"title":1053},"\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices","Managing Node-RED versions on Devices",{"path":1055,"title":1056},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements","Snapshot Improvements",{"path":1058,"title":1059},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements-pt3","Snapshot Upload",{"path":1061,"title":1059},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-upload",{"path":1063,"title":1064},"\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support","Running the Device Agent behind an HTTP proxy",{"path":1066,"title":1067},"\u002Fchangelog\u002F2024\u002F06\u002Flibrary-blueprints","Custom hostnames for your instances",{"path":1069,"title":1070},"\u002Fchangelog\u002F2024\u002F06\u002Fmultiline-env-vars","Multi-line Environment Variables",{"path":1072,"title":1073},"\u002Fchangelog\u002F2024\u002F06\u002Fsnapshot-flow-compare","Compare Snapshots flows",{"path":1075,"title":1076},"\u002Fchangelog\u002F2024\u002F07\u002Fapplications-search","Applications Search",{"path":1078,"title":1079},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-group-clear-snapshot","Device Groups Snapshots",{"path":1081,"title":1082},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-delete","Managing devices",{"path":1084,"title":1082},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-move",{"path":1086,"title":1087},"\u002Fchangelog\u002F2024\u002F07\u002Fedit-snapshots","Edit Snapshots",{"path":1089,"title":1090},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant","The FlowFuse Expert",{"path":1092,"title":1093},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant-json","FlowFuse Expert Writes JSON",{"path":1095,"title":1096},"\u002Fchangelog\u002F2024\u002F07\u002Fimmersive-editor","Immersive Editor Experience",{"path":1098,"title":1099},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-inbox","Notifications Inbox",{"path":1101,"title":1099},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-update",{"path":1103,"title":1104},"\u002Fchangelog\u002F2024\u002F07\u002Fpersistent-storage","Persistent Storage on FlowFuse Cloud",{"path":1106,"title":1107},"\u002Fchangelog\u002F2024\u002F07\u002Fsso","Single Sign On Updates",{"path":1109,"title":1110},"\u002Fchangelog\u002F2024\u002F08\u002Fbill-of-materials","Bill of Materials",{"path":1112,"title":1113},"\u002Fchangelog\u002F2024\u002F08\u002Fenterprise-license-update","Enforcing Enterprise Restrictions",{"path":1115,"title":1116},"\u002Fchangelog\u002F2024\u002F08\u002Fldap-sso-groups","LDAP Single Sign On Updates",{"path":1118,"title":1119},"\u002Fchangelog\u002F2024\u002F08\u002Fstatic-file-service-navigation-visibility","Static File Service Navigation and Visibility",{"path":1121,"title":1122},"\u002Fchangelog\u002F2024\u002F10\u002Fdevice-group-env-vars","Environment Variables for your Device Groups",{"path":1124,"title":1125},"\u002Fchangelog\u002F2024\u002F10\u002Fmqtt-service","MQTT Broker Service",{"path":1127,"title":1128},"\u002Fchangelog\u002F2024\u002F10\u002Fnotifications-bulk-actions","Managing Notifications",{"path":1130,"title":1131},"\u002Fchangelog\u002F2024\u002F10\u002Fsnapshot-download-upload-options","Snapshot Upload and Download Improvements",{"path":1133,"title":772},"\u002Fchangelog\u002F2024\u002F10\u002Fversion-history-timeline",{"path":1135,"title":1136},"\u002Fchangelog\u002F2024\u002F11\u002Faudit-log-hierarchy","Audit logs show hierarchical events",{"path":1138,"title":1139},"\u002Fchangelog\u002F2024\u002F11\u002Fdevice-agent-release","Device Agent 3.0 released",{"path":1141,"title":1142},"\u002Fchangelog\u002F2024\u002F11\u002Fmqtt-topic-hierarchy","MQTT Topic Hierarchy view",{"path":1144,"title":1145},"\u002Fchangelog\u002F2024\u002F11\u002Fteam-search","Team-wide search",{"path":1147,"title":1148},"\u002Fchangelog\u002F2024\u002F12\u002Fdashboad-iframe","Allow Dashboards to be embedded in iFrames",{"path":1150,"title":1151},"\u002Fchangelog\u002F2024\u002F12\u002Fdevice-editor-cache","Device Editor Access Speed Up",{"path":1153,"title":1154},"\u002Fchangelog\u002F2024\u002F12\u002Fteam-bom-timeline","Team BOM and Pipeline Views",{"path":1156,"title":1157},"\u002Fchangelog\u002F2025\u002F01\u002Ffree-tier-onboarding","New Onboarding Tour for Free Tier Users",{"path":1159,"title":1160},"\u002Fchangelog\u002F2025\u002F01\u002Fhidden-env-vars","Hidden Environment Variables",{"path":1162,"title":1163},"\u002Fchangelog\u002F2025\u002F01\u002Fimproved-diagnostics","Improved Diagnostics",{"path":1165,"title":1166},"\u002Fchangelog\u002F2025\u002F01\u002Fteam-level-groups","Team level view of Groups",{"path":1168,"title":1169},"\u002Fchangelog\u002F2025\u002F02\u002Fadditional-device-version-history-events","New Remote Instances Version History Events",{"path":1171,"title":1172},"\u002Fchangelog\u002F2025\u002F02\u002Fbroker-error-feedback","Improved Broker Connection Feedback",{"path":1174,"title":1175},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-agent-updates","FlowFuse User Authentication on Remote Instances",{"path":1177,"title":772},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-version-history-timeline",{"path":1179,"title":1180},"\u002Fchangelog\u002F2025\u002F02\u002Fexternal-brokers","External MQTT Brokers",{"path":1182,"title":1183},"\u002Fchangelog\u002F2025\u002F02\u002Fmqtt-schema-suggestions","MQTT Smart Schema Suggestions",{"path":1185,"title":1186},"\u002Fchangelog\u002F2025\u002F02\u002Fresend-and-extend-team-invitation-expiration","Re-send Team Invitations",{"path":1188,"title":1189},"\u002Fchangelog\u002F2025\u002F02\u002Fschema-docs","Personalized Schema Documentation",{"path":1191,"title":1192},"\u002Fchangelog\u002F2025\u002F02\u002Ftopic-hierarchy-search","Search & Filter for Topic Hierarchy List",{"path":1194,"title":1195},"\u002Fchangelog\u002F2025\u002F03\u002Fcontainer-tags","Changes to tags for flowfuse\u002Fnode-red",{"path":1197,"title":1198},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-groups","Multiple Device Groups in a pipeline",{"path":1200,"title":1201},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-local-login","Local Login for Remote Instances",{"path":1203,"title":1204},"\u002Fchangelog\u002F2025\u002F03\u002Ffree-tier","Free Tier now more accessible to all",{"path":1206,"title":1207},"\u002Fchangelog\u002F2025\u002F03\u002Fresource-notifications","Resource Alerts",{"path":1209,"title":1210},"\u002Fchangelog\u002F2025\u002F03\u002Fsnapshot-filter","Filtering Snapshots",{"path":1212,"title":1213},"\u002Fchangelog\u002F2025\u002F03\u002Fteam-npm-registry","NPM Package Hosting",{"path":1215,"title":1216},"\u002Fchangelog\u002F2025\u002F03\u002Ftopic-deletion","MQTT Topic Management",{"path":1218,"title":1219},"\u002Fchangelog\u002F2025\u002F04\u002Fdevice-provisioning","Remote Instance Provisioning",{"path":1221,"title":1222},"\u002Fchangelog\u002F2025\u002F04\u002Fgit-integration","Git Integration with Pipelines",{"path":1224,"title":1225},"\u002Fchangelog\u002F2025\u002F04\u002Finstance-log-browsing","Better Node-RED log handling",{"path":1227,"title":1228},"\u002Fchangelog\u002F2025\u002F05\u002Fimport-node-red-flows","Import Node-RED Flows During Remote Instance Setup",{"path":1230,"title":1231},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant","FlowFuse Expert just got smarter",{"path":1233,"title":1231},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant-2",{"path":1235,"title":1236},"\u002Fchangelog\u002F2025\u002F06\u002Fgit-integration","Pulling snapshots from Git with Pipelines",{"path":1238,"title":1239},"\u002Fchangelog\u002F2025\u002F06\u002Finstance-performance-memory","Memory Metrics in Instance Performance View",{"path":1241,"title":1242},"\u002Fchangelog\u002F2025\u002F06\u002Fnew-home-page","Introducing the New Home Page Experience",{"path":1244,"title":1245},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance","Team Performance Feature",{"path":1247,"title":1248},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance-view","Instance Performance View",{"path":1250,"title":1251},"\u002Fchangelog\u002F2025\u002F06\u002Fui-refresh","Navigation UI Refresh",{"path":1253,"title":1254},"\u002Fchangelog\u002F2025\u002F07\u002Fbrowse-node-red-flows","Browse for Node-RED Flows During Remote Instance Setup",{"path":1256,"title":596},"\u002Fchangelog\u002F2025\u002F07\u002Fflowfuse-tables",{"path":1258,"title":1259},"\u002Fchangelog\u002F2025\u002F07\u002Fimport-blueprints","Import blueprints directly into your existing instances",{"path":1261,"title":1262},"\u002Fchangelog\u002F2025\u002F07\u002Fsimplified-applications-overview","Simplified Applications Page with Summary Tiles",{"path":1264,"title":1265},"\u002Fchangelog\u002F2025\u002F07\u002Fsmart-suggestions","Smart Suggestions",{"path":1267,"title":1268},"\u002Fchangelog\u002F2025\u002F07\u002Fteam-to-pro-plan-rename","Team Plan Renamed to Pro Plan",{"path":1270,"title":1271},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-hosted","Generate snapshot descriptions with AI",{"path":1273,"title":1274},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-remote","AI Snapshot Descriptions Now Work with Remote Instances",{"path":1276,"title":1277},"\u002Fchangelog\u002F2025\u002F08\u002Fdevice-performance","FlowFuse Remote Instance Performance Data",{"path":1279,"title":1280},"\u002Fchangelog\u002F2025\u002F08\u002Fdirect-sso","Direct SSO Login",{"path":1282,"title":1283},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-assistant","FlowFuse Expert documents your flows",{"path":1285,"title":1286},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-mqtt","FlowFuse MQTT",{"path":1288,"title":1289},"\u002Fchangelog\u002F2025\u002F08\u002Fhttp-cors","Configure HTTP CORS",{"path":1291,"title":1292},"\u002Fchangelog\u002F2025\u002F08\u002Fsubflow-export","Export SubFlow as Node-RED module",{"path":1294,"title":1295},"\u002Fchangelog\u002F2025\u002F08\u002Ftables-assistant","FlowFuse Tables with a little help from the Assistant",{"path":1297,"title":1298},"\u002Fchangelog\u002F2025\u002F09\u002Fexpose-saml-groups-to-dashboard","Allow SSO groups to be shared with the Node-RED Dashboard",{"path":1300,"title":1301},"\u002Fchangelog\u002F2025\u002F09\u002Finline-assist","FlowFuse Expert can help you write code",{"path":1303,"title":1304},"\u002Fchangelog\u002F2025\u002F09\u002Fretiring-flowforge-device-agent","No more @flowforge\u002Fflowforge-device-agent releases",{"path":1306,"title":1307},"\u002Fchangelog\u002F2025\u002F09\u002Frevised-instance-snapshot-ui","Streamlined Snapshot Management",{"path":1309,"title":1310},"\u002Fchangelog\u002F2025\u002F09\u002Fteam-broker-async-api","Capture Async API data from FlowFuse Team Broker",{"path":1312,"title":1313},"\u002Fchangelog\u002F2025\u002F10\u002Fapplication-level-rbac","Application-level access control for Enterprise teams",{"path":1315,"title":1316},"\u002Fchangelog\u002F2025\u002F10\u002Fbulk-device-group-assignment","Easier Access to Bulk Device Group Management",{"path":1318,"title":1319},"\u002Fchangelog\u002F2025\u002F10\u002Fduplicate-instances-across-applications","Duplicate Instances Across Different Applications",{"path":1321,"title":1322},"\u002Fchangelog\u002F2025\u002F10\u002Fimport-flows-on-instance-creation","Import flows during instance creation",{"path":1324,"title":1325},"\u002Fchangelog\u002F2025\u002F10\u002Fmcp-nodes","FlowFuse MCP Server Nodes",{"path":1327,"title":1328},"\u002Fchangelog\u002F2025\u002F10\u002Fonnx-nodes","FlowFuse AI Nodes",{"path":1330,"title":1331},"\u002Fchangelog\u002F2025\u002F10\u002Fsettings-page-device-group-management","Device Group Management from Settings Page",{"path":1333,"title":1334},"\u002Fchangelog\u002F2025\u002F11\u002Fff-expert-update","FlowFuse Expert Update",{"path":1336,"title":1337},"\u002Fchangelog\u002F2025\u002F11\u002Fminimum-nodejs-version","Node.js v20 Minimum Version Requirement",{"path":1339,"title":1340},"\u002Fchangelog\u002F2025\u002F11\u002Fsso-session","SSO control over Session life",{"path":1342,"title":1343},"\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights","FlowFuse Expert: Now with MCP-Powered Insights",{"path":1345,"title":1346},"\u002Fchangelog\u002F2025\u002F12\u002Fscheduled-maintenance","Scheduled Maintenance Mode",{"path":1348,"title":1349},"\u002Fchangelog\u002F2026\u002F01\u002Fdevice-agent-containers","Device Agent Docker Containers updated",{"path":1351,"title":1352},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-manage-palette","FlowFuse Expert: Enhanced Palette Integration",{"path":1354,"title":1355},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-nr-actions","FlowFuse Expert: Integration with Node-RED",{"path":1357,"title":1358},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-palette-queries","FlowFuse Expert: Palette Queries",{"path":1360,"title":1361},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-select-flows","FlowFuse Expert: Ask about your flows",{"path":1363,"title":1364},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-rbacs","FlowFuse Expert: MCP-Powered Insights with RBACs",{"path":1366,"title":1367},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-security","FlowFuse Expert: MCP-Powered Insights",{"path":1369,"title":1370},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options","Set Node.js Options for Remote Instances",{"path":1372,"title":1373},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context","FlowFuse Expert: Helping you make sense of your debug log",{"path":1375,"title":1376},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner","FlowFuse Expert: Never Miss an Update",{"path":1378,"title":1379},"\u002Fchangelog\u002F2026\u002F02\u002Fha-instance-rolling-restart","HA Hosted Instance Rolling Restart",{"path":1381,"title":1382},"\u002Fchangelog\u002F2026\u002F02\u002Fremote-instances-immersive-editor","Immersive Mode for Remote Instances",{"path":1384,"title":1385},"\u002Fchangelog\u002F2026\u002F02\u002Frestoring-snapshots-to-remote-instances","Restoring snapshots to developer-mode Remote Instances",{"path":1387,"title":1388},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops","Azure DevOps Pipeline support",{"path":1390,"title":1391},"\u002Fchangelog\u002F2026\u002F03\u002Fdeveloper-mode-in-immersive-editor","Developer Mode Now Accessible from the Immersive Editor",{"path":1393,"title":1394},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title","Embedded Editor Now Shows Active Tab",{"path":1396,"title":1397},"\u002Fchangelog\u002F2026\u002F03\u002Fmarch-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on March 28th, 2026",{"path":1399,"title":1400},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor","View Snapshot Details in the Immersive Editor",{"path":1402,"title":1403},"\u002Fchangelog\u002F2026\u002F04\u002Fexpert-action-links","FlowFuse expert action links",{"path":1405,"title":1406},"\u002Fchangelog\u002F2026\u002F04\u002Fhosted-instance-url-env-var","Hosted Instances know their own URL",{"path":1408,"title":665},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer",{"path":1410,"title":1411},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer","Richer snapshot comparison view",{"path":1413,"title":1414},"\u002Fchangelog\u002F2026\u002F05\u002Fai-opt-out","AI Feature Opt-Out for Teams",{"path":1416,"title":1417},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building","FlowFuse Expert Builds Your Application",{"path":1419,"title":1420},"\u002Fchangelog\u002F2026\u002F05\u002Fsingle-sso-provider","Single SSO provider for all users",{"path":1422,"title":1423},"\u002Fchangelog\u002F2026\u002F06\u002Fdark-mode","Dark Mode",{"path":1425,"title":1426},"\u002Fchangelog\u002F2026\u002F06\u002Fdevice-agent-v4-released","Device Agent v4 released",{"path":1428,"title":1429},"\u002Fchangelog\u002F2026\u002F06\u002Fgeneric-git-server-support","Connect Pipelines to Any Git Server",{"path":1431,"title":1432},"\u002Fchangelog\u002F2026\u002F06\u002Fjuly-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on July 11th, 2026",{"path":1434,"title":1435},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups","Application Roles from SSO Groups",{"path":1437,"title":1438},"\u002Fchangelog\u002F2026\u002F07\u002Fdevice-agent-onboarding","Getting started with FlowFuse straight from the terminal",{"path":1440,"title":1441},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-enhancements","FlowFuse Expert Enhancements",{"path":1443,"title":1444},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation","FlowFuse Expert Can Now Work With Your Tables",{"path":1446,"title":1447},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats","Team Scoped Personal Access Tokens",{"path":1449,"title":1450},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards","A Dedicated Home for Your Dashboards",[],1786105900228]