[{"data":1,"prerenderedAt":1367},["ShallowReactive",2],{"blog-\u002Fblog\u002F2026\u002F07\u002Fishikawa-fishbone-diagram":3,"featureCatalog":437,"changelog-titles":832,"blog-all-for-related":1366},{"id":4,"title":5,"authors":6,"body":8,"cta":412,"date":416,"description":417,"extension":418,"features":419,"image":420,"lastUpdated":421,"meta":422,"navigation":427,"path":428,"release":419,"seo":429,"sitemap":430,"stem":431,"subtitle":432,"tags":433,"tldr":435,"video":419,"__hash__":436},"blog\u002Fblog\u002F2026\u002F07\u002Fishikawa-fishbone-diagram.md","Ishikawa Fishbone Diagram: 6M, Manufacturing Example & Template",[7],"sumit-shinde",{"type":9,"value":10,"toc":399},"minimark",[11,15,18,23,26,29,40,48,52,71,74,78,81,122,125,128,132,135,141,147,153,164,174,178,181,219,222,225,229,232,310,313,317,320,331,338,342,345,351,357,363,369,375,379,382,388,391],[12,13,14],"p",{},"The most dangerous words in a root cause investigation are often the ones spoken with the most confidence: \"We already know what caused it.\" That assumption sends teams straight to a fix before they've explored the system behind the failure. When the same issue returns a few weeks later, it becomes clear they fixed the symptom, not the cause.",[12,16,17],{},"Kaoru Ishikawa built a drawing in the 1960s to kill that exact reflex. It looks like a fish skeleton, which is why almost nobody calls it by his name. Sixty years and a dozen fancier root-cause tools later, engineers still reach for it first. Not because it's clever. Because it forces every theory in the room onto one wall, where the weak ones have nowhere to hide.",[19,20,22],"h2",{"id":21},"what-is-a-fishbone-diagram","What Is a Fishbone Diagram?",[12,24,25],{},"Strip away the terminology and a fishbone diagram is a structured way to brainstorm causes without letting the loudest person in the room decide the answer.",[12,27,28],{},"You write the problem, the effect you want to eliminate, on the right side. That's the fish's head. A horizontal line runs left into it: the spine. Off that spine you draw diagonal branches, the ribs, and each rib is a category of causes. Under each category you hang the specific things that might be going wrong. When you're done, you're looking at every plausible cause for one problem, sorted into groups, on a single page.",[12,30,31,32,39],{},"The naming gets confusing, so here it is plainly. Ishikawa diagram, fishbone diagram, and cause-and-effect diagram all refer to the same tool. The names are used interchangeably in practice, though purists will point out that not every cause-and-effect sketch follows the fishbone shape. It's one of the ",[33,34,38],"a",{"href":35,"rel":36},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSeven_basic_tools_of_quality",[37],"nofollow","seven basic quality tools",", the club of simple techniques quality engineers lean on before pulling out anything statistical.",[12,41,42,43,47],{},"What it does ",[44,45,46],"em",{},"not"," do is prove anything. A fishbone diagram generates hypotheses. It tells you where to look, not what the answer is. That distinction is the whole difference between a diagram that helps and one that wastes an afternoon, and we'll come back to it.",[19,49,51],{"id":50},"who-invented-the-ishikawa-diagram","Who Invented the Ishikawa Diagram?",[12,53,54,55,60,61,64,65,70],{},"The diagram is named after ",[33,56,59],{"href":57,"rel":58},"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FKaoru_Ishikawa",[37],"Kaoru Ishikawa"," (1915–1989), a Japanese engineer, University of Tokyo professor, and one of the founding fathers of modern quality management. He popularized it in the 1960s while developing quality processes at the Kawasaki shipyards, and formalized it in his 1968 book ",[44,62,63],{},"Guide to Quality Control",". His aim was democratic: he wanted quality improvement in the hands of ordinary workers, not locked inside a specialist team, so he built a diagram simple enough that anyone on the line could use it, which is a big part of why the ",[33,66,69],{"href":67,"rel":68},"https:\u002F\u002Fasq.org\u002Fquality-resources\u002Ffishbone",[37],"American Society for Quality"," still lists it among the seven basic tools sixty years on.",[12,72,73],{},"Its reach since has been broad. One famous case is Mazda, whose engineers reportedly used an Ishikawa diagram to map every factor behind the \"Jinba Ittai\" (horse and rider as one) feel of the original MX-5 Miata.",[19,75,77],{"id":76},"what-are-the-6ms-in-a-fishbone-diagram","What Are the 6Ms in a Fishbone Diagram?",[12,79,80],{},"Ishikawa suggested generic labels for the rib categories so teams would have somewhere to start instead of staring at a blank spine. In manufacturing, those defaults became the 6Ms:",[82,83,84,92,98,104,110,116],"ul",{},[85,86,87,91],"li",{},[88,89,90],"strong",{},"Manpower"," (people): training gaps, unclear responsibilities, communication breakdowns, fatigue.",[85,93,94,97],{},[88,95,96],{},"Method"," (process): missing standards, steps performed inconsistently, procedures that no longer match reality.",[85,99,100,103],{},[88,101,102],{},"Machine"," (equipment): worn parts, skipped maintenance, wrong tooling, calibration drift.",[85,105,106,109],{},[88,107,108],{},"Material"," (inputs): out-of-spec raw material, supplier variation, wrong batch, storage damage.",[85,111,112,115],{},[88,113,114],{},"Measurement"," (data): miscalibrated instruments, wrong gauge, inconsistent inspection, bad data collection.",[85,117,118,121],{},[88,119,120],{},"Mother Nature"," (environment): temperature, humidity, vibration, dust, anything the surroundings do to the process.",[12,123,124],{},"Here is the part most guides bury: Ishikawa himself told people to rename these categories to fit their problem. The 6Ms are training wheels, not scripture. They map cleanly onto a factory floor, but even there you'll often want to tweak them, and outside a production line they can fall apart entirely.",[12,126,127],{},"Some teams add a seventh M, Money, when cost drivers matter. Process industries sometimes swap in categories like Environment, Equipment, and Procedures. For a service or business problem, the 7Ps (Product, Price, Place, Promotion, People, Process, Physical Evidence) fit better than machinery and materials. The right categories are the ones that make your team say \"oh, we haven't thought about that bucket yet.\" If a category sits empty because it doesn't apply, delete it. An empty rib is not a sign you missed something; it's a sign the label was wrong for your problem.",[19,129,131],{"id":130},"how-to-make-a-fishbone-diagram","How to Make a Fishbone Diagram",[12,133,134],{},"The mechanics take five minutes. Doing it well takes discipline. Here's the sequence.",[12,136,137,140],{},[88,138,139],{},"Write a problem statement, not a topic."," \"Machine downtime\" is a topic. \"Line 3 filler stops an average of 4 times per shift, each stop lasting 6 to 12 minutes\" is a problem statement. The second one gives the team something specific to explain. Vague heads produce vague ribs.",[12,142,143,146],{},[88,144,145],{},"Draw the spine and pick your categories."," Four to six is the sweet spot. Fewer and you're not really sorting; more and the diagram turns into a wall of branches nobody can read. Start from the 6Ms if you're in manufacturing, adapt hard if you're not.",[12,148,149,152],{},[88,150,151],{},"Brainstorm causes under each category."," This is where the tool earns its keep. Go category by category and ask what, under this heading, could produce the effect. Write everything down, even the theories you doubt. The point of sorting into buckets is that it triggers ideas you'd never reach with an open-ended \"what's wrong?\"",[12,154,155,158,159,163],{},[88,156,157],{},"Push each cause deeper with \"why.\""," A first-level cause is rarely the root. Pair the fishbone with the ",[33,160,162],{"href":161},"\u002Fblog\u002F2025\u002F12\u002Ffive-whys-root-cause-analysis-definition-examples\u002F","5 Whys",": for each rib entry, ask why that happens, and hang the answer as a sub-branch. \"Bearing failed\" becomes \"bearing failed → lubrication skipped → PM schedule not followed → no one owns the schedule.\" Now you're looking at a root, not a symptom.",[12,165,166,169,170,173],{},[88,167,168],{},"Then stop drawing and start verifying."," This is the step that separates analysis from theater. A finished fishbone is a list of ",[44,171,172],{},"suspects",", and every suspect is a hypothesis you can test against data. Circle the two or three most likely causes, then go check them: pull the maintenance log, measure the material, watch the operator. The diagram points the flashlight. It doesn't tell you what's in the dark.",[19,175,177],{"id":176},"fishbone-diagram-example","Fishbone Diagram Example",[12,179,180],{},"Abstract diagrams teach nothing, so here's the kind of case that plays out on a real line. A packaging line is rejecting cartons because the printed date code is smearing. That's the head of the fish. The team runs 6M categories:",[82,182,183,189,195,201,207,213],{},[85,184,185,188],{},[88,186,187],{},"Machine:"," print head height drifted, print head overdue for cleaning, conveyor speed increased last month.",[85,190,191,194],{},[88,192,193],{},"Material:"," new ink supplier introduced two weeks ago, carton stock switched to a glossier finish.",[85,196,197,200],{},[88,198,199],{},"Method:"," no standard for print-head-to-carton distance, cleaning interval never written down.",[85,202,203,206],{},[88,204,205],{},"Manpower:"," night shift not trained on the new ink's dry time.",[85,208,209,212],{},[88,210,211],{},"Measurement:"," no check on ink cure before cartons stack.",[85,214,215,218],{},[88,216,217],{},"Mother Nature:"," plant humidity up since the HVAC repair.",[12,220,221],{},"Six categories, roughly a dozen suspects. Now the 5 Whys on the strongest lead: the glossier carton stock. Why does gloss smear? Ink doesn't absorb. Why not? The new stock is non-porous. Why did we switch? Purchasing found a cheaper supplier. Why didn't anyone flag the print impact? No one owns print-compatibility sign-off on material changes.",[12,223,224],{},"Notice what happened. The obvious fix, \"clean the print head,\" would have bought a day of relief and then the smearing returns. The fishbone surfaced two causes that interacted, a material change and a missing sign-off process, that a single-thread investigation would have walked right past. That's the entire value of the tool: it makes interacting causes visible instead of letting you commit to the first plausible one.",[19,226,228],{"id":227},"fishbone-vs-5-whys-vs-pareto-which-one-when","Fishbone vs. 5 Whys vs. Pareto: Which One, When",[12,230,231],{},"The fishbone rarely works alone, and it's easy to reach for the wrong tool. Here's how the three most common root-cause techniques divide the labor.",[233,234,235,254],"table",{},[236,237,238],"thead",{},[239,240,241,245,248,251],"tr",{},[242,243,244],"th",{},"Tool",[242,246,247],{},"What it does",[242,249,250],{},"Use it when",[242,252,253],{},"Where it falls short",[255,256,257,274,291],"tbody",{},[239,258,259,265,268,271],{},[260,261,262],"td",{},[88,263,264],{},"Fishbone diagram",[260,266,267],{},"Goes wide. Surfaces every plausible cause across several categories so nothing obvious gets missed.",[260,269,270],{},"You don't yet know where the problem lives and want the team's collective knowledge on one page.",[260,272,273],{},"Treats every branch as equally worth investigating. Says nothing about which cause matters most.",[239,275,276,282,285,288],{},[260,277,278],{},[88,279,280],{},[33,281,162],{"href":161},[260,283,284],{},"Goes deep. Drills a single cause chain, asking \"why\" until you hit something fixable rather than another symptom.",[260,286,287],{},"After the fishbone, on the two or three branches you think are strongest.",[260,289,290],{},"It's a single thread. Drill the wrong cause and you'll reach a confident, well-reasoned, wrong answer.",[239,292,293,301,304,307],{},[260,294,295],{},[88,296,297],{},[33,298,300],{"href":299},"\u002Fblog\u002F2025\u002F08\u002Fpareto-chart-manufacturing-guide\u002F","Pareto chart",[260,302,303],{},"Ranks. Sorts candidate causes by frequency or impact so you fix the vital few, not the trivial many.",[260,305,306],{},"You can count occurrences and need to decide where to act first.",[260,308,309],{},"Needs data you may not have early on, and only ranks what you already thought to measure.",[12,311,312],{},"The sequence is: fishbone to find suspects, 5 Whys to reach the root of the best ones, Pareto to decide which roots are worth fixing first. They're not competitors. They're a pipeline.",[19,314,316],{"id":315},"fishbone-diagram-template","Fishbone Diagram Template",[12,318,319],{},"You don't need software. Here's a text skeleton you can drop into any doc and fill in:",[321,322,327],"pre",{"className":323,"code":325,"language":326},[324],"language-text","                    Method            Machine           Measurement\n                       \\                 |                  \u002F\n             cause ─────\\        cause ──|        cause ───\u002F\n             cause ──────\\       cause ──|        cause ──\u002F\n                          \\              |               \u002F\n   ══════════════════════════════════════════════════════════►  [ PROBLEM ]\n                          \u002F              |               \\\n             cause ──────\u002F       cause ──|        cause ──\\\n             cause ─────\u002F        cause ──|        cause ───\\\n                       \u002F                 |                  \\\n                   Manpower          Material           Mother Nature\n","text",[328,329,325],"code",{"__ignoreMap":330},"",[12,332,333,334,337],{},"Rules for using it: replace the six labels with categories that fit ",[44,335,336],{},"your"," problem, keep the problem statement specific, and treat every \"cause\" line as something you'll later verify with data. If you prefer digital, any diagramming tool works, but the paper-and-marker version on a wall is often better because it gets the whole team pointing at the same branch.",[19,339,341],{"id":340},"common-fishbone-diagram-mistakes","Common Fishbone Diagram Mistakes",[12,343,344],{},"Most failed fishbone sessions fail the same handful of ways.",[12,346,347,350],{},[88,348,349],{},"Labeling empty branches and calling it done."," Six categories with two vague words under each is a brainstorming template, not root-cause analysis. If the diagram doesn't contain specific, checkable causes, you've drawn a fish, not found a problem.",[12,352,353,356],{},[88,354,355],{},"Confusing the diagram with the answer."," The single most common error. The fishbone lists suspects; it does not convict any of them. Teams that skip verification and just \"fix\" the most-discussed branch are gambling, not analyzing.",[12,358,359,362],{},[88,360,361],{},"Using the 6Ms where they don't fit."," Forcing every problem into the manufacturing 6Ms produces empty ribs and missed causes. Pick categories that match your failure surface, and drop the ones that don't apply.",[12,364,365,368],{},[88,366,367],{},"Vague problem statements."," A fuzzy head produces a fuzzy diagram. Spend the extra two minutes writing what actually happened, where, and how often.",[12,370,371,374],{},[88,372,373],{},"Stopping at the first level."," \"Operator error\" is where lazy analysis ends and real analysis begins. Ask why five times before you believe you've hit a root.",[19,376,378],{"id":377},"where-the-fishbone-fits","Where the Fishbone Fits",[12,380,381],{},"The Ishikawa diagram survives because it does one job well: it gets a group of people to externalize their theories, sort them, and argue about them on paper before spending money. It's cheap, it's visual, and it needs no training to read. Those are the same reasons the simplest tools tend to outlast the sophisticated ones.",[12,383,384,385,387],{},"It has limits. It shows causes but not their relative weight or how they interact over time; for that you'd reach for a ",[33,386,300],{"href":299},", fault tree, or statistical analysis. And it's only as good as the verification that follows it. Draw the fish, then go prove which bone is broken.",[12,389,390],{},"Used that way, as a hypothesis generator that hands off to real investigation, it remains one of the fastest ways to stop treating symptoms and start fixing causes. Sixty years in, that's still a rare thing for a tool to do.",[12,392,393,394,398],{},"The catch is that verification needs data the whiteboard can't give you: how often the machine actually stalls, whether the material batch really shifted, what the sensor logged when the defect appeared. That's the step where ",[33,395,397],{"href":396},"\u002F","FlowFuse"," fits, connecting your PLCs, sensors, and quality systems into dashboards so you can test which suspected cause is real and confirm the fix held. It won't draw the fishbone for you, but it settles which bone was broken.",{"title":330,"searchDepth":400,"depth":400,"links":401},4,[402,404,405,406,407,408,409,410,411],{"id":21,"depth":403,"text":22},2,{"id":50,"depth":403,"text":51},{"id":76,"depth":403,"text":77},{"id":130,"depth":403,"text":131},{"id":176,"depth":403,"text":177},{"id":227,"depth":403,"text":228},{"id":315,"depth":403,"text":316},{"id":340,"depth":403,"text":341},{"id":377,"depth":403,"text":378},{"type":413,"title":414,"description":415},"contact","Turn suspected causes into verified ones","Talk to our team about connecting your PLCs, sensors, and quality systems to FlowFuse, so you can verify which root cause is real with live production data and confirm your fixes actually hold.","2026-07-27","Learn what an Ishikawa (fishbone) diagram is, the 6Ms, and how to use it for root cause analysis in manufacturing, with a worked example, how it compares to the 5 Whys and Pareto analysis, a template, and common mistakes.","md",null,"\u002Fblog\u002F2026\u002F07\u002Fimages\u002Fwhat-is-ishikawa-fishbone-diagram.png","2026-07-29",{"excerpt":423},{"type":9,"value":424},[425],[12,426,14],{},true,"\u002Fblog\u002F2026\u002F07\u002Fishikawa-fishbone-diagram",{"title":5,"description":417},{"loc":428},"blog\u002F2026\u002F07\u002Fishikawa-fishbone-diagram","How a 60-year-old drawing still finds the root cause faster than most modern tools.",[434],"flowfuse","An Ishikawa diagram, better known as a fishbone or cause-and-effect diagram, finds the real cause of a problem instead of chasing symptoms by sorting possible causes into categories branching off a central spine. The 6Ms are a starting point for manufacturing, but you swap them for whatever fits your problem. It works because it forces a team to externalize and argue their theories on paper before spending money on a fix, and it fails when people stop at labeling empty branches and call that analysis. The diagram surfaces suspects; verifying which one is real, with data, is what actually fixes the problem.","TFJSjaDFPp5NLsvBtO-CkRoccbveU6WAxRoFF1wZC1E",{"id":438,"extension":439,"meta":440,"sections":441,"stem":830,"__hash__":831},"featureCatalog\u002Ffeature-catalog.yml","yml",{},[442,493,594,656,733,812],{"id":443,"title":444,"features":445},"ai-automation","AI & Automation",[446,456,466,476,482,488],{"id":447,"title":448,"description":449,"docsLink":450,"changelog":451,"tiers":455},"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",[452],{"url":453,"release":454},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner\u002F","2.28",{"edge":427,"hub":427,"fleet":427},{"id":457,"title":458,"description":459,"docsLink":460,"changelog":461,"subfeature":427,"showOnPricing":464,"tiers":465},"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",[462],{"url":463,"release":454},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context\u002F",false,{"edge":427,"hub":427,"fleet":427},{"id":467,"title":468,"description":469,"docsLink":470,"changelog":471,"subfeature":427,"showOnPricing":464,"tiers":475},"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",[472],{"url":473,"release":474},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building\u002F","2.30",{"edge":427,"hub":427,"fleet":427},{"id":477,"title":478,"description":479,"docsLink":480,"subfeature":427,"beta":427,"showOnPricing":464,"tiers":481},"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":427,"hub":427,"fleet":427},{"id":483,"title":484,"description":485,"docsLink":486,"tiers":487},"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":427,"hub":427,"fleet":427},{"id":489,"title":490,"description":491,"tiers":492},"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":427,"hub":427,"fleet":427},{"id":494,"title":495,"features":496},"build","Build",[497,503,509,519,525,531,535,541,547,555,561,565,569,578,586],{"id":498,"title":499,"description":500,"docsLink":501,"tiers":502},"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":427,"hub":464,"fleet":427},{"id":504,"title":505,"description":506,"docsLink":507,"tiers":508},"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":427,"hub":427,"fleet":427},{"id":510,"title":511,"description":512,"docsLink":513,"changelog":514,"tiers":518},"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",[515],{"url":516,"release":517},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation\u002F","2.33",{"edge":427,"hub":427,"fleet":427},{"id":520,"title":521,"description":522,"docsLink":523,"tiers":524},"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":427,"hub":427,"fleet":427},{"id":526,"title":527,"description":528,"docsLink":529,"showOnPricing":464,"tiers":530},"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":427,"hub":427,"fleet":427},{"id":532,"title":533,"showOnPricing":464,"tiers":534},"static-assets","Static Assets",{"edge":427,"hub":427,"fleet":427},{"id":536,"title":537,"description":538,"docsLink":539,"tiers":540},"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":427,"hub":427,"fleet":427},{"id":542,"title":543,"description":544,"docsLink":545,"tiers":546},"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":427,"hub":427,"fleet":427},{"id":548,"title":549,"description":550,"changelog":551,"subfeature":427,"showOnPricing":464,"tiers":554},"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.",[552],{"url":553,"release":517},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards\u002F",{"edge":427,"hub":427,"fleet":427},{"id":556,"title":557,"description":558,"docsLink":559,"tiers":560},"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":427,"hub":427,"fleet":427},{"id":562,"title":563,"subfeature":427,"showOnPricing":464,"tiers":564},"blueprints-ot-apps","Blueprints - OT APPS",{"edge":427,"hub":464,"fleet":427},{"id":566,"title":567,"subfeature":427,"showOnPricing":464,"tiers":568},"blueprints-it-apps","Blueprints - IT APPS",{"edge":464,"hub":427,"fleet":464},{"id":570,"title":571,"description":572,"changelog":573,"showOnPricing":464,"tiers":577},"immersive-editor-snapshots","Snapshot Details in Immersive Editor","View and manage snapshot details directly inside the immersive editor without leaving your editing session.",[574],{"url":575,"release":576},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor\u002F","2.29",{"edge":427,"hub":427,"fleet":427},{"id":579,"title":580,"description":581,"changelog":582,"showOnPricing":464,"tiers":585},"immersive-editor-drawer","Customisable Immersive Editor Drawer","Pin, move, resize, or full-screen the immersive editor drawer. Your preferences are remembered between sessions.",[583],{"url":584,"release":474},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer\u002F",{"edge":427,"hub":427,"fleet":427},{"id":587,"title":588,"description":589,"changelog":590,"showOnPricing":464,"tiers":593},"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.",[591],{"url":592,"release":576},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title\u002F",{"edge":427,"hub":427,"fleet":427},{"id":595,"title":596,"features":597},"deploy","Deploy",[598,604,613,619,625,631,637,643,648],{"id":599,"title":600,"description":601,"docsLink":602,"tiers":603},"hosted-instances","Cloud Instances","Run Node-RED instances managed and hosted by FlowFuse.","\u002Fdocs\u002Fuser\u002Fintroduction\u002F#creating-a-node-red-instance",{"edge":427,"hub":427,"fleet":427},{"id":605,"title":606,"description":607,"docsLink":608,"changelog":609,"tiers":612},"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",[610],{"url":611,"release":454},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options\u002F",{"edge":427,"hub":464,"fleet":427},{"id":614,"title":615,"description":616,"docsLink":617,"tiers":618},"custom-hostnames","Custom Hostnames","Access your Node-RED application via your own domain name.","\u002Fdocs\u002Fuser\u002Fcustom-hostnames\u002F",{"edge":464,"hub":427,"fleet":464},{"id":620,"title":621,"description":622,"docsLink":623,"tiers":624},"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":427,"hub":464,"fleet":427},{"id":626,"title":627,"description":628,"docsLink":629,"showOnPricing":464,"tiers":630},"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":427,"hub":427,"fleet":427},{"id":632,"title":633,"description":634,"docsLink":635,"tiers":636},"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":427,"hub":427,"fleet":427},{"id":638,"title":639,"description":640,"docsLink":641,"tiers":642},"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":464,"hub":427,"fleet":464},{"id":644,"title":645,"description":646,"docsLink":641,"subfeature":427,"showOnPricing":464,"tiers":647},"git-integration-github","GitHub","Push and pull snapshots to GitHub repositories through DevOps Pipeline Git Stages.",{"edge":464,"hub":427,"fleet":464},{"id":649,"title":650,"description":651,"docsLink":641,"changelog":652,"subfeature":427,"showOnPricing":464,"tiers":655},"git-integration-azure","Azure DevOps","Push and pull snapshots to Azure DevOps repositories through DevOps Pipeline Git Stages.",[653],{"url":654,"release":576},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops\u002F",{"edge":464,"hub":427,"fleet":464},{"id":657,"title":658,"features":659},"operate-maintain","Operate & Maintain",[660,666,672,677,685,689,693,698,704,710,715,721,725,729],{"id":661,"title":662,"description":663,"docsLink":664,"tiers":665},"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":427,"hub":427,"fleet":427},{"id":667,"title":668,"description":669,"docsLink":670,"subfeature":427,"showOnPricing":464,"tiers":671},"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":427,"hub":427,"fleet":427},{"id":673,"title":674,"description":675,"docsLink":670,"subfeature":427,"showOnPricing":464,"tiers":676},"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":427,"hub":427,"fleet":427},{"id":678,"title":679,"description":680,"changelog":681,"subfeature":427,"showOnPricing":464,"tiers":684},"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.",[682],{"url":683,"release":576},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer\u002F",{"edge":427,"hub":427,"fleet":427},{"id":686,"title":687,"subfeature":427,"showOnPricing":464,"tiers":688},"version-history-timeline","Version History Timeline",{"edge":427,"hub":427,"fleet":427},{"id":690,"title":691,"tiers":692},"unlimited-workflow-executions","Unlimited Workflow Executions",{"edge":427,"hub":427,"fleet":427},{"id":694,"title":695,"description":696,"tiers":697},"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":427,"hub":464,"fleet":427},{"id":699,"title":700,"description":701,"docsLink":702,"tiers":703},"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":427,"hub":464,"fleet":427},{"id":705,"title":706,"description":707,"docsLink":708,"tiers":709},"high-availability","High Availability","Leverage horizontal scaling for reliable and scalable processing of your data through Node-RED.","\u002Fdocs\u002Fuser\u002Fhigh-availability\u002F",{"edge":464,"hub":427,"fleet":464},{"id":711,"title":712,"description":713,"tiers":714},"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":427,"hub":427,"fleet":427},{"id":716,"title":717,"description":718,"docsLink":719,"subfeature":427,"showOnPricing":464,"tiers":720},"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":427,"hub":427,"fleet":427},{"id":722,"title":723,"subfeature":427,"showOnPricing":464,"tiers":724},"email-alerts","Email Alerts",{"edge":427,"hub":427,"fleet":427},{"id":726,"title":727,"showOnPricing":464,"tiers":728},"api-debug-length-limit","API\u002FDebug Length Limit",{"edge":427,"hub":427,"fleet":427},{"id":730,"title":731,"tiers":732},"protected-instances","Protected Instances",{"edge":464,"hub":427,"fleet":464},{"id":734,"title":735,"features":736},"govern-secure","Govern and Secure",[737,746,752,758,763,769,775,781,789,795,801,807],{"id":738,"title":739,"description":740,"docsLink":741,"changelog":742,"tiers":745},"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",[743],{"url":744,"release":517},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups\u002F",{"edge":427,"hub":427,"fleet":427},{"id":747,"title":748,"description":749,"docsLink":750,"tiers":751},"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":427,"hub":427,"fleet":427},{"id":753,"title":754,"description":755,"docsLink":756,"tiers":757},"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":464,"hub":427,"fleet":427},{"id":759,"title":760,"description":761,"tiers":762},"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":427,"hub":464,"fleet":464},{"id":764,"title":765,"description":766,"docsLink":767,"tiers":768},"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":427,"hub":427,"fleet":427},{"id":770,"title":771,"description":772,"docsLink":773,"tiers":774},"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":427,"hub":427,"fleet":427},{"id":776,"title":777,"description":778,"docsLink":779,"subfeature":427,"showOnPricing":464,"tiers":780},"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":427,"hub":427,"fleet":427},{"id":782,"title":783,"description":784,"changelog":785,"subfeature":427,"showOnPricing":464,"tiers":788},"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.",[786],{"url":787,"release":517},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats\u002F",{"edge":427,"hub":427,"fleet":427},{"id":790,"title":791,"description":792,"docsLink":793,"showOnPricing":464,"tiers":794},"team-members","Team Members","Invite multiple team members to collaborate on the same Node-RED flows.","\u002Fdocs\u002Fuser\u002Fteam\u002F#teams",{"edge":427,"hub":427,"fleet":427},{"id":796,"title":797,"description":798,"docsLink":799,"showOnPricing":464,"tiers":800},"endpoint-security","Endpoint Security","Secure HTTP endpoints for hosted Node-RED instances using FlowFuse credentials.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#security",{"edge":427,"hub":427,"fleet":427},{"id":802,"title":803,"description":804,"docsLink":805,"tiers":806},"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":464,"hub":427,"fleet":464},{"id":808,"title":809,"description":810,"tiers":811},"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":464,"hub":427,"fleet":464},{"id":813,"title":814,"features":815},"support","Support",[816,821,825],{"id":817,"title":818,"docsLink":819,"tiers":820},"installation-support","Installation Support","\u002Fdocs\u002Finstall\u002Fintroduction\u002F#do-you-need-help-installation-service",{"edge":427,"hub":427,"fleet":427},{"id":822,"title":823,"showOnPricing":464,"tiers":824},"live-chat-support","Live Chat Support",{"edge":427,"hub":427,"fleet":427},{"id":826,"title":827,"docsLink":828,"tiers":829},"enterprise-support","Enterprise Support","\u002Fdocs\u002Fpremium-support\u002F",{"edge":427,"hub":427,"fleet":427},"feature-catalog","0AnkhTIPCECCwP9NmbTWP5HvRYx4FTSao4lG93-HaWM",[833,836,839,842,845,848,850,853,856,859,862,864,867,870,873,876,879,882,885,888,891,894,897,900,903,906,909,912,915,918,921,924,927,930,933,936,939,942,945,948,951,954,957,960,963,966,969,972,975,977,980,983,986,989,992,995,998,1000,1003,1006,1009,1012,1015,1017,1020,1023,1026,1029,1032,1035,1038,1041,1044,1047,1049,1052,1055,1058,1061,1064,1067,1070,1073,1076,1079,1082,1085,1088,1091,1093,1096,1099,1102,1105,1108,1111,1114,1117,1120,1123,1126,1129,1132,1135,1138,1141,1144,1147,1149,1152,1155,1158,1161,1164,1167,1170,1172,1175,1178,1181,1184,1187,1190,1193,1196,1199,1202,1205,1208,1211,1214,1217,1220,1223,1226,1229,1232,1235,1238,1241,1244,1247,1250,1253,1256,1259,1262,1265,1268,1271,1274,1277,1280,1283,1286,1289,1292,1295,1298,1301,1304,1307,1310,1313,1316,1319,1322,1324,1327,1330,1333,1336,1339,1342,1345,1348,1351,1354,1357,1360,1363],{"path":834,"title":835},"\u002Fchangelog\u002F2023\u002F09\u002Fcustom-node-support","Custom Node Support",{"path":837,"title":838},"\u002Fchangelog\u002F2023\u002F09\u002Fdevops-actions","DevOps Pipeline with action selection",{"path":840,"title":841},"\u002Fchangelog\u002F2023\u002F09\u002Fintroduction-enterprise-tier","Introducing the Enterprise Tier",{"path":843,"title":844},"\u002Fchangelog\u002F2023\u002F09\u002Fpipeline-api","API Endpoint for DevOps Pipeline",{"path":846,"title":847},"\u002Fchangelog\u002F2023\u002F09\u002Fsnapshots-devices","Usability improvements to Device Management",{"path":849,"title":557},"\u002Fchangelog\u002F2023\u002F10\u002Fblueprints",{"path":851,"title":852},"\u002Fchangelog\u002F2023\u002F10\u002Fcertified-nodes","Certified Nodes",{"path":854,"title":855},"\u002Fchangelog\u002F2023\u002F10\u002Fdevice-snapshot-selection","Enhanced Snapshot Selection",{"path":857,"title":858},"\u002Fchangelog\u002F2023\u002F10\u002Fpath-bug-fix","Device Agent path bug fix",{"path":860,"title":861},"\u002Fchangelog\u002F2023\u002F10\u002Fresource-alerts","Resource Monitoring in Audit Log",{"path":863,"title":748},"\u002Fchangelog\u002F2023\u002F11\u002F2fa",{"path":865,"title":866},"\u002Fchangelog\u002F2023\u002F11\u002Fdefault-editor","Device Editor enabled by default",{"path":868,"title":869},"\u002Fchangelog\u002F2023\u002F11\u002Fdevices-in-pipelines","Devices in DevOps Pipelines",{"path":871,"title":872},"\u002Fchangelog\u002F2023\u002F11\u002Fproject-nodes-devices","Project Nodes for Devices",{"path":874,"title":875},"\u002Fchangelog\u002F2023\u002F12\u002Fbilling","No Credit Card required for billing",{"path":877,"title":878},"\u002Fchangelog\u002F2023\u002F12\u002Fblueprint-selection","Blueprint Selection Update",{"path":880,"title":881},"\u002Fchangelog\u002F2023\u002F12\u002Fdevice-groups","Device Groups",{"path":883,"title":884},"\u002Fchangelog\u002F2023\u002F12\u002Femail-alerting-node-red-crash","Email Alerts for Audit Log Events",{"path":886,"title":887},"\u002Fchangelog\u002F2023\u002F12\u002Fnode-red-updated","Node-RED 3.1.3 now available",{"path":889,"title":890},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-audit-log","Introducing the Device Auditlog Feature",{"path":892,"title":893},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-groups-snapshot","Device Groups - Automatic snapshot assignment",{"path":895,"title":896},"\u002Fchangelog\u002F2024\u002F01\u002Ffleet-mode","Renaming \"Default Device Mode\" to \"Fleet Mode\"",{"path":898,"title":899},"\u002Fchangelog\u002F2024\u002F01\u002Fhelm-v2","Helm Chart v2.0",{"path":901,"title":902},"\u002Fchangelog\u002F2024\u002F01\u002Fnew-blueprints","New Blueprints added",{"path":904,"title":905},"\u002Fchangelog\u002F2024\u002F01\u002Fsecurity-updates","Security Updates",{"path":907,"title":908},"\u002Fchangelog\u002F2024\u002F01\u002Fsso-team-membership","Managing Team Membership via SSO",{"path":910,"title":911},"\u002Fchangelog\u002F2024\u002F01\u002Fstreamlined-device-assignment","Streamlined Device assignment",{"path":913,"title":914},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-auto-snapshot","Device Auto Snapshots",{"path":916,"title":917},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-instance-audit-logs","Device Instance Audit Logging",{"path":919,"title":920},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-onboarding-improvements","Device Onboarding Improvements",{"path":922,"title":923},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-pricing-change","Pricing change for Devices",{"path":925,"title":926},"\u002Fchangelog\u002F2024\u002F02\u002Finstance-auto-snapshots","Instance Auto Snapshots",{"path":928,"title":929},"\u002Fchangelog\u002F2024\u002F02\u002Fpostgresql-upgrade","PostgreSQL Version update",{"path":931,"title":932},"\u002Fchangelog\u002F2024\u002F03\u002Fbearer-token-authentication","Bearer Token Authentication for Node-RED Instances",{"path":934,"title":935},"\u002Fchangelog\u002F2024\u002F03\u002Finstance-protection-mode","Instance Protection Mode",{"path":937,"title":938},"\u002Fchangelog\u002F2024\u002F03\u002Flimits-debug-payload","Configure HTTP Payload and Debug Message size",{"path":940,"title":941},"\u002Fchangelog\u002F2024\u002F03\u002Frestart-devices-remotly","Remote Device Restart",{"path":943,"title":944},"\u002Fchangelog\u002F2024\u002F04\u002Fcustom-nodes-on-devices","Custom Nodes Support on Devices",{"path":946,"title":947},"\u002Fchangelog\u002F2024\u002F04\u002Fdevice-auto-snapshot","Direct Dashboard Access",{"path":949,"title":950},"\u002Fchangelog\u002F2024\u002F04\u002Fimproving-device-groups","Improving Device Groups",{"path":952,"title":953},"\u002Fchangelog\u002F2024\u002F04\u002Fpricing-change","Pricing change Enterprise & Teams Tier",{"path":955,"title":956},"\u002Fchangelog\u002F2024\u002F04\u002Ftougher-rate-limiting","Tougher Rate Limiting on Public Routes",{"path":958,"title":959},"\u002Fchangelog\u002F2024\u002F05\u002Finstance-healthcheck","Customizing instance health-check settings",{"path":961,"title":962},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-blueprints","Blueprints added to Library",{"path":964,"title":965},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-flowviewer","Team Library - Flow Viewer",{"path":967,"title":968},"\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices","Managing Node-RED versions on Devices",{"path":970,"title":971},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements","Snapshot Improvements",{"path":973,"title":974},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements-pt3","Snapshot Upload",{"path":976,"title":974},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-upload",{"path":978,"title":979},"\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support","Running the Device Agent behind an HTTP proxy",{"path":981,"title":982},"\u002Fchangelog\u002F2024\u002F06\u002Flibrary-blueprints","Custom hostnames for your instances",{"path":984,"title":985},"\u002Fchangelog\u002F2024\u002F06\u002Fmultiline-env-vars","Multi-line Environment Variables",{"path":987,"title":988},"\u002Fchangelog\u002F2024\u002F06\u002Fsnapshot-flow-compare","Compare Snapshots flows",{"path":990,"title":991},"\u002Fchangelog\u002F2024\u002F07\u002Fapplications-search","Applications Search",{"path":993,"title":994},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-group-clear-snapshot","Device Groups Snapshots",{"path":996,"title":997},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-delete","Managing devices",{"path":999,"title":997},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-move",{"path":1001,"title":1002},"\u002Fchangelog\u002F2024\u002F07\u002Fedit-snapshots","Edit Snapshots",{"path":1004,"title":1005},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant","The FlowFuse Expert",{"path":1007,"title":1008},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant-json","FlowFuse Expert Writes JSON",{"path":1010,"title":1011},"\u002Fchangelog\u002F2024\u002F07\u002Fimmersive-editor","Immersive Editor Experience",{"path":1013,"title":1014},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-inbox","Notifications Inbox",{"path":1016,"title":1014},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-update",{"path":1018,"title":1019},"\u002Fchangelog\u002F2024\u002F07\u002Fpersistent-storage","Persistent Storage on FlowFuse Cloud",{"path":1021,"title":1022},"\u002Fchangelog\u002F2024\u002F07\u002Fsso","Single Sign On Updates",{"path":1024,"title":1025},"\u002Fchangelog\u002F2024\u002F08\u002Fbill-of-materials","Bill of Materials",{"path":1027,"title":1028},"\u002Fchangelog\u002F2024\u002F08\u002Fenterprise-license-update","Enforcing Enterprise Restrictions",{"path":1030,"title":1031},"\u002Fchangelog\u002F2024\u002F08\u002Fldap-sso-groups","LDAP Single Sign On Updates",{"path":1033,"title":1034},"\u002Fchangelog\u002F2024\u002F08\u002Fstatic-file-service-navigation-visibility","Static File Service Navigation and Visibility",{"path":1036,"title":1037},"\u002Fchangelog\u002F2024\u002F10\u002Fdevice-group-env-vars","Environment Variables for your Device Groups",{"path":1039,"title":1040},"\u002Fchangelog\u002F2024\u002F10\u002Fmqtt-service","MQTT Broker Service",{"path":1042,"title":1043},"\u002Fchangelog\u002F2024\u002F10\u002Fnotifications-bulk-actions","Managing Notifications",{"path":1045,"title":1046},"\u002Fchangelog\u002F2024\u002F10\u002Fsnapshot-download-upload-options","Snapshot Upload and Download Improvements",{"path":1048,"title":687},"\u002Fchangelog\u002F2024\u002F10\u002Fversion-history-timeline",{"path":1050,"title":1051},"\u002Fchangelog\u002F2024\u002F11\u002Faudit-log-hierarchy","Audit logs show hierarchical events",{"path":1053,"title":1054},"\u002Fchangelog\u002F2024\u002F11\u002Fdevice-agent-release","Device Agent 3.0 released",{"path":1056,"title":1057},"\u002Fchangelog\u002F2024\u002F11\u002Fmqtt-topic-hierarchy","MQTT Topic Hierarchy view",{"path":1059,"title":1060},"\u002Fchangelog\u002F2024\u002F11\u002Fteam-search","Team-wide search",{"path":1062,"title":1063},"\u002Fchangelog\u002F2024\u002F12\u002Fdashboad-iframe","Allow Dashboards to be embedded in iFrames",{"path":1065,"title":1066},"\u002Fchangelog\u002F2024\u002F12\u002Fdevice-editor-cache","Device Editor Access Speed Up",{"path":1068,"title":1069},"\u002Fchangelog\u002F2024\u002F12\u002Fteam-bom-timeline","Team BOM and Pipeline Views",{"path":1071,"title":1072},"\u002Fchangelog\u002F2025\u002F01\u002Ffree-tier-onboarding","New Onboarding Tour for Free Tier Users",{"path":1074,"title":1075},"\u002Fchangelog\u002F2025\u002F01\u002Fhidden-env-vars","Hidden Environment Variables",{"path":1077,"title":1078},"\u002Fchangelog\u002F2025\u002F01\u002Fimproved-diagnostics","Improved Diagnostics",{"path":1080,"title":1081},"\u002Fchangelog\u002F2025\u002F01\u002Fteam-level-groups","Team level view of Groups",{"path":1083,"title":1084},"\u002Fchangelog\u002F2025\u002F02\u002Fadditional-device-version-history-events","New Remote Instances Version History Events",{"path":1086,"title":1087},"\u002Fchangelog\u002F2025\u002F02\u002Fbroker-error-feedback","Improved Broker Connection Feedback",{"path":1089,"title":1090},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-agent-updates","FlowFuse User Authentication on Remote Instances",{"path":1092,"title":687},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-version-history-timeline",{"path":1094,"title":1095},"\u002Fchangelog\u002F2025\u002F02\u002Fexternal-brokers","External MQTT Brokers",{"path":1097,"title":1098},"\u002Fchangelog\u002F2025\u002F02\u002Fmqtt-schema-suggestions","MQTT Smart Schema Suggestions",{"path":1100,"title":1101},"\u002Fchangelog\u002F2025\u002F02\u002Fresend-and-extend-team-invitation-expiration","Re-send Team Invitations",{"path":1103,"title":1104},"\u002Fchangelog\u002F2025\u002F02\u002Fschema-docs","Personalized Schema Documentation",{"path":1106,"title":1107},"\u002Fchangelog\u002F2025\u002F02\u002Ftopic-hierarchy-search","Search & Filter for Topic Hierarchy List",{"path":1109,"title":1110},"\u002Fchangelog\u002F2025\u002F03\u002Fcontainer-tags","Changes to tags for flowfuse\u002Fnode-red",{"path":1112,"title":1113},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-groups","Multiple Device Groups in a pipeline",{"path":1115,"title":1116},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-local-login","Local Login for Remote Instances",{"path":1118,"title":1119},"\u002Fchangelog\u002F2025\u002F03\u002Ffree-tier","Free Tier now more accessible to all",{"path":1121,"title":1122},"\u002Fchangelog\u002F2025\u002F03\u002Fresource-notifications","Resource Alerts",{"path":1124,"title":1125},"\u002Fchangelog\u002F2025\u002F03\u002Fsnapshot-filter","Filtering Snapshots",{"path":1127,"title":1128},"\u002Fchangelog\u002F2025\u002F03\u002Fteam-npm-registry","NPM Package Hosting",{"path":1130,"title":1131},"\u002Fchangelog\u002F2025\u002F03\u002Ftopic-deletion","MQTT Topic Management",{"path":1133,"title":1134},"\u002Fchangelog\u002F2025\u002F04\u002Fdevice-provisioning","Remote Instance Provisioning",{"path":1136,"title":1137},"\u002Fchangelog\u002F2025\u002F04\u002Fgit-integration","Git Integration with Pipelines",{"path":1139,"title":1140},"\u002Fchangelog\u002F2025\u002F04\u002Finstance-log-browsing","Better Node-RED log handling",{"path":1142,"title":1143},"\u002Fchangelog\u002F2025\u002F05\u002Fimport-node-red-flows","Import Node-RED Flows During Remote Instance Setup",{"path":1145,"title":1146},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant","FlowFuse Expert just got smarter",{"path":1148,"title":1146},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant-2",{"path":1150,"title":1151},"\u002Fchangelog\u002F2025\u002F06\u002Fgit-integration","Pulling snapshots from Git with Pipelines",{"path":1153,"title":1154},"\u002Fchangelog\u002F2025\u002F06\u002Finstance-performance-memory","Memory Metrics in Instance Performance View",{"path":1156,"title":1157},"\u002Fchangelog\u002F2025\u002F06\u002Fnew-home-page","Introducing the New Home Page Experience",{"path":1159,"title":1160},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance","Team Performance Feature",{"path":1162,"title":1163},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance-view","Instance Performance View",{"path":1165,"title":1166},"\u002Fchangelog\u002F2025\u002F06\u002Fui-refresh","Navigation UI Refresh",{"path":1168,"title":1169},"\u002Fchangelog\u002F2025\u002F07\u002Fbrowse-node-red-flows","Browse for Node-RED Flows During Remote Instance Setup",{"path":1171,"title":511},"\u002Fchangelog\u002F2025\u002F07\u002Fflowfuse-tables",{"path":1173,"title":1174},"\u002Fchangelog\u002F2025\u002F07\u002Fimport-blueprints","Import blueprints directly into your existing instances",{"path":1176,"title":1177},"\u002Fchangelog\u002F2025\u002F07\u002Fsimplified-applications-overview","Simplified Applications Page with Summary Tiles",{"path":1179,"title":1180},"\u002Fchangelog\u002F2025\u002F07\u002Fsmart-suggestions","Smart Suggestions",{"path":1182,"title":1183},"\u002Fchangelog\u002F2025\u002F07\u002Fteam-to-pro-plan-rename","Team Plan Renamed to Pro Plan",{"path":1185,"title":1186},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-hosted","Generate snapshot descriptions with AI",{"path":1188,"title":1189},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-remote","AI Snapshot Descriptions Now Work with Remote Instances",{"path":1191,"title":1192},"\u002Fchangelog\u002F2025\u002F08\u002Fdevice-performance","FlowFuse Remote Instance Performance Data",{"path":1194,"title":1195},"\u002Fchangelog\u002F2025\u002F08\u002Fdirect-sso","Direct SSO Login",{"path":1197,"title":1198},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-assistant","FlowFuse Expert documents your flows",{"path":1200,"title":1201},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-mqtt","FlowFuse MQTT",{"path":1203,"title":1204},"\u002Fchangelog\u002F2025\u002F08\u002Fhttp-cors","Configure HTTP CORS",{"path":1206,"title":1207},"\u002Fchangelog\u002F2025\u002F08\u002Fsubflow-export","Export SubFlow as Node-RED module",{"path":1209,"title":1210},"\u002Fchangelog\u002F2025\u002F08\u002Ftables-assistant","FlowFuse Tables with a little help from the Assistant",{"path":1212,"title":1213},"\u002Fchangelog\u002F2025\u002F09\u002Fexpose-saml-groups-to-dashboard","Allow SSO groups to be shared with the Node-RED Dashboard",{"path":1215,"title":1216},"\u002Fchangelog\u002F2025\u002F09\u002Finline-assist","FlowFuse Expert can help you write code",{"path":1218,"title":1219},"\u002Fchangelog\u002F2025\u002F09\u002Fretiring-flowforge-device-agent","No more @flowforge\u002Fflowforge-device-agent releases",{"path":1221,"title":1222},"\u002Fchangelog\u002F2025\u002F09\u002Frevised-instance-snapshot-ui","Streamlined Snapshot Management",{"path":1224,"title":1225},"\u002Fchangelog\u002F2025\u002F09\u002Fteam-broker-async-api","Capture Async API data from FlowFuse Team Broker",{"path":1227,"title":1228},"\u002Fchangelog\u002F2025\u002F10\u002Fapplication-level-rbac","Application-level access control for Enterprise teams",{"path":1230,"title":1231},"\u002Fchangelog\u002F2025\u002F10\u002Fbulk-device-group-assignment","Easier Access to Bulk Device Group Management",{"path":1233,"title":1234},"\u002Fchangelog\u002F2025\u002F10\u002Fduplicate-instances-across-applications","Duplicate Instances Across Different Applications",{"path":1236,"title":1237},"\u002Fchangelog\u002F2025\u002F10\u002Fimport-flows-on-instance-creation","Import flows during instance creation",{"path":1239,"title":1240},"\u002Fchangelog\u002F2025\u002F10\u002Fmcp-nodes","FlowFuse MCP Server Nodes",{"path":1242,"title":1243},"\u002Fchangelog\u002F2025\u002F10\u002Fonnx-nodes","FlowFuse AI Nodes",{"path":1245,"title":1246},"\u002Fchangelog\u002F2025\u002F10\u002Fsettings-page-device-group-management","Device Group Management from Settings Page",{"path":1248,"title":1249},"\u002Fchangelog\u002F2025\u002F11\u002Fff-expert-update","FlowFuse Expert Update",{"path":1251,"title":1252},"\u002Fchangelog\u002F2025\u002F11\u002Fminimum-nodejs-version","Node.js v20 Minimum Version Requirement",{"path":1254,"title":1255},"\u002Fchangelog\u002F2025\u002F11\u002Fsso-session","SSO control over Session life",{"path":1257,"title":1258},"\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights","FlowFuse Expert: Now with MCP-Powered Insights",{"path":1260,"title":1261},"\u002Fchangelog\u002F2025\u002F12\u002Fscheduled-maintenance","Scheduled Maintenance Mode",{"path":1263,"title":1264},"\u002Fchangelog\u002F2026\u002F01\u002Fdevice-agent-containers","Device Agent Docker Containers updated",{"path":1266,"title":1267},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-manage-palette","FlowFuse Expert: Enhanced Palette Integration",{"path":1269,"title":1270},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-nr-actions","FlowFuse Expert: Integration with Node-RED",{"path":1272,"title":1273},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-palette-queries","FlowFuse Expert: Palette Queries",{"path":1275,"title":1276},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-select-flows","FlowFuse Expert: Ask about your flows",{"path":1278,"title":1279},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-rbacs","FlowFuse Expert: MCP-Powered Insights with RBACs",{"path":1281,"title":1282},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-security","FlowFuse Expert: MCP-Powered Insights",{"path":1284,"title":1285},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options","Set Node.js Options for Remote Instances",{"path":1287,"title":1288},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context","FlowFuse Expert: Helping you make sense of your debug log",{"path":1290,"title":1291},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner","FlowFuse Expert: Never Miss an Update",{"path":1293,"title":1294},"\u002Fchangelog\u002F2026\u002F02\u002Fha-instance-rolling-restart","HA Hosted Instance Rolling Restart",{"path":1296,"title":1297},"\u002Fchangelog\u002F2026\u002F02\u002Fremote-instances-immersive-editor","Immersive Mode for Remote Instances",{"path":1299,"title":1300},"\u002Fchangelog\u002F2026\u002F02\u002Frestoring-snapshots-to-remote-instances","Restoring snapshots to developer-mode Remote Instances",{"path":1302,"title":1303},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops","Azure DevOps Pipeline support",{"path":1305,"title":1306},"\u002Fchangelog\u002F2026\u002F03\u002Fdeveloper-mode-in-immersive-editor","Developer Mode Now Accessible from the Immersive Editor",{"path":1308,"title":1309},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title","Embedded Editor Now Shows Active Tab",{"path":1311,"title":1312},"\u002Fchangelog\u002F2026\u002F03\u002Fmarch-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on March 28th, 2026",{"path":1314,"title":1315},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor","View Snapshot Details in the Immersive Editor",{"path":1317,"title":1318},"\u002Fchangelog\u002F2026\u002F04\u002Fexpert-action-links","FlowFuse expert action links",{"path":1320,"title":1321},"\u002Fchangelog\u002F2026\u002F04\u002Fhosted-instance-url-env-var","Hosted Instances know their own URL",{"path":1323,"title":580},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer",{"path":1325,"title":1326},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer","Richer snapshot comparison view",{"path":1328,"title":1329},"\u002Fchangelog\u002F2026\u002F05\u002Fai-opt-out","AI Feature Opt-Out for Teams",{"path":1331,"title":1332},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building","FlowFuse Expert Builds Your Application",{"path":1334,"title":1335},"\u002Fchangelog\u002F2026\u002F05\u002Fsingle-sso-provider","Single SSO provider for all users",{"path":1337,"title":1338},"\u002Fchangelog\u002F2026\u002F06\u002Fdark-mode","Dark Mode",{"path":1340,"title":1341},"\u002Fchangelog\u002F2026\u002F06\u002Fdevice-agent-v4-released","Device Agent v4 released",{"path":1343,"title":1344},"\u002Fchangelog\u002F2026\u002F06\u002Fgeneric-git-server-support","Connect Pipelines to Any Git Server",{"path":1346,"title":1347},"\u002Fchangelog\u002F2026\u002F06\u002Fjuly-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on July 11th, 2026",{"path":1349,"title":1350},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups","Application Roles from SSO Groups",{"path":1352,"title":1353},"\u002Fchangelog\u002F2026\u002F07\u002Fdevice-agent-onboarding","Getting started with FlowFuse straight from the terminal",{"path":1355,"title":1356},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-enhancements","FlowFuse Expert Enhancements",{"path":1358,"title":1359},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation","FlowFuse Expert Can Now Work With Your Tables",{"path":1361,"title":1362},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats","Team Scoped Personal Access Tokens",{"path":1364,"title":1365},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards","A Dedicated Home for Your Dashboards",[],1786105903387]