[{"data":1,"prerenderedAt":1330},["ShallowReactive",2],{"blog-\u002Fblog\u002F2026\u002F06\u002Fmqtt-vs-sparkplug-b":3,"featureCatalog":400,"changelog-titles":795,"blog-all-for-related":1329},{"id":4,"title":5,"authors":6,"body":8,"cta":373,"date":377,"description":378,"extension":379,"features":380,"image":381,"lastUpdated":380,"meta":382,"navigation":388,"path":389,"release":380,"seo":390,"sitemap":391,"stem":392,"subtitle":393,"tags":394,"tldr":398,"video":380,"__hash__":399},"blog\u002Fblog\u002F2026\u002F06\u002Fmqtt-vs-sparkplug-b.md","MQTT vs Sparkplug B: Which One (or Both) Do You Need?",[7],"sumit-shinde",{"type":9,"value":10,"toc":361},"minimark",[11,15,27,30,33,38,148,151,155,158,161,165,176,182,185,192,209,214,225,228,231,235,244,251,265,268,271,275,278,287,290,294,297,338,342,345,348],[12,13,14],"p",{},"MQTT is everywhere in industrial setups. It has been the default for moving sensor data and machine states around for a long time now, mostly because it's lightweight and it just works on almost anything.",[12,16,17,18,22,23,26],{},"The catch is that it doesn't really tell you anything about the data itself. Say a broker gets a message on ",[19,20,21],"code",{},"plant1\u002Fline4\u002Ftemp"," with a value of ",[19,24,25],{},"72",". Is that Celsius? Fahrenheit? Is the device still running, or did it go offline a few hours ago and that's just the last number it sent? MQTT won't tell you. It moves the bytes and the rest is up to you, which means everyone ends up handling it their own way.",[12,28,29],{},"That's the problem Sparkplug B tries to solve. It adds the structure that plain MQTT leaves out, so your data actually makes sense to something like a SCADA system without you having to write custom code for every device.",[12,31,32],{},"So do you need one, the other, or both? That's what this post is about.",[34,35,37],"h2",{"id":36},"mqtt-vs-sparkplug-b-at-a-glance","MQTT vs Sparkplug B at a glance",[39,40,41,56],"table",{},[42,43,44],"thead",{},[45,46,47,50,53],"tr",{},[48,49],"th",{},[48,51,52],{},"Plain MQTT",[48,54,55],{},"Sparkplug B",[57,58,59,71,82,93,104,115,126,137],"tbody",{},[45,60,61,65,68],{},[62,63,64],"td",{},"What it is",[62,66,67],{},"A lightweight transport for moving messages",[62,69,70],{},"A specification layered on top of MQTT",[45,72,73,76,79],{},[62,74,75],{},"Topic structure",[62,77,78],{},"You define your own",[62,80,81],{},"Fixed, standardized namespace",[45,83,84,87,90],{},[62,85,86],{},"Payload format",[62,88,89],{},"Anything you want, usually JSON",[62,91,92],{},"Binary Protocol Buffers, defined schema",[45,94,95,98,101],{},[62,96,97],{},"Device state",[62,99,100],{},"Not built in; roll your own heartbeat",[62,102,103],{},"Birth and death certificates out of the box",[45,105,106,109,112],{},[62,107,108],{},"Bandwidth",[62,110,111],{},"Heavier, especially with JSON",[62,113,114],{},"Compact; report-by-exception cuts traffic sharply",[45,116,117,120,123],{},[62,118,119],{},"Delivery guarantee",[62,121,122],{},"Pick your QoS: 0, 1, or 2",[62,124,125],{},"QoS 0 for all data and lifecycle messages (\"fire and forget\"); host STATE uses QoS 1",[45,127,128,131,134],{},[62,129,130],{},"Readable on the wire",[62,132,133],{},"Yes, if you use JSON",[62,135,136],{},"No, needs tooling to decode",[45,138,139,142,145],{},[62,140,141],{},"Best fit",[62,143,144],{},"Small or custom setups, data you can't lose",[62,146,147],{},"Many devices, multiple vendors, SCADA and analytics",[12,149,150],{},"The rest of this post unpacks why each row lands where it does.",[34,152,154],{"id":153},"a-pattern-that-repeats","A pattern that repeats",[12,156,157],{},"There's a story that plays out on a lot of teams, and in my experience it goes roughly the same way every time.",[12,159,160],{},"A team starts with plain MQTT because it's the obvious choice. A handful of PLCs and sensors, JSON payloads, a broker like Mosquitto in the middle, and a dashboard reading off it. It works. Then the system grows, more lines, a second site, new people, and as it grows it starts to strain in three specific places. Those three places are worth walking through, because they're the same three gaps almost everyone hits, and they're exactly what Sparkplug B was designed to close.",[34,162,164],{"id":163},"where-plain-mqtt-starts-to-hurt","Where plain MQTT starts to hurt",[12,166,167,168,175],{},"It's worth hearing this from the person who built it. ",[169,170,174],"a",{"href":171,"rel":172},"https:\u002F\u002Felement8.co.za\u002FResources\u002Farlen-nipper-co-inventor-of-mqtt-shares-his-incredible-journey-and-his-vision-for-iiot\u002F",[173],"nofollow","Arlen Nipper"," co-invented MQTT and later wrote the Sparkplug specification, and he's blunt about the trade-off at the heart of the protocol:",[177,178,179],"blockquote",{},[12,180,181],{},"Both the good and the bad thing about MQTT is, you can publish anything you want on any topic.",[12,183,184],{},"That freedom is why MQTT spread, and it's also where the strain comes from once you scale. It tends to show up in three specific places.",[12,186,187,188,191],{},"The first strain is payload bloat. JSON is easy to read, which is why people reach for it, but it isn't efficient. A single temperature reading written as ",[19,189,190],{},"{\"sensorId\":32,\"sensorValue\":24.5}"," is around 36 bytes when the actual data is a handful. That feels like nothing until you're pushing thousands of tags a second, and then it adds up fast.",[12,193,194,195,198,199,202,203,208],{},"The second is structure, or the lack of it. MQTT doesn't define any topic layout, so every integration team invents its own conventions. One group publishes temperature to ",[19,196,197],{},"line2\u002Ftemp",", another to ",[19,200,201],{},"plant\u002Fline5\u002Fsensors\u002Ftemperature\u002Fvalue",", and a contractor wires up something nobody can explain later. ",[169,204,207],{"href":205,"rel":206},"https:\u002F\u002Fwww.eclipse.org\u002Fcommunity\u002Feclipse_newsletter\u002F2021\u002Ffebruary\u002F1.php",[173],"Walker Reynolds",", the systems integrator who popularized the Unified Namespace idea, summed up the trade-off:",[177,210,211],{},[12,212,213],{},"Yes, MQTT is flexible, you can basically publish any payload to any topic, but this can create a mess in the topic namespace.",[12,215,216,217,219,220,224],{},"Keeping it all consistent across multiple plants and vendors turns into a constant chore. This is the ",[19,218,21],{}," problem from the intro, just multiplied by every team that ever touched the system. Nothing is wrong, exactly, and it all keeps running, but at some point nobody can open the broker and understand the whole thing anymore. (If you're working through how to impose order on a sprawling MQTT setup, ",[169,221,223],{"href":222},"\u002Fblog\u002F2024\u002F11\u002Fgetting-the-most-out-of-mqtt-for-industrial-iot\u002F","getting the most out of MQTT for industrial IoT"," goes deeper on this.)",[12,226,227],{},"The third strain is the one that quietly causes the most trouble: state. If a device drops offline, it isn't always obvious. Plain MQTT will happily show you the last value a sensor published, steady as anything, long after the sensor itself has gone dark. Teams end up bolting on their own heartbeat logic just to answer the question \"is this device actually alive?\" There is a built-in MQTT feature that helps, the Last Will and Testament, where a client registers a message that the broker sends automatically if the connection drops, but you have to set it up yourself on every device, and plenty of setups never get around to it.",[12,229,230],{},"For small projects and proofs of concept, none of this matters and plain MQTT is completely fine. The cracks only show when you scale, twenty-plus lines or multiple sites, which is right about when teams start looking at Sparkplug B.",[34,232,234],{"id":233},"what-sparkplug-b-changes","What Sparkplug B changes",[12,236,237,238,243],{},"Sparkplug B is a specification that sits on top of MQTT, ",[169,239,242],{"href":240,"rel":241},"https:\u002F\u002Fsparkplug.eclipse.org\u002Fspecification\u002Fversion\u002F3.0\u002Fdocuments\u002Fsparkplug-specification-3.0.0.pdf",[173],"governed by the Eclipse Foundation",", and built specifically for industrial use. It doesn't replace MQTT, it adds the conventions MQTT deliberately leaves out: a fixed topic structure, a defined binary payload format using Google Protocol Buffers, and built-in device state. Look at what each one does for the three problems above.",[12,245,246,247,250],{},"For the structure problem, Sparkplug defines the topic layout so no team gets to invent its own. Every topic starts with ",[19,248,249],{},"spBv1.0"," to mark the version and encoding, then a group ID that bundles your edge nodes, usually by plant or site, followed by the message type, the edge node ID, and the device ID. The rigidity is the point. Onboarding a new line gets faster simply because everyone already speaks the same language.",[12,252,253,254,259,260,264],{},"For the bloat problem, the binary Protobuf format is far more compact than JSON. Protobuf payloads typically run 60 to 75% smaller than the equivalent JSON for the same data, since it drops the field names, repeated keys, and punctuation that JSON carries and encodes numbers as compact binary instead of text. Sparkplug also lets you batch many tag updates into a single message instead of one message per tag, which cuts broker overhead and network chatter, and it only sends when a value changes rather than polling. That report-by-exception approach, according to the ",[169,255,258],{"href":256,"rel":257},"https:\u002F\u002Fprojects.eclipse.org\u002Fprojects\u002Fiot.sparkplug",[173],"Eclipse Sparkplug project",", has been shown to cut network bandwidth by 80 to 95%, though only when the full state management is actually implemented. On constrained links like cellular or satellite, where bandwidth costs real money, that combination adds up quickly. (If you want to see what those binary savings look like in practice, here's a hands-on walkthrough of ",[169,261,263],{"href":262},"\u002Fblog\u002F2025\u002F11\u002Foptimize-industrial-data-protocol-buffers\u002F","optimizing industrial data with Protocol Buffers",".)",[12,266,267],{},"For the state problem, Sparkplug uses birth and death certificates. A device publishes a birth certificate when it comes online, listing everything it offers, and a death certificate when it disconnects. So instead of writing custom scripts to guess whether a device is alive, you get that state visible in the SCADA system out of the box. One detail most write-ups blur is worth getting right: the delivery of that death certificate on an unexpected disconnect is handled by MQTT's own Last Will mechanism, not by Sparkplug. Sparkplug defines the meaning and structure; MQTT does the delivering.",[12,269,270],{},"The real payoff isn't any single number, it's operational simplicity. Less time spent troubleshooting whether a device is alive or decoding someone else's topic scheme, and more time on the actual process.",[34,272,274],{"id":273},"the-qos-catch","The QoS catch",[12,276,277],{},"Sparkplug B carries a trade-off that rarely makes it into the comparison posts, and to my mind it's a serious one.",[12,279,280,281,286],{},"The ",[169,282,285],{"href":283,"rel":284},"https:\u002F\u002Fgithub.com\u002Feclipse-sparkplug\u002Fsparkplug\u002Fblob\u002Fmaster\u002Fdocs\u002Fnormative_statements.md",[173],"Sparkplug B spec mandates QoS 0"," for all data and lifecycle messages, the NBIRTH, DBIRTH, NDATA, DDATA, NDEATH, and DDEATH messages that carry your actual telemetry and device state. The one exception is the Primary Host Application's STATE message, which uses QoS 1 so host availability is signalled reliably. But for the data you care about, QoS 0 means \"fire and forget.\" The publisher sends a message and moves on, with no delivery guarantee. In theory that's maximum speed. In practice, if the network hiccups or the broker restarts, that data is gone. For a real-time dashboard, fine. For a regulated environment where every reading has to be accounted for, that's a genuine risk. Plain MQTT, by contrast, lets you pick your quality of service: QoS 0, QoS 1 for \"at least once,\" or QoS 2 for \"exactly once.\" If you can't afford to lose data, you choose a higher level and pay for it in some performance.",[12,288,289],{},"The other costs are smaller but real. The binary payload that saves you bandwidth is also harder to debug, since you can't just read it off the wire without the right tooling. And teams used to sending plain JSON have a learning curve to climb: topic conventions, birth and death messages, protobuf schemas. For a handful of sensors, that overhead isn't worth it. Plain MQTT is simpler and does the job.",[34,291,293],{"id":292},"how-to-choose-between-mqtt-and-sparkplug-b","How to choose between MQTT and Sparkplug B",[12,295,296],{},"If you want a way to work through the decision rather than a verdict, run your situation past these in order.",[298,299,300,308,314,320,326,332],"ol",{},[301,302,303,307],"li",{},[304,305,306],"strong",{},"Map your scale and who touches the system."," Count devices, sites, teams, and vendors. A single site with a handful of sensors you fully control points to plain MQTT; many devices across multiple teams or vendors points toward Sparkplug B.",[301,309,310,313],{},[304,311,312],{},"Decide whether you can tolerate losing a message."," Sparkplug B mandates QoS 0, fire and forget, for all data and lifecycle messages, with no delivery guarantee. If your data is regulated or safety-critical and every reading must be accounted for, use plain MQTT with a higher QoS level.",[301,315,316,319],{},[304,317,318],{},"Audit your topic naming."," If teams are each inventing their own topic conventions and nobody can read the broker at a glance anymore, that disorder is the signal that Sparkplug B's fixed namespace is worth adopting.",[301,321,322,325],{},[304,323,324],{},"Check your bandwidth and network conditions."," On constrained or costly links such as cellular or satellite, Sparkplug B's compact binary payloads and report-by-exception cut traffic meaningfully. On a fast local network the difference matters less.",[301,327,328,331],{},[304,329,330],{},"Look at what consumes the data downstream."," If a SCADA system, historian, or analytics layer must understand the data without custom integration for every source, Sparkplug B's self-describing payloads pay off.",[301,333,334,337],{},[304,335,336],{},"Consider running both."," Match each protocol to the data it carries: Sparkplug B for the bulk of telemetry, plain MQTT with higher QoS for the critical data that cannot be lost.",[34,339,341],{"id":340},"mqtt-sparkplug-b-or-both","MQTT, Sparkplug B, or both",[12,343,344],{},"Run those steps and a shape usually emerges. Plain MQTT fits when you control both ends, want flexibility, or genuinely cannot lose a message and need a higher QoS than Sparkplug allows for data: small deployments, prototypes, regulated data with strict traceability. Sparkplug B earns its complexity when many devices and vendors feed something downstream that has to understand the data on its own, and the odd dropped reading isn't a catastrophe: real-time dashboards, OEE, non-critical analytics.",[12,346,347],{},"And often the honest answer is both. The pattern I've seen at larger manufacturers is to run Sparkplug B for the bulk of their telemetry and fall back to plain MQTT with higher QoS, or another protocol entirely, for the critical data that absolutely cannot be lost. They aren't really competitors. They're the same foundation with different amounts of structure and different guarantees, and the smart move is matching each to the data it's carrying.",[12,349,350,351,355,356,360],{},"Whichever way you land, the next step is wiring it up. If you're building on FlowFuse, here are practical guides for ",[169,352,354],{"href":353},"\u002Fblog\u002F2024\u002F06\u002Fhow-to-use-mqtt-in-node-red\u002F","using MQTT in FlowFuse"," and for ",[169,357,359],{"href":358},"\u002Fblog\u002F2024\u002F08\u002Fusing-mqtt-sparkplugb-with-node-red\u002F","using MQTT Sparkplug B with FlowFuse",".",{"title":362,"searchDepth":363,"depth":363,"links":364},"",4,[365,367,368,369,370,371,372],{"id":36,"depth":366,"text":37},2,{"id":153,"depth":366,"text":154},{"id":163,"depth":366,"text":164},{"id":233,"depth":366,"text":234},{"id":273,"depth":366,"text":274},{"id":292,"depth":366,"text":293},{"id":340,"depth":366,"text":341},{"type":374,"title":375,"description":376},"contact","Make MQTT and Sparkplug B work without the plumbing","Whether you settle on plain MQTT, Sparkplug B, or both, FlowFuse lets you connect your brokers and build dashboards and logic on that data with low-code, with an AI copilot that builds the flows for you from a prompt. FlowFuse supports both MQTT and Sparkplug B, along with all the major industrial protocols you are likely to run alongside them, so your data lands in one place regardless of what each device speaks. Talk to our team about your industrial data.","2026-06-11","A practical guide to choosing between plain MQTT and Sparkplug B for industrial IoT: where MQTT's flexibility turns into a topic-namespace mess, what Sparkplug B's structure, binary payloads, and birth\u002Fdeath certificates fix, the QoS 0 trade-off nobody mentions, and why most large deployments end up running both.","md",null,"\u002Fblog\u002F2026\u002F06\u002Fimages\u002Fmqtt-vs-sparkplug.png",{"keywords":383,"excerpt":384},"mqtt vs sparkplug b, sparkplug b, mqtt, industrial pub sub, mqtt topic namespace, sparkplug birth death certificate, mqtt qos, protobuf vs json, unified namespace, scada mqtt, iiot messaging, report by exception",{"type":9,"value":385},[386],[12,387,14],{},true,"\u002Fblog\u002F2026\u002F06\u002Fmqtt-vs-sparkplug-b",{"title":5,"description":378},{"loc":389},"blog\u002F2026\u002F06\u002Fmqtt-vs-sparkplug-b","MQTT moves your data. Sparkplug B gives it structure. Here's how to choose.",[395,396,397],"post","mqtt","sparkplug","MQTT is a lightweight transport that moves industrial data but says nothing about what that data means, how topics are named, or whether a device is still alive. That flexibility turns into a mess at scale. Sparkplug B layers a fixed topic namespace, compact binary payloads, and birth\u002Fdeath certificates on top of MQTT to fix exactly that, at the cost of more complexity and a hard QoS 0 (fire-and-forget) delivery model for telemetry with no guarantee. Use plain MQTT for small or custom setups and data you cannot lose; use Sparkplug B for many-device, multi-vendor systems feeding SCADA or analytics; and expect larger deployments to run both, matching each protocol to the data it carries.","ahzY8E6X1X4dCTPL81uk0M0MeXqYc8jSEe1k12Hq_HY",{"id":401,"extension":402,"meta":403,"sections":404,"stem":793,"__hash__":794},"featureCatalog\u002Ffeature-catalog.yml","yml",{},[405,456,557,619,696,775],{"id":406,"title":407,"features":408},"ai-automation","AI & Automation",[409,419,429,439,445,451],{"id":410,"title":411,"description":412,"docsLink":413,"changelog":414,"tiers":418},"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",[415],{"url":416,"release":417},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner\u002F","2.28",{"edge":388,"hub":388,"fleet":388},{"id":420,"title":421,"description":422,"docsLink":423,"changelog":424,"subfeature":388,"showOnPricing":427,"tiers":428},"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",[425],{"url":426,"release":417},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context\u002F",false,{"edge":388,"hub":388,"fleet":388},{"id":430,"title":431,"description":432,"docsLink":433,"changelog":434,"subfeature":388,"showOnPricing":427,"tiers":438},"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",[435],{"url":436,"release":437},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building\u002F","2.30",{"edge":388,"hub":388,"fleet":388},{"id":440,"title":441,"description":442,"docsLink":443,"subfeature":388,"beta":388,"showOnPricing":427,"tiers":444},"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":388,"hub":388,"fleet":388},{"id":446,"title":447,"description":448,"docsLink":449,"tiers":450},"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":388,"hub":388,"fleet":388},{"id":452,"title":453,"description":454,"tiers":455},"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":388,"hub":388,"fleet":388},{"id":457,"title":458,"features":459},"build","Build",[460,466,472,482,488,494,498,504,510,518,524,528,532,541,549],{"id":461,"title":462,"description":463,"docsLink":464,"tiers":465},"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":388,"hub":427,"fleet":388},{"id":467,"title":468,"description":469,"docsLink":470,"tiers":471},"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":388,"hub":388,"fleet":388},{"id":473,"title":474,"description":475,"docsLink":476,"changelog":477,"tiers":481},"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",[478],{"url":479,"release":480},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation\u002F","2.33",{"edge":388,"hub":388,"fleet":388},{"id":483,"title":484,"description":485,"docsLink":486,"tiers":487},"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":388,"hub":388,"fleet":388},{"id":489,"title":490,"description":491,"docsLink":492,"showOnPricing":427,"tiers":493},"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":388,"hub":388,"fleet":388},{"id":495,"title":496,"showOnPricing":427,"tiers":497},"static-assets","Static Assets",{"edge":388,"hub":388,"fleet":388},{"id":499,"title":500,"description":501,"docsLink":502,"tiers":503},"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":388,"hub":388,"fleet":388},{"id":505,"title":506,"description":507,"docsLink":508,"tiers":509},"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":388,"hub":388,"fleet":388},{"id":511,"title":512,"description":513,"changelog":514,"subfeature":388,"showOnPricing":427,"tiers":517},"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.",[515],{"url":516,"release":480},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards\u002F",{"edge":388,"hub":388,"fleet":388},{"id":519,"title":520,"description":521,"docsLink":522,"tiers":523},"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":388,"hub":388,"fleet":388},{"id":525,"title":526,"subfeature":388,"showOnPricing":427,"tiers":527},"blueprints-ot-apps","Blueprints - OT APPS",{"edge":388,"hub":427,"fleet":388},{"id":529,"title":530,"subfeature":388,"showOnPricing":427,"tiers":531},"blueprints-it-apps","Blueprints - IT APPS",{"edge":427,"hub":388,"fleet":427},{"id":533,"title":534,"description":535,"changelog":536,"showOnPricing":427,"tiers":540},"immersive-editor-snapshots","Snapshot Details in Immersive Editor","View and manage snapshot details directly inside the immersive editor without leaving your editing session.",[537],{"url":538,"release":539},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor\u002F","2.29",{"edge":388,"hub":388,"fleet":388},{"id":542,"title":543,"description":544,"changelog":545,"showOnPricing":427,"tiers":548},"immersive-editor-drawer","Customisable Immersive Editor Drawer","Pin, move, resize, or full-screen the immersive editor drawer. Your preferences are remembered between sessions.",[546],{"url":547,"release":437},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer\u002F",{"edge":388,"hub":388,"fleet":388},{"id":550,"title":551,"description":552,"changelog":553,"showOnPricing":427,"tiers":556},"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.",[554],{"url":555,"release":539},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title\u002F",{"edge":388,"hub":388,"fleet":388},{"id":558,"title":559,"features":560},"deploy","Deploy",[561,567,576,582,588,594,600,606,611],{"id":562,"title":563,"description":564,"docsLink":565,"tiers":566},"hosted-instances","Cloud Instances","Run Node-RED instances managed and hosted by FlowFuse.","\u002Fdocs\u002Fuser\u002Fintroduction\u002F#creating-a-node-red-instance",{"edge":388,"hub":388,"fleet":388},{"id":568,"title":569,"description":570,"docsLink":571,"changelog":572,"tiers":575},"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",[573],{"url":574,"release":417},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options\u002F",{"edge":388,"hub":427,"fleet":388},{"id":577,"title":578,"description":579,"docsLink":580,"tiers":581},"custom-hostnames","Custom Hostnames","Access your Node-RED application via your own domain name.","\u002Fdocs\u002Fuser\u002Fcustom-hostnames\u002F",{"edge":427,"hub":388,"fleet":427},{"id":583,"title":584,"description":585,"docsLink":586,"tiers":587},"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":388,"hub":427,"fleet":388},{"id":589,"title":590,"description":591,"docsLink":592,"showOnPricing":427,"tiers":593},"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":388,"hub":388,"fleet":388},{"id":595,"title":596,"description":597,"docsLink":598,"tiers":599},"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":388,"hub":388,"fleet":388},{"id":601,"title":602,"description":603,"docsLink":604,"tiers":605},"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":427,"hub":388,"fleet":427},{"id":607,"title":608,"description":609,"docsLink":604,"subfeature":388,"showOnPricing":427,"tiers":610},"git-integration-github","GitHub","Push and pull snapshots to GitHub repositories through DevOps Pipeline Git Stages.",{"edge":427,"hub":388,"fleet":427},{"id":612,"title":613,"description":614,"docsLink":604,"changelog":615,"subfeature":388,"showOnPricing":427,"tiers":618},"git-integration-azure","Azure DevOps","Push and pull snapshots to Azure DevOps repositories through DevOps Pipeline Git Stages.",[616],{"url":617,"release":539},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops\u002F",{"edge":427,"hub":388,"fleet":427},{"id":620,"title":621,"features":622},"operate-maintain","Operate & Maintain",[623,629,635,640,648,652,656,661,667,673,678,684,688,692],{"id":624,"title":625,"description":626,"docsLink":627,"tiers":628},"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":388,"hub":388,"fleet":388},{"id":630,"title":631,"description":632,"docsLink":633,"subfeature":388,"showOnPricing":427,"tiers":634},"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":388,"hub":388,"fleet":388},{"id":636,"title":637,"description":638,"docsLink":633,"subfeature":388,"showOnPricing":427,"tiers":639},"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":388,"hub":388,"fleet":388},{"id":641,"title":642,"description":643,"changelog":644,"subfeature":388,"showOnPricing":427,"tiers":647},"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.",[645],{"url":646,"release":539},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer\u002F",{"edge":388,"hub":388,"fleet":388},{"id":649,"title":650,"subfeature":388,"showOnPricing":427,"tiers":651},"version-history-timeline","Version History Timeline",{"edge":388,"hub":388,"fleet":388},{"id":653,"title":654,"tiers":655},"unlimited-workflow-executions","Unlimited Workflow Executions",{"edge":388,"hub":388,"fleet":388},{"id":657,"title":658,"description":659,"tiers":660},"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":388,"hub":427,"fleet":388},{"id":662,"title":663,"description":664,"docsLink":665,"tiers":666},"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":388,"hub":427,"fleet":388},{"id":668,"title":669,"description":670,"docsLink":671,"tiers":672},"high-availability","High Availability","Leverage horizontal scaling for reliable and scalable processing of your data through Node-RED.","\u002Fdocs\u002Fuser\u002Fhigh-availability\u002F",{"edge":427,"hub":388,"fleet":427},{"id":674,"title":675,"description":676,"tiers":677},"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":388,"hub":388,"fleet":388},{"id":679,"title":680,"description":681,"docsLink":682,"subfeature":388,"showOnPricing":427,"tiers":683},"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":388,"hub":388,"fleet":388},{"id":685,"title":686,"subfeature":388,"showOnPricing":427,"tiers":687},"email-alerts","Email Alerts",{"edge":388,"hub":388,"fleet":388},{"id":689,"title":690,"showOnPricing":427,"tiers":691},"api-debug-length-limit","API\u002FDebug Length Limit",{"edge":388,"hub":388,"fleet":388},{"id":693,"title":694,"tiers":695},"protected-instances","Protected Instances",{"edge":427,"hub":388,"fleet":427},{"id":697,"title":698,"features":699},"govern-secure","Govern and Secure",[700,709,715,721,726,732,738,744,752,758,764,770],{"id":701,"title":702,"description":703,"docsLink":704,"changelog":705,"tiers":708},"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",[706],{"url":707,"release":480},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups\u002F",{"edge":388,"hub":388,"fleet":388},{"id":710,"title":711,"description":712,"docsLink":713,"tiers":714},"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":388,"hub":388,"fleet":388},{"id":716,"title":717,"description":718,"docsLink":719,"tiers":720},"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":427,"hub":388,"fleet":388},{"id":722,"title":723,"description":724,"tiers":725},"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":388,"hub":427,"fleet":427},{"id":727,"title":728,"description":729,"docsLink":730,"tiers":731},"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":388,"hub":388,"fleet":388},{"id":733,"title":734,"description":735,"docsLink":736,"tiers":737},"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":388,"hub":388,"fleet":388},{"id":739,"title":740,"description":741,"docsLink":742,"subfeature":388,"showOnPricing":427,"tiers":743},"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":388,"hub":388,"fleet":388},{"id":745,"title":746,"description":747,"changelog":748,"subfeature":388,"showOnPricing":427,"tiers":751},"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.",[749],{"url":750,"release":480},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats\u002F",{"edge":388,"hub":388,"fleet":388},{"id":753,"title":754,"description":755,"docsLink":756,"showOnPricing":427,"tiers":757},"team-members","Team Members","Invite multiple team members to collaborate on the same Node-RED flows.","\u002Fdocs\u002Fuser\u002Fteam\u002F#teams",{"edge":388,"hub":388,"fleet":388},{"id":759,"title":760,"description":761,"docsLink":762,"showOnPricing":427,"tiers":763},"endpoint-security","Endpoint Security","Secure HTTP endpoints for hosted Node-RED instances using FlowFuse credentials.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#security",{"edge":388,"hub":388,"fleet":388},{"id":765,"title":766,"description":767,"docsLink":768,"tiers":769},"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":427,"hub":388,"fleet":427},{"id":771,"title":772,"description":773,"tiers":774},"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":427,"hub":388,"fleet":427},{"id":776,"title":777,"features":778},"support","Support",[779,784,788],{"id":780,"title":781,"docsLink":782,"tiers":783},"installation-support","Installation Support","\u002Fdocs\u002Finstall\u002Fintroduction\u002F#do-you-need-help-installation-service",{"edge":388,"hub":388,"fleet":388},{"id":785,"title":786,"showOnPricing":427,"tiers":787},"live-chat-support","Live Chat Support",{"edge":388,"hub":388,"fleet":388},{"id":789,"title":790,"docsLink":791,"tiers":792},"enterprise-support","Enterprise Support","\u002Fdocs\u002Fpremium-support\u002F",{"edge":388,"hub":388,"fleet":388},"feature-catalog","0AnkhTIPCECCwP9NmbTWP5HvRYx4FTSao4lG93-HaWM",[796,799,802,805,808,811,813,816,819,822,825,827,830,833,836,839,842,845,848,851,854,857,860,863,866,869,872,875,878,881,884,887,890,893,896,899,902,905,908,911,914,917,920,923,926,929,932,935,938,940,943,946,949,952,955,958,961,963,966,969,972,975,978,980,983,986,989,992,995,998,1001,1004,1007,1010,1012,1015,1018,1021,1024,1027,1030,1033,1036,1039,1042,1045,1048,1051,1054,1056,1059,1062,1065,1068,1071,1074,1077,1080,1083,1086,1089,1092,1095,1098,1101,1104,1107,1110,1112,1115,1118,1121,1124,1127,1130,1133,1135,1138,1141,1144,1147,1150,1153,1156,1159,1162,1165,1168,1171,1174,1177,1180,1183,1186,1189,1192,1195,1198,1201,1204,1207,1210,1213,1216,1219,1222,1225,1228,1231,1234,1237,1240,1243,1246,1249,1252,1255,1258,1261,1264,1267,1270,1273,1276,1279,1282,1285,1287,1290,1293,1296,1299,1302,1305,1308,1311,1314,1317,1320,1323,1326],{"path":797,"title":798},"\u002Fchangelog\u002F2023\u002F09\u002Fcustom-node-support","Custom Node Support",{"path":800,"title":801},"\u002Fchangelog\u002F2023\u002F09\u002Fdevops-actions","DevOps Pipeline with action selection",{"path":803,"title":804},"\u002Fchangelog\u002F2023\u002F09\u002Fintroduction-enterprise-tier","Introducing the Enterprise Tier",{"path":806,"title":807},"\u002Fchangelog\u002F2023\u002F09\u002Fpipeline-api","API Endpoint for DevOps Pipeline",{"path":809,"title":810},"\u002Fchangelog\u002F2023\u002F09\u002Fsnapshots-devices","Usability improvements to Device Management",{"path":812,"title":520},"\u002Fchangelog\u002F2023\u002F10\u002Fblueprints",{"path":814,"title":815},"\u002Fchangelog\u002F2023\u002F10\u002Fcertified-nodes","Certified Nodes",{"path":817,"title":818},"\u002Fchangelog\u002F2023\u002F10\u002Fdevice-snapshot-selection","Enhanced Snapshot Selection",{"path":820,"title":821},"\u002Fchangelog\u002F2023\u002F10\u002Fpath-bug-fix","Device Agent path bug fix",{"path":823,"title":824},"\u002Fchangelog\u002F2023\u002F10\u002Fresource-alerts","Resource Monitoring in Audit Log",{"path":826,"title":711},"\u002Fchangelog\u002F2023\u002F11\u002F2fa",{"path":828,"title":829},"\u002Fchangelog\u002F2023\u002F11\u002Fdefault-editor","Device Editor enabled by default",{"path":831,"title":832},"\u002Fchangelog\u002F2023\u002F11\u002Fdevices-in-pipelines","Devices in DevOps Pipelines",{"path":834,"title":835},"\u002Fchangelog\u002F2023\u002F11\u002Fproject-nodes-devices","Project Nodes for Devices",{"path":837,"title":838},"\u002Fchangelog\u002F2023\u002F12\u002Fbilling","No Credit Card required for billing",{"path":840,"title":841},"\u002Fchangelog\u002F2023\u002F12\u002Fblueprint-selection","Blueprint Selection Update",{"path":843,"title":844},"\u002Fchangelog\u002F2023\u002F12\u002Fdevice-groups","Device Groups",{"path":846,"title":847},"\u002Fchangelog\u002F2023\u002F12\u002Femail-alerting-node-red-crash","Email Alerts for Audit Log Events",{"path":849,"title":850},"\u002Fchangelog\u002F2023\u002F12\u002Fnode-red-updated","Node-RED 3.1.3 now available",{"path":852,"title":853},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-audit-log","Introducing the Device Auditlog Feature",{"path":855,"title":856},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-groups-snapshot","Device Groups - Automatic snapshot assignment",{"path":858,"title":859},"\u002Fchangelog\u002F2024\u002F01\u002Ffleet-mode","Renaming \"Default Device Mode\" to \"Fleet Mode\"",{"path":861,"title":862},"\u002Fchangelog\u002F2024\u002F01\u002Fhelm-v2","Helm Chart v2.0",{"path":864,"title":865},"\u002Fchangelog\u002F2024\u002F01\u002Fnew-blueprints","New Blueprints added",{"path":867,"title":868},"\u002Fchangelog\u002F2024\u002F01\u002Fsecurity-updates","Security Updates",{"path":870,"title":871},"\u002Fchangelog\u002F2024\u002F01\u002Fsso-team-membership","Managing Team Membership via SSO",{"path":873,"title":874},"\u002Fchangelog\u002F2024\u002F01\u002Fstreamlined-device-assignment","Streamlined Device assignment",{"path":876,"title":877},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-auto-snapshot","Device Auto Snapshots",{"path":879,"title":880},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-instance-audit-logs","Device Instance Audit Logging",{"path":882,"title":883},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-onboarding-improvements","Device Onboarding Improvements",{"path":885,"title":886},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-pricing-change","Pricing change for Devices",{"path":888,"title":889},"\u002Fchangelog\u002F2024\u002F02\u002Finstance-auto-snapshots","Instance Auto Snapshots",{"path":891,"title":892},"\u002Fchangelog\u002F2024\u002F02\u002Fpostgresql-upgrade","PostgreSQL Version update",{"path":894,"title":895},"\u002Fchangelog\u002F2024\u002F03\u002Fbearer-token-authentication","Bearer Token Authentication for Node-RED Instances",{"path":897,"title":898},"\u002Fchangelog\u002F2024\u002F03\u002Finstance-protection-mode","Instance Protection Mode",{"path":900,"title":901},"\u002Fchangelog\u002F2024\u002F03\u002Flimits-debug-payload","Configure HTTP Payload and Debug Message size",{"path":903,"title":904},"\u002Fchangelog\u002F2024\u002F03\u002Frestart-devices-remotly","Remote Device Restart",{"path":906,"title":907},"\u002Fchangelog\u002F2024\u002F04\u002Fcustom-nodes-on-devices","Custom Nodes Support on Devices",{"path":909,"title":910},"\u002Fchangelog\u002F2024\u002F04\u002Fdevice-auto-snapshot","Direct Dashboard Access",{"path":912,"title":913},"\u002Fchangelog\u002F2024\u002F04\u002Fimproving-device-groups","Improving Device Groups",{"path":915,"title":916},"\u002Fchangelog\u002F2024\u002F04\u002Fpricing-change","Pricing change Enterprise & Teams Tier",{"path":918,"title":919},"\u002Fchangelog\u002F2024\u002F04\u002Ftougher-rate-limiting","Tougher Rate Limiting on Public Routes",{"path":921,"title":922},"\u002Fchangelog\u002F2024\u002F05\u002Finstance-healthcheck","Customizing instance health-check settings",{"path":924,"title":925},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-blueprints","Blueprints added to Library",{"path":927,"title":928},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-flowviewer","Team Library - Flow Viewer",{"path":930,"title":931},"\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices","Managing Node-RED versions on Devices",{"path":933,"title":934},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements","Snapshot Improvements",{"path":936,"title":937},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements-pt3","Snapshot Upload",{"path":939,"title":937},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-upload",{"path":941,"title":942},"\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support","Running the Device Agent behind an HTTP proxy",{"path":944,"title":945},"\u002Fchangelog\u002F2024\u002F06\u002Flibrary-blueprints","Custom hostnames for your instances",{"path":947,"title":948},"\u002Fchangelog\u002F2024\u002F06\u002Fmultiline-env-vars","Multi-line Environment Variables",{"path":950,"title":951},"\u002Fchangelog\u002F2024\u002F06\u002Fsnapshot-flow-compare","Compare Snapshots flows",{"path":953,"title":954},"\u002Fchangelog\u002F2024\u002F07\u002Fapplications-search","Applications Search",{"path":956,"title":957},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-group-clear-snapshot","Device Groups Snapshots",{"path":959,"title":960},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-delete","Managing devices",{"path":962,"title":960},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-move",{"path":964,"title":965},"\u002Fchangelog\u002F2024\u002F07\u002Fedit-snapshots","Edit Snapshots",{"path":967,"title":968},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant","The FlowFuse Expert",{"path":970,"title":971},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant-json","FlowFuse Expert Writes JSON",{"path":973,"title":974},"\u002Fchangelog\u002F2024\u002F07\u002Fimmersive-editor","Immersive Editor Experience",{"path":976,"title":977},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-inbox","Notifications Inbox",{"path":979,"title":977},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-update",{"path":981,"title":982},"\u002Fchangelog\u002F2024\u002F07\u002Fpersistent-storage","Persistent Storage on FlowFuse Cloud",{"path":984,"title":985},"\u002Fchangelog\u002F2024\u002F07\u002Fsso","Single Sign On Updates",{"path":987,"title":988},"\u002Fchangelog\u002F2024\u002F08\u002Fbill-of-materials","Bill of Materials",{"path":990,"title":991},"\u002Fchangelog\u002F2024\u002F08\u002Fenterprise-license-update","Enforcing Enterprise Restrictions",{"path":993,"title":994},"\u002Fchangelog\u002F2024\u002F08\u002Fldap-sso-groups","LDAP Single Sign On Updates",{"path":996,"title":997},"\u002Fchangelog\u002F2024\u002F08\u002Fstatic-file-service-navigation-visibility","Static File Service Navigation and Visibility",{"path":999,"title":1000},"\u002Fchangelog\u002F2024\u002F10\u002Fdevice-group-env-vars","Environment Variables for your Device Groups",{"path":1002,"title":1003},"\u002Fchangelog\u002F2024\u002F10\u002Fmqtt-service","MQTT Broker Service",{"path":1005,"title":1006},"\u002Fchangelog\u002F2024\u002F10\u002Fnotifications-bulk-actions","Managing Notifications",{"path":1008,"title":1009},"\u002Fchangelog\u002F2024\u002F10\u002Fsnapshot-download-upload-options","Snapshot Upload and Download Improvements",{"path":1011,"title":650},"\u002Fchangelog\u002F2024\u002F10\u002Fversion-history-timeline",{"path":1013,"title":1014},"\u002Fchangelog\u002F2024\u002F11\u002Faudit-log-hierarchy","Audit logs show hierarchical events",{"path":1016,"title":1017},"\u002Fchangelog\u002F2024\u002F11\u002Fdevice-agent-release","Device Agent 3.0 released",{"path":1019,"title":1020},"\u002Fchangelog\u002F2024\u002F11\u002Fmqtt-topic-hierarchy","MQTT Topic Hierarchy view",{"path":1022,"title":1023},"\u002Fchangelog\u002F2024\u002F11\u002Fteam-search","Team-wide search",{"path":1025,"title":1026},"\u002Fchangelog\u002F2024\u002F12\u002Fdashboad-iframe","Allow Dashboards to be embedded in iFrames",{"path":1028,"title":1029},"\u002Fchangelog\u002F2024\u002F12\u002Fdevice-editor-cache","Device Editor Access Speed Up",{"path":1031,"title":1032},"\u002Fchangelog\u002F2024\u002F12\u002Fteam-bom-timeline","Team BOM and Pipeline Views",{"path":1034,"title":1035},"\u002Fchangelog\u002F2025\u002F01\u002Ffree-tier-onboarding","New Onboarding Tour for Free Tier Users",{"path":1037,"title":1038},"\u002Fchangelog\u002F2025\u002F01\u002Fhidden-env-vars","Hidden Environment Variables",{"path":1040,"title":1041},"\u002Fchangelog\u002F2025\u002F01\u002Fimproved-diagnostics","Improved Diagnostics",{"path":1043,"title":1044},"\u002Fchangelog\u002F2025\u002F01\u002Fteam-level-groups","Team level view of Groups",{"path":1046,"title":1047},"\u002Fchangelog\u002F2025\u002F02\u002Fadditional-device-version-history-events","New Remote Instances Version History Events",{"path":1049,"title":1050},"\u002Fchangelog\u002F2025\u002F02\u002Fbroker-error-feedback","Improved Broker Connection Feedback",{"path":1052,"title":1053},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-agent-updates","FlowFuse User Authentication on Remote Instances",{"path":1055,"title":650},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-version-history-timeline",{"path":1057,"title":1058},"\u002Fchangelog\u002F2025\u002F02\u002Fexternal-brokers","External MQTT Brokers",{"path":1060,"title":1061},"\u002Fchangelog\u002F2025\u002F02\u002Fmqtt-schema-suggestions","MQTT Smart Schema Suggestions",{"path":1063,"title":1064},"\u002Fchangelog\u002F2025\u002F02\u002Fresend-and-extend-team-invitation-expiration","Re-send Team Invitations",{"path":1066,"title":1067},"\u002Fchangelog\u002F2025\u002F02\u002Fschema-docs","Personalized Schema Documentation",{"path":1069,"title":1070},"\u002Fchangelog\u002F2025\u002F02\u002Ftopic-hierarchy-search","Search & Filter for Topic Hierarchy List",{"path":1072,"title":1073},"\u002Fchangelog\u002F2025\u002F03\u002Fcontainer-tags","Changes to tags for flowfuse\u002Fnode-red",{"path":1075,"title":1076},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-groups","Multiple Device Groups in a pipeline",{"path":1078,"title":1079},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-local-login","Local Login for Remote Instances",{"path":1081,"title":1082},"\u002Fchangelog\u002F2025\u002F03\u002Ffree-tier","Free Tier now more accessible to all",{"path":1084,"title":1085},"\u002Fchangelog\u002F2025\u002F03\u002Fresource-notifications","Resource Alerts",{"path":1087,"title":1088},"\u002Fchangelog\u002F2025\u002F03\u002Fsnapshot-filter","Filtering Snapshots",{"path":1090,"title":1091},"\u002Fchangelog\u002F2025\u002F03\u002Fteam-npm-registry","NPM Package Hosting",{"path":1093,"title":1094},"\u002Fchangelog\u002F2025\u002F03\u002Ftopic-deletion","MQTT Topic Management",{"path":1096,"title":1097},"\u002Fchangelog\u002F2025\u002F04\u002Fdevice-provisioning","Remote Instance Provisioning",{"path":1099,"title":1100},"\u002Fchangelog\u002F2025\u002F04\u002Fgit-integration","Git Integration with Pipelines",{"path":1102,"title":1103},"\u002Fchangelog\u002F2025\u002F04\u002Finstance-log-browsing","Better Node-RED log handling",{"path":1105,"title":1106},"\u002Fchangelog\u002F2025\u002F05\u002Fimport-node-red-flows","Import Node-RED Flows During Remote Instance Setup",{"path":1108,"title":1109},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant","FlowFuse Expert just got smarter",{"path":1111,"title":1109},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant-2",{"path":1113,"title":1114},"\u002Fchangelog\u002F2025\u002F06\u002Fgit-integration","Pulling snapshots from Git with Pipelines",{"path":1116,"title":1117},"\u002Fchangelog\u002F2025\u002F06\u002Finstance-performance-memory","Memory Metrics in Instance Performance View",{"path":1119,"title":1120},"\u002Fchangelog\u002F2025\u002F06\u002Fnew-home-page","Introducing the New Home Page Experience",{"path":1122,"title":1123},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance","Team Performance Feature",{"path":1125,"title":1126},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance-view","Instance Performance View",{"path":1128,"title":1129},"\u002Fchangelog\u002F2025\u002F06\u002Fui-refresh","Navigation UI Refresh",{"path":1131,"title":1132},"\u002Fchangelog\u002F2025\u002F07\u002Fbrowse-node-red-flows","Browse for Node-RED Flows During Remote Instance Setup",{"path":1134,"title":474},"\u002Fchangelog\u002F2025\u002F07\u002Fflowfuse-tables",{"path":1136,"title":1137},"\u002Fchangelog\u002F2025\u002F07\u002Fimport-blueprints","Import blueprints directly into your existing instances",{"path":1139,"title":1140},"\u002Fchangelog\u002F2025\u002F07\u002Fsimplified-applications-overview","Simplified Applications Page with Summary Tiles",{"path":1142,"title":1143},"\u002Fchangelog\u002F2025\u002F07\u002Fsmart-suggestions","Smart Suggestions",{"path":1145,"title":1146},"\u002Fchangelog\u002F2025\u002F07\u002Fteam-to-pro-plan-rename","Team Plan Renamed to Pro Plan",{"path":1148,"title":1149},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-hosted","Generate snapshot descriptions with AI",{"path":1151,"title":1152},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-remote","AI Snapshot Descriptions Now Work with Remote Instances",{"path":1154,"title":1155},"\u002Fchangelog\u002F2025\u002F08\u002Fdevice-performance","FlowFuse Remote Instance Performance Data",{"path":1157,"title":1158},"\u002Fchangelog\u002F2025\u002F08\u002Fdirect-sso","Direct SSO Login",{"path":1160,"title":1161},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-assistant","FlowFuse Expert documents your flows",{"path":1163,"title":1164},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-mqtt","FlowFuse MQTT",{"path":1166,"title":1167},"\u002Fchangelog\u002F2025\u002F08\u002Fhttp-cors","Configure HTTP CORS",{"path":1169,"title":1170},"\u002Fchangelog\u002F2025\u002F08\u002Fsubflow-export","Export SubFlow as Node-RED module",{"path":1172,"title":1173},"\u002Fchangelog\u002F2025\u002F08\u002Ftables-assistant","FlowFuse Tables with a little help from the Assistant",{"path":1175,"title":1176},"\u002Fchangelog\u002F2025\u002F09\u002Fexpose-saml-groups-to-dashboard","Allow SSO groups to be shared with the Node-RED Dashboard",{"path":1178,"title":1179},"\u002Fchangelog\u002F2025\u002F09\u002Finline-assist","FlowFuse Expert can help you write code",{"path":1181,"title":1182},"\u002Fchangelog\u002F2025\u002F09\u002Fretiring-flowforge-device-agent","No more @flowforge\u002Fflowforge-device-agent releases",{"path":1184,"title":1185},"\u002Fchangelog\u002F2025\u002F09\u002Frevised-instance-snapshot-ui","Streamlined Snapshot Management",{"path":1187,"title":1188},"\u002Fchangelog\u002F2025\u002F09\u002Fteam-broker-async-api","Capture Async API data from FlowFuse Team Broker",{"path":1190,"title":1191},"\u002Fchangelog\u002F2025\u002F10\u002Fapplication-level-rbac","Application-level access control for Enterprise teams",{"path":1193,"title":1194},"\u002Fchangelog\u002F2025\u002F10\u002Fbulk-device-group-assignment","Easier Access to Bulk Device Group Management",{"path":1196,"title":1197},"\u002Fchangelog\u002F2025\u002F10\u002Fduplicate-instances-across-applications","Duplicate Instances Across Different Applications",{"path":1199,"title":1200},"\u002Fchangelog\u002F2025\u002F10\u002Fimport-flows-on-instance-creation","Import flows during instance creation",{"path":1202,"title":1203},"\u002Fchangelog\u002F2025\u002F10\u002Fmcp-nodes","FlowFuse MCP Server Nodes",{"path":1205,"title":1206},"\u002Fchangelog\u002F2025\u002F10\u002Fonnx-nodes","FlowFuse AI Nodes",{"path":1208,"title":1209},"\u002Fchangelog\u002F2025\u002F10\u002Fsettings-page-device-group-management","Device Group Management from Settings Page",{"path":1211,"title":1212},"\u002Fchangelog\u002F2025\u002F11\u002Fff-expert-update","FlowFuse Expert Update",{"path":1214,"title":1215},"\u002Fchangelog\u002F2025\u002F11\u002Fminimum-nodejs-version","Node.js v20 Minimum Version Requirement",{"path":1217,"title":1218},"\u002Fchangelog\u002F2025\u002F11\u002Fsso-session","SSO control over Session life",{"path":1220,"title":1221},"\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights","FlowFuse Expert: Now with MCP-Powered Insights",{"path":1223,"title":1224},"\u002Fchangelog\u002F2025\u002F12\u002Fscheduled-maintenance","Scheduled Maintenance Mode",{"path":1226,"title":1227},"\u002Fchangelog\u002F2026\u002F01\u002Fdevice-agent-containers","Device Agent Docker Containers updated",{"path":1229,"title":1230},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-manage-palette","FlowFuse Expert: Enhanced Palette Integration",{"path":1232,"title":1233},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-nr-actions","FlowFuse Expert: Integration with Node-RED",{"path":1235,"title":1236},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-palette-queries","FlowFuse Expert: Palette Queries",{"path":1238,"title":1239},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-select-flows","FlowFuse Expert: Ask about your flows",{"path":1241,"title":1242},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-rbacs","FlowFuse Expert: MCP-Powered Insights with RBACs",{"path":1244,"title":1245},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-security","FlowFuse Expert: MCP-Powered Insights",{"path":1247,"title":1248},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options","Set Node.js Options for Remote Instances",{"path":1250,"title":1251},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context","FlowFuse Expert: Helping you make sense of your debug log",{"path":1253,"title":1254},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner","FlowFuse Expert: Never Miss an Update",{"path":1256,"title":1257},"\u002Fchangelog\u002F2026\u002F02\u002Fha-instance-rolling-restart","HA Hosted Instance Rolling Restart",{"path":1259,"title":1260},"\u002Fchangelog\u002F2026\u002F02\u002Fremote-instances-immersive-editor","Immersive Mode for Remote Instances",{"path":1262,"title":1263},"\u002Fchangelog\u002F2026\u002F02\u002Frestoring-snapshots-to-remote-instances","Restoring snapshots to developer-mode Remote Instances",{"path":1265,"title":1266},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops","Azure DevOps Pipeline support",{"path":1268,"title":1269},"\u002Fchangelog\u002F2026\u002F03\u002Fdeveloper-mode-in-immersive-editor","Developer Mode Now Accessible from the Immersive Editor",{"path":1271,"title":1272},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title","Embedded Editor Now Shows Active Tab",{"path":1274,"title":1275},"\u002Fchangelog\u002F2026\u002F03\u002Fmarch-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on March 28th, 2026",{"path":1277,"title":1278},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor","View Snapshot Details in the Immersive Editor",{"path":1280,"title":1281},"\u002Fchangelog\u002F2026\u002F04\u002Fexpert-action-links","FlowFuse expert action links",{"path":1283,"title":1284},"\u002Fchangelog\u002F2026\u002F04\u002Fhosted-instance-url-env-var","Hosted Instances know their own URL",{"path":1286,"title":543},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer",{"path":1288,"title":1289},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer","Richer snapshot comparison view",{"path":1291,"title":1292},"\u002Fchangelog\u002F2026\u002F05\u002Fai-opt-out","AI Feature Opt-Out for Teams",{"path":1294,"title":1295},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building","FlowFuse Expert Builds Your Application",{"path":1297,"title":1298},"\u002Fchangelog\u002F2026\u002F05\u002Fsingle-sso-provider","Single SSO provider for all users",{"path":1300,"title":1301},"\u002Fchangelog\u002F2026\u002F06\u002Fdark-mode","Dark Mode",{"path":1303,"title":1304},"\u002Fchangelog\u002F2026\u002F06\u002Fdevice-agent-v4-released","Device Agent v4 released",{"path":1306,"title":1307},"\u002Fchangelog\u002F2026\u002F06\u002Fgeneric-git-server-support","Connect Pipelines to Any Git Server",{"path":1309,"title":1310},"\u002Fchangelog\u002F2026\u002F06\u002Fjuly-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on July 11th, 2026",{"path":1312,"title":1313},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups","Application Roles from SSO Groups",{"path":1315,"title":1316},"\u002Fchangelog\u002F2026\u002F07\u002Fdevice-agent-onboarding","Getting started with FlowFuse straight from the terminal",{"path":1318,"title":1319},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-enhancements","FlowFuse Expert Enhancements",{"path":1321,"title":1322},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation","FlowFuse Expert Can Now Work With Your Tables",{"path":1324,"title":1325},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats","Team Scoped Personal Access Tokens",{"path":1327,"title":1328},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards","A Dedicated Home for Your Dashboards",[],1786105902170]