[{"data":1,"prerenderedAt":1450},["ShallowReactive",2],{"blog-\u002Fblog\u002F2025\u002F12\u002Fwhat-is-mttf":3,"featureCatalog":520,"changelog-titles":915,"blog-all-for-related":1449},{"id":4,"title":5,"authors":6,"body":8,"cta":499,"date":500,"description":501,"extension":502,"features":499,"image":503,"lastUpdated":499,"meta":504,"navigation":510,"path":511,"release":499,"seo":512,"sitemap":513,"stem":514,"subtitle":515,"tags":516,"tldr":518,"video":499,"__hash__":519},"blog\u002Fblog\u002F2025\u002F12\u002Fwhat-is-mttf.md","Mean Time to Failure (MTTF): Formula, Calculation, MTTF vs MTBF vs MTTR, and More",[7],"sumit-shinde",{"type":9,"value":10,"toc":476},"minimark",[11,15,18,21,24,29,41,44,73,79,83,86,97,107,112,115,121,124,128,131,134,138,141,147,151,155,158,192,199,204,207,211,214,217,220,226,231,234,238,241,244,247,251,254,327,333,337,354,357,361,364,373,376,380,383,386,389,392,396,399,425,429,432,435,438,441],[12,13,14],"p",{},"When a critical motor bearing assembly fails after just 6 months, half its rated lifespan, maintenance teams face a fundamental question: \"How long should this component actually last?\"",[12,16,17],{},"Mean Time to Failure (MTTF) provides the answer. It measures the average operational lifetime of non-repairable components before permanent failure, enabling data-driven decisions about replacement timing, spare parts inventory, and component selection.",[12,19,20],{},"MTTF emerged as a core reliability engineering metric in the 1950s during the development of military and aerospace reliability theory. Today, it remains essential across industries where component reliability determines operational success, from semiconductor manufacturing to data centers to industrial automation.",[12,22,23],{},"This guide explains what MTTF measures, how to calculate it correctly with real examples, how it differs from related metrics, and how to use MTTF data for strategic maintenance planning.",[25,26,28],"h2",{"id":27},"what-is-mean-time-to-failure-mttf","What is Mean Time to Failure (MTTF)?",[12,30,31,32,36,37,40],{},"Mean Time to Failure (MTTF) is a reliability metric that measures ",[33,34,35],"strong",{},"the average operating time of a non-repairable component before it fails permanently",". Once the component fails, it is ",[33,38,39],{},"replaced, not repaired",".",[12,42,43],{},"MTTF is commonly used for items such as light bulbs, batteries, sealed bearings, hard drives, electronic modules, and disposable filters. It helps teams understand how long a part typically lasts under normal operating conditions, enabling better planning for replacements, spare parts management, and reduction of unexpected downtime.",[12,45,46,47,56,57,64,65,72],{},"MTTF is a core concept in reliability engineering and is widely used in maintenance planning, lifecycle cost analysis, and dependability studies. It is formally supported by industry standards such as ",[33,48,49],{},[50,51,55],"a",{"href":52,"rel":53},"https:\u002F\u002Fwww.sre.org\u002Fmil-hdbk-217-the-perceived-standard\u002F",[54],"nofollow","MIL-HDBK-217",", ",[33,58,59],{},[50,60,63],{"href":61,"rel":62},"https:\u002F\u002Fstandards.ieee.org\u002Fieee\u002F1413\u002F3764\u002F",[54],"IEEE Standard 1413",", and ",[33,66,67],{},[50,68,71],{"href":69,"rel":70},"https:\u002F\u002Fwebstore.iec.ch\u002Fen\u002Fpublication\u002F1294",[54],"IEC 60300-3-1",", which provide guidance on reliability and dependability analysis across the equipment life cycle.",[12,74,75,78],{},[33,76,77],{},"Important",": MTTF represents a statistical average, some components will fail earlier while others last longer. Use it for planning and forecasting, not for predicting exact failure times of individual components.",[25,80,82],{"id":81},"mean-time-to-failure-mttf-formula","Mean Time to Failure (MTTF) Formula",[12,84,85],{},"The MTTF calculation is straightforward:",[87,88,93],"pre",{"className":89,"code":91,"language":92},[90],"language-text","MTTF = Total Operating Time \u002F Number of Failures\n","text",[94,95,91],"code",{"__ignoreMap":96},"",[12,98,99,102,103,106],{},[33,100,101],{},"Total Operating Time"," is the sum of all hours every unit ran before failing. ",[33,104,105],{},"Number of Failures"," is how many units failed permanently and were replaced (not repaired).",[108,109,111],"h3",{"id":110},"example","Example",[12,113,114],{},"You have 50 light bulbs. Ten bulbs burn out after 8,000 hours (that's 80,000 total hours). Fifteen more fail at 10,000 hours (150,000 hours). The remaining 25 bulbs last 12,000 hours each (300,000 hours). Add it all up and you get 530,000 hours across 50 bulbs.",[12,116,117,118],{},"MTTF = 530,000 \u002F 50 = ",[33,119,120],{},"10,600 hours",[12,122,123],{},"This means on average, each bulb lasts 10,600 hours before it fails.",[108,125,127],{"id":126},"quick-shortcuts","Quick Shortcuts",[12,129,130],{},"If all your components run the same amount of time before the test ends, you can use this shortcut: multiply the number of units by hours run, then divide by failures observed.",[12,132,133],{},"The failure rate is simply the inverse of MTTF. If MTTF is 10,000 hours, your failure rate is 0.0001 failures per hour, which means you expect 1 failure every 10,000 hours.",[108,135,137],{"id":136},"what-this-formula-assumes","What This Formula Assumes",[12,139,140],{},"The basic MTTF formula works when you're tracking non-repairable parts, failures occur randomly during their normal lifespan, and operating conditions remain roughly consistent. You also need enough failures to make the average meaningful, ideally 30 or more data points.",[12,142,143,146],{},[33,144,145],{},"When basic MTTF doesn't apply",": If you have components still running at the end of your observation period, or if failure patterns follow a bathtub curve (high early failures, stable middle period, increasing wear-out failures), you'll need advanced statistical methods like Weibull analysis or censored data techniques.",[25,148,150],{"id":149},"how-to-calculate-mean-time-to-failure-mttf","How to Calculate Mean Time to Failure (MTTF)",[108,152,154],{"id":153},"example-1-data-center-hard-drives","Example 1: Data Center Hard Drives",[12,156,157],{},"A data center operates 100 identical hard drives. Over 18 months of operation, they track which drives fail and need replacement:",[159,160,161,168,174,180,186],"ul",{},[162,163,164,167],"li",{},[33,165,166],{},"Month 6:"," 3 drives fail after 4,380 hours each = 13,140 hours",[162,169,170,173],{},[33,171,172],{},"Month 9:"," 5 drives fail after 6,570 hours each = 32,850 hours",[162,175,176,179],{},[33,177,178],{},"Month 12:"," 4 drives fail after 8,760 hours each = 35,040 hours",[162,181,182,185],{},[33,183,184],{},"Month 15:"," 6 drives fail after 10,950 hours each = 65,700 hours",[162,187,188,191],{},[33,189,190],{},"Month 18:"," 7 drives fail after 13,140 hours each = 91,980 hours",[12,193,194,195,198],{},"Total operating time = 238,710 hours",[196,197],"br",{},"\nTotal failures = 25 drives",[12,200,201],{},[33,202,203],{},"MTTF = 238,710 \u002F 25 = 9,548 hours",[12,205,206],{},"This tells the data center they can expect each hard drive to last roughly 9,548 hours (just over 1 year). The remaining 75 drives are still running, so the actual MTTF might be higher, but this gives them a working estimate for planning replacements and maintaining spare inventory.",[108,208,210],{"id":209},"example-2-manufacturing-plant-conveyor-belts","Example 2: Manufacturing Plant Conveyor Belts",[12,212,213],{},"A factory runs 20 conveyor lines, each with identical drive belts. The maintenance team tracks belt failures over 2 years:",[12,215,216],{},"All 20 belts start fresh. After 8,000 hours of operation, 4 belts have failed. After 12,000 hours, 6 more fail. After 16,000 hours, another 5 fail. The remaining 5 belts are still running at the 2-year mark (17,520 hours).",[12,218,219],{},"Simplified calculation using all belts (including those still running):",[12,221,222,223,225],{},"Total time = 20 belts × 17,520 hours = 350,400 hours",[196,224],{},"\nTotal failures = 15 belts",[12,227,228],{},[33,229,230],{},"MTTF = 350,400 \u002F 15 = 23,360 hours",[12,232,233],{},"The plant now knows these belts typically last about 23,360 hours (roughly 2.7 years in continuous operation). They can schedule preventive replacements at around 20,000 hours to avoid unexpected breakdowns during production runs.",[25,235,237],{"id":236},"common-calculation-mistakes-to-avoid","Common Calculation Mistakes to Avoid",[12,239,240],{},"One of the most common mistakes when calculating MTTF is confusing calendar time with actual operating hours. A component that runs only part of the day will accumulate operating hours much more slowly than calendar time passes, so it’s critical to measure true runtime rather than elapsed days or months. Another frequent error is including repaired equipment in MTTF calculations. If a component is fixed and returned to service, it belongs in MTBF calculations, not MTTF, which only applies to items that are permanently replaced after failure.",[12,242,243],{},"Small sample sizes also lead to misleading results. Calculating MTTF from just a few failures can produce numbers that fluctuate widely and don’t reflect real performance. In practice, at least 20 to 30 failures are needed to produce meaningful averages, with larger datasets providing more reliable insight. Operating conditions are another major source of error. The same component can have very different lifespans depending on factors like temperature, dust, vibration, and load, so MTTF values should always be compared under similar conditions.",[12,245,246],{},"Finally, MTTF is often misunderstood as a guaranteed lifespan. It is only an average. Some components will fail much earlier than the MTTF value, while others will last significantly longer. Maintenance planning should account for this natural variation instead of treating MTTF as a minimum life expectancy.",[25,248,250],{"id":249},"difference-between-mttf-mtbf-and-mttr","Difference Between MTTF, MTBF, and MTTR",[12,252,253],{},"These three acronyms measure fundamentally different aspects of reliability:",[255,256,257,275],"table",{},[258,259,260],"thead",{},[261,262,263,267,270,273],"tr",{},[264,265,266],"th",{},"Metric",[264,268,269],{},"What It Measures",[264,271,272],{},"Use For",[264,274,111],{},[276,277,278,295,311],"tbody",{},[261,279,280,286,289,292],{},[281,282,283],"td",{},[33,284,285],{},"MTTF",[281,287,288],{},"Average time until permanent failure",[281,290,291],{},"Non-repairable items replaced when they fail",[281,293,294],{},"Light bulbs, batteries, hard drives, sealed bearings",[261,296,297,302,305,308],{},[281,298,299],{},[33,300,301],{},"MTBF",[281,303,304],{},"Average time between repair events",[281,306,307],{},"Repairable systems fixed and returned to service",[281,309,310],{},"Motors, pumps, HVAC systems, vehicles",[261,312,313,318,321,324],{},[281,314,315],{},[33,316,317],{},"MTTR",[281,319,320],{},"Average time to complete repairs",[281,322,323],{},"Any equipment requiring repair",[281,325,326],{},"All repairable systems",[12,328,329,332],{},[33,330,331],{},"The key distinction",": MTTF applies when you discard and replace it. MTBF applies when you fix it and keep using it. MTTR tells you how long the fixing takes.",[108,334,336],{"id":335},"calculation-formulas","Calculation Formulas",[159,338,339,344,349],{},[162,340,341,343],{},[33,342,285],{}," = Total operating time ÷ Number of permanent failures",[162,345,346,348],{},[33,347,301],{}," = Total operating time ÷ Number of repair events (excluding repair time)",[162,350,351,353],{},[33,352,317],{}," = Total repair time ÷ Number of repairs",[12,355,356],{},"A facility might track MTTF for LED bulbs in their fixtures (replace when burned out) while tracking MTBF for the fixtures themselves (repair when they fail). Both metrics serve different planning purposes.",[25,358,360],{"id":359},"where-to-find-reliable-mttf-data","Where to Find Reliable MTTF Data",[12,362,363],{},"Manufacturer datasheets are a useful starting point, but they should not be treated as definitive. Published MTTF values are usually measured under controlled laboratory conditions with clean environments, ideal installation, stable temperatures, and moderate loads. Real operating environments are rarely this consistent, so actual component life in the field is often shorter or more variable than datasheet values suggest.",[12,365,366,367,372],{},"Industry reliability databases provide more realistic benchmarks. Standards such as ",[50,368,371],{"href":369,"rel":370},"https:\u002F\u002Fwww.iso.org\u002Fstandard\u002F64076.html",[54],"ISO 14224"," compile failure and maintenance data from hundreds of similar facilities, offering reference values that reflect real-world operating conditions rather than ideal test scenarios. These benchmarks are helpful for comparison, but they still represent averages across many sites and may not fully match your specific environment.",[12,374,375],{},"The most reliable MTTF data comes from your own facility. By tracking installation dates and failure times, you can build site-specific reliability data that reflects your actual loads, temperatures, maintenance practices, and environmental conditions. After collecting data from 20 to 30 failures, your internal MTTF values will often be more accurate and actionable than any external source.",[25,377,379],{"id":378},"using-mttf-for-better-maintenance-planning","Using MTTF for Better Maintenance Planning",[12,381,382],{},"MTTF delivers the most value when it supports proactive maintenance decisions rather than reactive repairs. When using MTTF for maintenance planning, the objective is to replace components before failures disrupt production. For example, if a component typically fails around 20,000 operating hours, scheduling replacement at 15,000 hours during planned maintenance windows can prevent unexpected breakdowns and emergency interventions. Replacing parts slightly early is often far less costly than absorbing unplanned downtime.",[12,384,385],{},"MTTF also plays a critical role in spare parts optimization, particularly in manufacturing and industrial automation environments where many identical components operate continuously across multiple machines. By estimating expected failures per year based on operating hours and installed quantities, maintenance teams can stock enough spares to meet short-term demand without tying up excessive working capital. Even modest improvements in MTTF-based inventory planning can significantly reduce both downtime risk and excess inventory.",[12,387,388],{},"Supplier selection becomes more objective when MTTF data is used instead of relying solely on datasheet claims. In real-world maintenance planning scenarios, teams can compare components based on total cost per operating hour rather than purchase price alone. A higher-priced component with a longer operating life may ultimately be more economical once labor costs, downtime impact, and replacement frequency are considered.",[12,390,391],{},"Finally, MTTF helps reveal the true cost drivers within maintenance budgets across manufacturing and industrial automation systems. By combining replacement costs, downtime impact, and failure frequency, teams can identify which components contribute most to annual maintenance spend. Incremental improvements in component reliability often translate into substantial cost savings while also improving overall equipment availability.",[25,393,395],{"id":394},"when-mttf-isnt-the-right-metric","When MTTF Isn't the Right Metric",[12,397,398],{},"MTTF has limitations. Don't use it when:",[159,400,401,407,413,419],{},[162,402,403,406],{},[33,404,405],{},"Equipment gets repaired, not replaced"," - Use MTBF instead",[162,408,409,412],{},[33,410,411],{},"Failure patterns show wear-out"," - Components with bathtub curves (high early failures, then stable, then increasing wear-out failures) need Weibull analysis",[162,414,415,418],{},[33,416,417],{},"You need real-time reliability"," - MTTF describes past performance; it doesn't predict when the next specific unit will fail",[162,420,421,424],{},[33,422,423],{},"Safety-critical applications"," - Statistical averages aren't appropriate for systems where a single failure could cause injury or environmental harm. Use fault tree analysis or failure mode effects analysis instead",[25,426,428],{"id":427},"bottom-line","Bottom Line",[12,430,431],{},"Stop guessing when parts will fail. Start tracking installation dates and failure times today. After 20-30 failures, you'll have better data than any manufacturer spec sheet, data that reflects your actual operating conditions, not laboratory ideals.",[12,433,434],{},"Use that data to schedule replacements during planned downtime rather than waiting for 2am emergency breakdowns. Stock the right number of spares, not too many tying up working capital, not too few forcing expedited shipping and production delays. Compare suppliers based on actual performance in your facility, not who's cheapest on paper.",[12,436,437],{},"The math is straightforward: unplanned breakdowns cost 3-5x more than scheduled replacements when you factor in overtime labor, rush parts shipping, and lost production. MTTF transforms reactive firefighting into predictable maintenance.",[12,439,440],{},"Your facility is unique. Your conditions, loads, and environment create a reliability profile unlike any other operation. The only MTTF numbers that truly matter are the ones you measure yourself.",[12,442,443,444,448,449,56,453,457,458,462,463,56,467,64,471,475],{},"As your equipment base grows, manual tracking becomes cumbersome. ",[50,445,447],{"href":446},"\u002F","FlowFuse"," automates this by connecting to ",[50,450,452],{"href":451},"\u002Fblog\u002F2025\u002F12\u002Fwhat-is-plc\u002F","PLCs",[50,454,456],{"href":455},"\u002Fsolutions\u002Fscada\u002F","SCADA"," systems, ",[50,459,461],{"href":460},"\u002Fsolutions\u002Fmes\u002F","MES"," platforms, and your CMMS, pulling operating hours directly from equipment through industrial protocols like ",[50,464,466],{"href":465},"\u002Fnode-red\u002Fprotocol\u002Fmodbus\u002F","Modbus",[50,468,470],{"href":469},"\u002Fblog\u002F2025\u002F07\u002Freading-and-writing-plc-data-using-opc-ua\u002F","OPC UA",[50,472,474],{"href":473},"\u002Fblog\u002F2025\u002F10\u002Fusing-ethernet-ip-with-flowfuse\u002F","EtherNet\u002FIP",", then capturing failure events to recalculate MTTF in real-time across your entire facility.",{"title":96,"searchDepth":477,"depth":477,"links":478},4,[479,481,487,491,492,495,496,497,498],{"id":27,"depth":480,"text":28},2,{"id":81,"depth":480,"text":82,"children":482},[483,485,486],{"id":110,"depth":484,"text":111},3,{"id":126,"depth":484,"text":127},{"id":136,"depth":484,"text":137},{"id":149,"depth":480,"text":150,"children":488},[489,490],{"id":153,"depth":484,"text":154},{"id":209,"depth":484,"text":210},{"id":236,"depth":480,"text":237},{"id":249,"depth":480,"text":250,"children":493},[494],{"id":335,"depth":484,"text":336},{"id":359,"depth":480,"text":360},{"id":378,"depth":480,"text":379},{"id":394,"depth":480,"text":395},{"id":427,"depth":480,"text":428},null,"2025-12-29","Learn what Mean Time to Failure (MTTF) means, how to calculate it with real examples, industry benchmarks, and how to use MTTF data to improve equipment reliability and maintenance planning.","md","\u002Fblog\u002F2025\u002F12\u002Fimages\u002Fwhat-is-mttf.png",{"keywords":505,"excerpt":506},"MTTF, mean time to failure, MTTF formula, MTTF calculation, how to calculate MTTF, MTTF vs MTBF, MTTF vs MTTR, equipment reliability, failure prediction, reliability metrics, asset management",{"type":9,"value":507},[508],[12,509,14],{},true,"\u002Fblog\u002F2025\u002F12\u002Fwhat-is-mttf",{"title":5,"description":501},{"loc":511},"blog\u002F2025\u002F12\u002Fwhat-is-mttf","Understanding equipment reliability and predicting failure patterns",[517],"flowfuse","Mean Time to Failure (MTTF) measures the average operating lifetime of non-repairable components such as light bulbs, batteries, and electronic modules before permanent failure requiring replacement, not repair. The formula is simply total operating time divided by number of failures, providing a statistical average useful for planning preventive replacements, spare parts inventory, and procurement decisions. MTTF differs from MTBF (which applies to repairable systems) and MTTR (which measures repair time).","fvxn9DXDC0u7ISYX_2-5VSDyVHrPiRVGa6LZ754Yt68",{"id":521,"extension":522,"meta":523,"sections":524,"stem":913,"__hash__":914},"featureCatalog\u002Ffeature-catalog.yml","yml",{},[525,576,677,739,816,895],{"id":526,"title":527,"features":528},"ai-automation","AI & Automation",[529,539,549,559,565,571],{"id":530,"title":531,"description":532,"docsLink":533,"changelog":534,"tiers":538},"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",[535],{"url":536,"release":537},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner\u002F","2.28",{"edge":510,"hub":510,"fleet":510},{"id":540,"title":541,"description":542,"docsLink":543,"changelog":544,"subfeature":510,"showOnPricing":547,"tiers":548},"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",[545],{"url":546,"release":537},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context\u002F",false,{"edge":510,"hub":510,"fleet":510},{"id":550,"title":551,"description":552,"docsLink":553,"changelog":554,"subfeature":510,"showOnPricing":547,"tiers":558},"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",[555],{"url":556,"release":557},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building\u002F","2.30",{"edge":510,"hub":510,"fleet":510},{"id":560,"title":561,"description":562,"docsLink":563,"subfeature":510,"beta":510,"showOnPricing":547,"tiers":564},"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":510,"hub":510,"fleet":510},{"id":566,"title":567,"description":568,"docsLink":569,"tiers":570},"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":510,"hub":510,"fleet":510},{"id":572,"title":573,"description":574,"tiers":575},"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":510,"hub":510,"fleet":510},{"id":577,"title":578,"features":579},"build","Build",[580,586,592,602,608,614,618,624,630,638,644,648,652,661,669],{"id":581,"title":582,"description":583,"docsLink":584,"tiers":585},"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":510,"hub":547,"fleet":510},{"id":587,"title":588,"description":589,"docsLink":590,"tiers":591},"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":510,"hub":510,"fleet":510},{"id":593,"title":594,"description":595,"docsLink":596,"changelog":597,"tiers":601},"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",[598],{"url":599,"release":600},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation\u002F","2.33",{"edge":510,"hub":510,"fleet":510},{"id":603,"title":604,"description":605,"docsLink":606,"tiers":607},"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":510,"hub":510,"fleet":510},{"id":609,"title":610,"description":611,"docsLink":612,"showOnPricing":547,"tiers":613},"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":510,"hub":510,"fleet":510},{"id":615,"title":616,"showOnPricing":547,"tiers":617},"static-assets","Static Assets",{"edge":510,"hub":510,"fleet":510},{"id":619,"title":620,"description":621,"docsLink":622,"tiers":623},"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":510,"hub":510,"fleet":510},{"id":625,"title":626,"description":627,"docsLink":628,"tiers":629},"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":510,"hub":510,"fleet":510},{"id":631,"title":632,"description":633,"changelog":634,"subfeature":510,"showOnPricing":547,"tiers":637},"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.",[635],{"url":636,"release":600},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards\u002F",{"edge":510,"hub":510,"fleet":510},{"id":639,"title":640,"description":641,"docsLink":642,"tiers":643},"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":510,"hub":510,"fleet":510},{"id":645,"title":646,"subfeature":510,"showOnPricing":547,"tiers":647},"blueprints-ot-apps","Blueprints - OT APPS",{"edge":510,"hub":547,"fleet":510},{"id":649,"title":650,"subfeature":510,"showOnPricing":547,"tiers":651},"blueprints-it-apps","Blueprints - IT APPS",{"edge":547,"hub":510,"fleet":547},{"id":653,"title":654,"description":655,"changelog":656,"showOnPricing":547,"tiers":660},"immersive-editor-snapshots","Snapshot Details in Immersive Editor","View and manage snapshot details directly inside the immersive editor without leaving your editing session.",[657],{"url":658,"release":659},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor\u002F","2.29",{"edge":510,"hub":510,"fleet":510},{"id":662,"title":663,"description":664,"changelog":665,"showOnPricing":547,"tiers":668},"immersive-editor-drawer","Customisable Immersive Editor Drawer","Pin, move, resize, or full-screen the immersive editor drawer. Your preferences are remembered between sessions.",[666],{"url":667,"release":557},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer\u002F",{"edge":510,"hub":510,"fleet":510},{"id":670,"title":671,"description":672,"changelog":673,"showOnPricing":547,"tiers":676},"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.",[674],{"url":675,"release":659},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title\u002F",{"edge":510,"hub":510,"fleet":510},{"id":678,"title":679,"features":680},"deploy","Deploy",[681,687,696,702,708,714,720,726,731],{"id":682,"title":683,"description":684,"docsLink":685,"tiers":686},"hosted-instances","Cloud Instances","Run Node-RED instances managed and hosted by FlowFuse.","\u002Fdocs\u002Fuser\u002Fintroduction\u002F#creating-a-node-red-instance",{"edge":510,"hub":510,"fleet":510},{"id":688,"title":689,"description":690,"docsLink":691,"changelog":692,"tiers":695},"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",[693],{"url":694,"release":537},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options\u002F",{"edge":510,"hub":547,"fleet":510},{"id":697,"title":698,"description":699,"docsLink":700,"tiers":701},"custom-hostnames","Custom Hostnames","Access your Node-RED application via your own domain name.","\u002Fdocs\u002Fuser\u002Fcustom-hostnames\u002F",{"edge":547,"hub":510,"fleet":547},{"id":703,"title":704,"description":705,"docsLink":706,"tiers":707},"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":510,"hub":547,"fleet":510},{"id":709,"title":710,"description":711,"docsLink":712,"showOnPricing":547,"tiers":713},"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":510,"hub":510,"fleet":510},{"id":715,"title":716,"description":717,"docsLink":718,"tiers":719},"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":510,"hub":510,"fleet":510},{"id":721,"title":722,"description":723,"docsLink":724,"tiers":725},"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":547,"hub":510,"fleet":547},{"id":727,"title":728,"description":729,"docsLink":724,"subfeature":510,"showOnPricing":547,"tiers":730},"git-integration-github","GitHub","Push and pull snapshots to GitHub repositories through DevOps Pipeline Git Stages.",{"edge":547,"hub":510,"fleet":547},{"id":732,"title":733,"description":734,"docsLink":724,"changelog":735,"subfeature":510,"showOnPricing":547,"tiers":738},"git-integration-azure","Azure DevOps","Push and pull snapshots to Azure DevOps repositories through DevOps Pipeline Git Stages.",[736],{"url":737,"release":659},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops\u002F",{"edge":547,"hub":510,"fleet":547},{"id":740,"title":741,"features":742},"operate-maintain","Operate & Maintain",[743,749,755,760,768,772,776,781,787,793,798,804,808,812],{"id":744,"title":745,"description":746,"docsLink":747,"tiers":748},"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":510,"hub":510,"fleet":510},{"id":750,"title":751,"description":752,"docsLink":753,"subfeature":510,"showOnPricing":547,"tiers":754},"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":510,"hub":510,"fleet":510},{"id":756,"title":757,"description":758,"docsLink":753,"subfeature":510,"showOnPricing":547,"tiers":759},"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":510,"hub":510,"fleet":510},{"id":761,"title":762,"description":763,"changelog":764,"subfeature":510,"showOnPricing":547,"tiers":767},"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.",[765],{"url":766,"release":659},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer\u002F",{"edge":510,"hub":510,"fleet":510},{"id":769,"title":770,"subfeature":510,"showOnPricing":547,"tiers":771},"version-history-timeline","Version History Timeline",{"edge":510,"hub":510,"fleet":510},{"id":773,"title":774,"tiers":775},"unlimited-workflow-executions","Unlimited Workflow Executions",{"edge":510,"hub":510,"fleet":510},{"id":777,"title":778,"description":779,"tiers":780},"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":510,"hub":547,"fleet":510},{"id":782,"title":783,"description":784,"docsLink":785,"tiers":786},"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":510,"hub":547,"fleet":510},{"id":788,"title":789,"description":790,"docsLink":791,"tiers":792},"high-availability","High Availability","Leverage horizontal scaling for reliable and scalable processing of your data through Node-RED.","\u002Fdocs\u002Fuser\u002Fhigh-availability\u002F",{"edge":547,"hub":510,"fleet":547},{"id":794,"title":795,"description":796,"tiers":797},"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":510,"hub":510,"fleet":510},{"id":799,"title":800,"description":801,"docsLink":802,"subfeature":510,"showOnPricing":547,"tiers":803},"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":510,"hub":510,"fleet":510},{"id":805,"title":806,"subfeature":510,"showOnPricing":547,"tiers":807},"email-alerts","Email Alerts",{"edge":510,"hub":510,"fleet":510},{"id":809,"title":810,"showOnPricing":547,"tiers":811},"api-debug-length-limit","API\u002FDebug Length Limit",{"edge":510,"hub":510,"fleet":510},{"id":813,"title":814,"tiers":815},"protected-instances","Protected Instances",{"edge":547,"hub":510,"fleet":547},{"id":817,"title":818,"features":819},"govern-secure","Govern and Secure",[820,829,835,841,846,852,858,864,872,878,884,890],{"id":821,"title":822,"description":823,"docsLink":824,"changelog":825,"tiers":828},"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",[826],{"url":827,"release":600},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups\u002F",{"edge":510,"hub":510,"fleet":510},{"id":830,"title":831,"description":832,"docsLink":833,"tiers":834},"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":510,"hub":510,"fleet":510},{"id":836,"title":837,"description":838,"docsLink":839,"tiers":840},"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":547,"hub":510,"fleet":510},{"id":842,"title":843,"description":844,"tiers":845},"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":510,"hub":547,"fleet":547},{"id":847,"title":848,"description":849,"docsLink":850,"tiers":851},"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":510,"hub":510,"fleet":510},{"id":853,"title":854,"description":855,"docsLink":856,"tiers":857},"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":510,"hub":510,"fleet":510},{"id":859,"title":860,"description":861,"docsLink":862,"subfeature":510,"showOnPricing":547,"tiers":863},"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":510,"hub":510,"fleet":510},{"id":865,"title":866,"description":867,"changelog":868,"subfeature":510,"showOnPricing":547,"tiers":871},"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.",[869],{"url":870,"release":600},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats\u002F",{"edge":510,"hub":510,"fleet":510},{"id":873,"title":874,"description":875,"docsLink":876,"showOnPricing":547,"tiers":877},"team-members","Team Members","Invite multiple team members to collaborate on the same Node-RED flows.","\u002Fdocs\u002Fuser\u002Fteam\u002F#teams",{"edge":510,"hub":510,"fleet":510},{"id":879,"title":880,"description":881,"docsLink":882,"showOnPricing":547,"tiers":883},"endpoint-security","Endpoint Security","Secure HTTP endpoints for hosted Node-RED instances using FlowFuse credentials.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#security",{"edge":510,"hub":510,"fleet":510},{"id":885,"title":886,"description":887,"docsLink":888,"tiers":889},"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":547,"hub":510,"fleet":547},{"id":891,"title":892,"description":893,"tiers":894},"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":547,"hub":510,"fleet":547},{"id":896,"title":897,"features":898},"support","Support",[899,904,908],{"id":900,"title":901,"docsLink":902,"tiers":903},"installation-support","Installation Support","\u002Fdocs\u002Finstall\u002Fintroduction\u002F#do-you-need-help-installation-service",{"edge":510,"hub":510,"fleet":510},{"id":905,"title":906,"showOnPricing":547,"tiers":907},"live-chat-support","Live Chat Support",{"edge":510,"hub":510,"fleet":510},{"id":909,"title":910,"docsLink":911,"tiers":912},"enterprise-support","Enterprise Support","\u002Fdocs\u002Fpremium-support\u002F",{"edge":510,"hub":510,"fleet":510},"feature-catalog","0AnkhTIPCECCwP9NmbTWP5HvRYx4FTSao4lG93-HaWM",[916,919,922,925,928,931,933,936,939,942,945,947,950,953,956,959,962,965,968,971,974,977,980,983,986,989,992,995,998,1001,1004,1007,1010,1013,1016,1019,1022,1025,1028,1031,1034,1037,1040,1043,1046,1049,1052,1055,1058,1060,1063,1066,1069,1072,1075,1078,1081,1083,1086,1089,1092,1095,1098,1100,1103,1106,1109,1112,1115,1118,1121,1124,1127,1130,1132,1135,1138,1141,1144,1147,1150,1153,1156,1159,1162,1165,1168,1171,1174,1176,1179,1182,1185,1188,1191,1194,1197,1200,1203,1206,1209,1212,1215,1218,1221,1224,1227,1230,1232,1235,1238,1241,1244,1247,1250,1253,1255,1258,1261,1264,1267,1270,1273,1276,1279,1282,1285,1288,1291,1294,1297,1300,1303,1306,1309,1312,1315,1318,1321,1324,1327,1330,1333,1336,1339,1342,1345,1348,1351,1354,1357,1360,1363,1366,1369,1372,1375,1378,1381,1384,1387,1390,1393,1396,1399,1402,1405,1407,1410,1413,1416,1419,1422,1425,1428,1431,1434,1437,1440,1443,1446],{"path":917,"title":918},"\u002Fchangelog\u002F2023\u002F09\u002Fcustom-node-support","Custom Node Support",{"path":920,"title":921},"\u002Fchangelog\u002F2023\u002F09\u002Fdevops-actions","DevOps Pipeline with action selection",{"path":923,"title":924},"\u002Fchangelog\u002F2023\u002F09\u002Fintroduction-enterprise-tier","Introducing the Enterprise Tier",{"path":926,"title":927},"\u002Fchangelog\u002F2023\u002F09\u002Fpipeline-api","API Endpoint for DevOps Pipeline",{"path":929,"title":930},"\u002Fchangelog\u002F2023\u002F09\u002Fsnapshots-devices","Usability improvements to Device Management",{"path":932,"title":640},"\u002Fchangelog\u002F2023\u002F10\u002Fblueprints",{"path":934,"title":935},"\u002Fchangelog\u002F2023\u002F10\u002Fcertified-nodes","Certified Nodes",{"path":937,"title":938},"\u002Fchangelog\u002F2023\u002F10\u002Fdevice-snapshot-selection","Enhanced Snapshot Selection",{"path":940,"title":941},"\u002Fchangelog\u002F2023\u002F10\u002Fpath-bug-fix","Device Agent path bug fix",{"path":943,"title":944},"\u002Fchangelog\u002F2023\u002F10\u002Fresource-alerts","Resource Monitoring in Audit Log",{"path":946,"title":831},"\u002Fchangelog\u002F2023\u002F11\u002F2fa",{"path":948,"title":949},"\u002Fchangelog\u002F2023\u002F11\u002Fdefault-editor","Device Editor enabled by default",{"path":951,"title":952},"\u002Fchangelog\u002F2023\u002F11\u002Fdevices-in-pipelines","Devices in DevOps Pipelines",{"path":954,"title":955},"\u002Fchangelog\u002F2023\u002F11\u002Fproject-nodes-devices","Project Nodes for Devices",{"path":957,"title":958},"\u002Fchangelog\u002F2023\u002F12\u002Fbilling","No Credit Card required for billing",{"path":960,"title":961},"\u002Fchangelog\u002F2023\u002F12\u002Fblueprint-selection","Blueprint Selection Update",{"path":963,"title":964},"\u002Fchangelog\u002F2023\u002F12\u002Fdevice-groups","Device Groups",{"path":966,"title":967},"\u002Fchangelog\u002F2023\u002F12\u002Femail-alerting-node-red-crash","Email Alerts for Audit Log Events",{"path":969,"title":970},"\u002Fchangelog\u002F2023\u002F12\u002Fnode-red-updated","Node-RED 3.1.3 now available",{"path":972,"title":973},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-audit-log","Introducing the Device Auditlog Feature",{"path":975,"title":976},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-groups-snapshot","Device Groups - Automatic snapshot assignment",{"path":978,"title":979},"\u002Fchangelog\u002F2024\u002F01\u002Ffleet-mode","Renaming \"Default Device Mode\" to \"Fleet Mode\"",{"path":981,"title":982},"\u002Fchangelog\u002F2024\u002F01\u002Fhelm-v2","Helm Chart v2.0",{"path":984,"title":985},"\u002Fchangelog\u002F2024\u002F01\u002Fnew-blueprints","New Blueprints added",{"path":987,"title":988},"\u002Fchangelog\u002F2024\u002F01\u002Fsecurity-updates","Security Updates",{"path":990,"title":991},"\u002Fchangelog\u002F2024\u002F01\u002Fsso-team-membership","Managing Team Membership via SSO",{"path":993,"title":994},"\u002Fchangelog\u002F2024\u002F01\u002Fstreamlined-device-assignment","Streamlined Device assignment",{"path":996,"title":997},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-auto-snapshot","Device Auto Snapshots",{"path":999,"title":1000},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-instance-audit-logs","Device Instance Audit Logging",{"path":1002,"title":1003},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-onboarding-improvements","Device Onboarding Improvements",{"path":1005,"title":1006},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-pricing-change","Pricing change for Devices",{"path":1008,"title":1009},"\u002Fchangelog\u002F2024\u002F02\u002Finstance-auto-snapshots","Instance Auto Snapshots",{"path":1011,"title":1012},"\u002Fchangelog\u002F2024\u002F02\u002Fpostgresql-upgrade","PostgreSQL Version update",{"path":1014,"title":1015},"\u002Fchangelog\u002F2024\u002F03\u002Fbearer-token-authentication","Bearer Token Authentication for Node-RED Instances",{"path":1017,"title":1018},"\u002Fchangelog\u002F2024\u002F03\u002Finstance-protection-mode","Instance Protection Mode",{"path":1020,"title":1021},"\u002Fchangelog\u002F2024\u002F03\u002Flimits-debug-payload","Configure HTTP Payload and Debug Message size",{"path":1023,"title":1024},"\u002Fchangelog\u002F2024\u002F03\u002Frestart-devices-remotly","Remote Device Restart",{"path":1026,"title":1027},"\u002Fchangelog\u002F2024\u002F04\u002Fcustom-nodes-on-devices","Custom Nodes Support on Devices",{"path":1029,"title":1030},"\u002Fchangelog\u002F2024\u002F04\u002Fdevice-auto-snapshot","Direct Dashboard Access",{"path":1032,"title":1033},"\u002Fchangelog\u002F2024\u002F04\u002Fimproving-device-groups","Improving Device Groups",{"path":1035,"title":1036},"\u002Fchangelog\u002F2024\u002F04\u002Fpricing-change","Pricing change Enterprise & Teams Tier",{"path":1038,"title":1039},"\u002Fchangelog\u002F2024\u002F04\u002Ftougher-rate-limiting","Tougher Rate Limiting on Public Routes",{"path":1041,"title":1042},"\u002Fchangelog\u002F2024\u002F05\u002Finstance-healthcheck","Customizing instance health-check settings",{"path":1044,"title":1045},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-blueprints","Blueprints added to Library",{"path":1047,"title":1048},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-flowviewer","Team Library - Flow Viewer",{"path":1050,"title":1051},"\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices","Managing Node-RED versions on Devices",{"path":1053,"title":1054},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements","Snapshot Improvements",{"path":1056,"title":1057},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements-pt3","Snapshot Upload",{"path":1059,"title":1057},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-upload",{"path":1061,"title":1062},"\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support","Running the Device Agent behind an HTTP proxy",{"path":1064,"title":1065},"\u002Fchangelog\u002F2024\u002F06\u002Flibrary-blueprints","Custom hostnames for your instances",{"path":1067,"title":1068},"\u002Fchangelog\u002F2024\u002F06\u002Fmultiline-env-vars","Multi-line Environment Variables",{"path":1070,"title":1071},"\u002Fchangelog\u002F2024\u002F06\u002Fsnapshot-flow-compare","Compare Snapshots flows",{"path":1073,"title":1074},"\u002Fchangelog\u002F2024\u002F07\u002Fapplications-search","Applications Search",{"path":1076,"title":1077},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-group-clear-snapshot","Device Groups Snapshots",{"path":1079,"title":1080},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-delete","Managing devices",{"path":1082,"title":1080},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-move",{"path":1084,"title":1085},"\u002Fchangelog\u002F2024\u002F07\u002Fedit-snapshots","Edit Snapshots",{"path":1087,"title":1088},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant","The FlowFuse Expert",{"path":1090,"title":1091},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant-json","FlowFuse Expert Writes JSON",{"path":1093,"title":1094},"\u002Fchangelog\u002F2024\u002F07\u002Fimmersive-editor","Immersive Editor Experience",{"path":1096,"title":1097},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-inbox","Notifications Inbox",{"path":1099,"title":1097},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-update",{"path":1101,"title":1102},"\u002Fchangelog\u002F2024\u002F07\u002Fpersistent-storage","Persistent Storage on FlowFuse Cloud",{"path":1104,"title":1105},"\u002Fchangelog\u002F2024\u002F07\u002Fsso","Single Sign On Updates",{"path":1107,"title":1108},"\u002Fchangelog\u002F2024\u002F08\u002Fbill-of-materials","Bill of Materials",{"path":1110,"title":1111},"\u002Fchangelog\u002F2024\u002F08\u002Fenterprise-license-update","Enforcing Enterprise Restrictions",{"path":1113,"title":1114},"\u002Fchangelog\u002F2024\u002F08\u002Fldap-sso-groups","LDAP Single Sign On Updates",{"path":1116,"title":1117},"\u002Fchangelog\u002F2024\u002F08\u002Fstatic-file-service-navigation-visibility","Static File Service Navigation and Visibility",{"path":1119,"title":1120},"\u002Fchangelog\u002F2024\u002F10\u002Fdevice-group-env-vars","Environment Variables for your Device Groups",{"path":1122,"title":1123},"\u002Fchangelog\u002F2024\u002F10\u002Fmqtt-service","MQTT Broker Service",{"path":1125,"title":1126},"\u002Fchangelog\u002F2024\u002F10\u002Fnotifications-bulk-actions","Managing Notifications",{"path":1128,"title":1129},"\u002Fchangelog\u002F2024\u002F10\u002Fsnapshot-download-upload-options","Snapshot Upload and Download Improvements",{"path":1131,"title":770},"\u002Fchangelog\u002F2024\u002F10\u002Fversion-history-timeline",{"path":1133,"title":1134},"\u002Fchangelog\u002F2024\u002F11\u002Faudit-log-hierarchy","Audit logs show hierarchical events",{"path":1136,"title":1137},"\u002Fchangelog\u002F2024\u002F11\u002Fdevice-agent-release","Device Agent 3.0 released",{"path":1139,"title":1140},"\u002Fchangelog\u002F2024\u002F11\u002Fmqtt-topic-hierarchy","MQTT Topic Hierarchy view",{"path":1142,"title":1143},"\u002Fchangelog\u002F2024\u002F11\u002Fteam-search","Team-wide search",{"path":1145,"title":1146},"\u002Fchangelog\u002F2024\u002F12\u002Fdashboad-iframe","Allow Dashboards to be embedded in iFrames",{"path":1148,"title":1149},"\u002Fchangelog\u002F2024\u002F12\u002Fdevice-editor-cache","Device Editor Access Speed Up",{"path":1151,"title":1152},"\u002Fchangelog\u002F2024\u002F12\u002Fteam-bom-timeline","Team BOM and Pipeline Views",{"path":1154,"title":1155},"\u002Fchangelog\u002F2025\u002F01\u002Ffree-tier-onboarding","New Onboarding Tour for Free Tier Users",{"path":1157,"title":1158},"\u002Fchangelog\u002F2025\u002F01\u002Fhidden-env-vars","Hidden Environment Variables",{"path":1160,"title":1161},"\u002Fchangelog\u002F2025\u002F01\u002Fimproved-diagnostics","Improved Diagnostics",{"path":1163,"title":1164},"\u002Fchangelog\u002F2025\u002F01\u002Fteam-level-groups","Team level view of Groups",{"path":1166,"title":1167},"\u002Fchangelog\u002F2025\u002F02\u002Fadditional-device-version-history-events","New Remote Instances Version History Events",{"path":1169,"title":1170},"\u002Fchangelog\u002F2025\u002F02\u002Fbroker-error-feedback","Improved Broker Connection Feedback",{"path":1172,"title":1173},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-agent-updates","FlowFuse User Authentication on Remote Instances",{"path":1175,"title":770},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-version-history-timeline",{"path":1177,"title":1178},"\u002Fchangelog\u002F2025\u002F02\u002Fexternal-brokers","External MQTT Brokers",{"path":1180,"title":1181},"\u002Fchangelog\u002F2025\u002F02\u002Fmqtt-schema-suggestions","MQTT Smart Schema Suggestions",{"path":1183,"title":1184},"\u002Fchangelog\u002F2025\u002F02\u002Fresend-and-extend-team-invitation-expiration","Re-send Team Invitations",{"path":1186,"title":1187},"\u002Fchangelog\u002F2025\u002F02\u002Fschema-docs","Personalized Schema Documentation",{"path":1189,"title":1190},"\u002Fchangelog\u002F2025\u002F02\u002Ftopic-hierarchy-search","Search & Filter for Topic Hierarchy List",{"path":1192,"title":1193},"\u002Fchangelog\u002F2025\u002F03\u002Fcontainer-tags","Changes to tags for flowfuse\u002Fnode-red",{"path":1195,"title":1196},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-groups","Multiple Device Groups in a pipeline",{"path":1198,"title":1199},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-local-login","Local Login for Remote Instances",{"path":1201,"title":1202},"\u002Fchangelog\u002F2025\u002F03\u002Ffree-tier","Free Tier now more accessible to all",{"path":1204,"title":1205},"\u002Fchangelog\u002F2025\u002F03\u002Fresource-notifications","Resource Alerts",{"path":1207,"title":1208},"\u002Fchangelog\u002F2025\u002F03\u002Fsnapshot-filter","Filtering Snapshots",{"path":1210,"title":1211},"\u002Fchangelog\u002F2025\u002F03\u002Fteam-npm-registry","NPM Package Hosting",{"path":1213,"title":1214},"\u002Fchangelog\u002F2025\u002F03\u002Ftopic-deletion","MQTT Topic Management",{"path":1216,"title":1217},"\u002Fchangelog\u002F2025\u002F04\u002Fdevice-provisioning","Remote Instance Provisioning",{"path":1219,"title":1220},"\u002Fchangelog\u002F2025\u002F04\u002Fgit-integration","Git Integration with Pipelines",{"path":1222,"title":1223},"\u002Fchangelog\u002F2025\u002F04\u002Finstance-log-browsing","Better Node-RED log handling",{"path":1225,"title":1226},"\u002Fchangelog\u002F2025\u002F05\u002Fimport-node-red-flows","Import Node-RED Flows During Remote Instance Setup",{"path":1228,"title":1229},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant","FlowFuse Expert just got smarter",{"path":1231,"title":1229},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant-2",{"path":1233,"title":1234},"\u002Fchangelog\u002F2025\u002F06\u002Fgit-integration","Pulling snapshots from Git with Pipelines",{"path":1236,"title":1237},"\u002Fchangelog\u002F2025\u002F06\u002Finstance-performance-memory","Memory Metrics in Instance Performance View",{"path":1239,"title":1240},"\u002Fchangelog\u002F2025\u002F06\u002Fnew-home-page","Introducing the New Home Page Experience",{"path":1242,"title":1243},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance","Team Performance Feature",{"path":1245,"title":1246},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance-view","Instance Performance View",{"path":1248,"title":1249},"\u002Fchangelog\u002F2025\u002F06\u002Fui-refresh","Navigation UI Refresh",{"path":1251,"title":1252},"\u002Fchangelog\u002F2025\u002F07\u002Fbrowse-node-red-flows","Browse for Node-RED Flows During Remote Instance Setup",{"path":1254,"title":594},"\u002Fchangelog\u002F2025\u002F07\u002Fflowfuse-tables",{"path":1256,"title":1257},"\u002Fchangelog\u002F2025\u002F07\u002Fimport-blueprints","Import blueprints directly into your existing instances",{"path":1259,"title":1260},"\u002Fchangelog\u002F2025\u002F07\u002Fsimplified-applications-overview","Simplified Applications Page with Summary Tiles",{"path":1262,"title":1263},"\u002Fchangelog\u002F2025\u002F07\u002Fsmart-suggestions","Smart Suggestions",{"path":1265,"title":1266},"\u002Fchangelog\u002F2025\u002F07\u002Fteam-to-pro-plan-rename","Team Plan Renamed to Pro Plan",{"path":1268,"title":1269},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-hosted","Generate snapshot descriptions with AI",{"path":1271,"title":1272},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-remote","AI Snapshot Descriptions Now Work with Remote Instances",{"path":1274,"title":1275},"\u002Fchangelog\u002F2025\u002F08\u002Fdevice-performance","FlowFuse Remote Instance Performance Data",{"path":1277,"title":1278},"\u002Fchangelog\u002F2025\u002F08\u002Fdirect-sso","Direct SSO Login",{"path":1280,"title":1281},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-assistant","FlowFuse Expert documents your flows",{"path":1283,"title":1284},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-mqtt","FlowFuse MQTT",{"path":1286,"title":1287},"\u002Fchangelog\u002F2025\u002F08\u002Fhttp-cors","Configure HTTP CORS",{"path":1289,"title":1290},"\u002Fchangelog\u002F2025\u002F08\u002Fsubflow-export","Export SubFlow as Node-RED module",{"path":1292,"title":1293},"\u002Fchangelog\u002F2025\u002F08\u002Ftables-assistant","FlowFuse Tables with a little help from the Assistant",{"path":1295,"title":1296},"\u002Fchangelog\u002F2025\u002F09\u002Fexpose-saml-groups-to-dashboard","Allow SSO groups to be shared with the Node-RED Dashboard",{"path":1298,"title":1299},"\u002Fchangelog\u002F2025\u002F09\u002Finline-assist","FlowFuse Expert can help you write code",{"path":1301,"title":1302},"\u002Fchangelog\u002F2025\u002F09\u002Fretiring-flowforge-device-agent","No more @flowforge\u002Fflowforge-device-agent releases",{"path":1304,"title":1305},"\u002Fchangelog\u002F2025\u002F09\u002Frevised-instance-snapshot-ui","Streamlined Snapshot Management",{"path":1307,"title":1308},"\u002Fchangelog\u002F2025\u002F09\u002Fteam-broker-async-api","Capture Async API data from FlowFuse Team Broker",{"path":1310,"title":1311},"\u002Fchangelog\u002F2025\u002F10\u002Fapplication-level-rbac","Application-level access control for Enterprise teams",{"path":1313,"title":1314},"\u002Fchangelog\u002F2025\u002F10\u002Fbulk-device-group-assignment","Easier Access to Bulk Device Group Management",{"path":1316,"title":1317},"\u002Fchangelog\u002F2025\u002F10\u002Fduplicate-instances-across-applications","Duplicate Instances Across Different Applications",{"path":1319,"title":1320},"\u002Fchangelog\u002F2025\u002F10\u002Fimport-flows-on-instance-creation","Import flows during instance creation",{"path":1322,"title":1323},"\u002Fchangelog\u002F2025\u002F10\u002Fmcp-nodes","FlowFuse MCP Server Nodes",{"path":1325,"title":1326},"\u002Fchangelog\u002F2025\u002F10\u002Fonnx-nodes","FlowFuse AI Nodes",{"path":1328,"title":1329},"\u002Fchangelog\u002F2025\u002F10\u002Fsettings-page-device-group-management","Device Group Management from Settings Page",{"path":1331,"title":1332},"\u002Fchangelog\u002F2025\u002F11\u002Fff-expert-update","FlowFuse Expert Update",{"path":1334,"title":1335},"\u002Fchangelog\u002F2025\u002F11\u002Fminimum-nodejs-version","Node.js v20 Minimum Version Requirement",{"path":1337,"title":1338},"\u002Fchangelog\u002F2025\u002F11\u002Fsso-session","SSO control over Session life",{"path":1340,"title":1341},"\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights","FlowFuse Expert: Now with MCP-Powered Insights",{"path":1343,"title":1344},"\u002Fchangelog\u002F2025\u002F12\u002Fscheduled-maintenance","Scheduled Maintenance Mode",{"path":1346,"title":1347},"\u002Fchangelog\u002F2026\u002F01\u002Fdevice-agent-containers","Device Agent Docker Containers updated",{"path":1349,"title":1350},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-manage-palette","FlowFuse Expert: Enhanced Palette Integration",{"path":1352,"title":1353},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-nr-actions","FlowFuse Expert: Integration with Node-RED",{"path":1355,"title":1356},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-palette-queries","FlowFuse Expert: Palette Queries",{"path":1358,"title":1359},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-select-flows","FlowFuse Expert: Ask about your flows",{"path":1361,"title":1362},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-rbacs","FlowFuse Expert: MCP-Powered Insights with RBACs",{"path":1364,"title":1365},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-security","FlowFuse Expert: MCP-Powered Insights",{"path":1367,"title":1368},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options","Set Node.js Options for Remote Instances",{"path":1370,"title":1371},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context","FlowFuse Expert: Helping you make sense of your debug log",{"path":1373,"title":1374},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner","FlowFuse Expert: Never Miss an Update",{"path":1376,"title":1377},"\u002Fchangelog\u002F2026\u002F02\u002Fha-instance-rolling-restart","HA Hosted Instance Rolling Restart",{"path":1379,"title":1380},"\u002Fchangelog\u002F2026\u002F02\u002Fremote-instances-immersive-editor","Immersive Mode for Remote Instances",{"path":1382,"title":1383},"\u002Fchangelog\u002F2026\u002F02\u002Frestoring-snapshots-to-remote-instances","Restoring snapshots to developer-mode Remote Instances",{"path":1385,"title":1386},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops","Azure DevOps Pipeline support",{"path":1388,"title":1389},"\u002Fchangelog\u002F2026\u002F03\u002Fdeveloper-mode-in-immersive-editor","Developer Mode Now Accessible from the Immersive Editor",{"path":1391,"title":1392},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title","Embedded Editor Now Shows Active Tab",{"path":1394,"title":1395},"\u002Fchangelog\u002F2026\u002F03\u002Fmarch-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on March 28th, 2026",{"path":1397,"title":1398},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor","View Snapshot Details in the Immersive Editor",{"path":1400,"title":1401},"\u002Fchangelog\u002F2026\u002F04\u002Fexpert-action-links","FlowFuse expert action links",{"path":1403,"title":1404},"\u002Fchangelog\u002F2026\u002F04\u002Fhosted-instance-url-env-var","Hosted Instances know their own URL",{"path":1406,"title":663},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer",{"path":1408,"title":1409},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer","Richer snapshot comparison view",{"path":1411,"title":1412},"\u002Fchangelog\u002F2026\u002F05\u002Fai-opt-out","AI Feature Opt-Out for Teams",{"path":1414,"title":1415},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building","FlowFuse Expert Builds Your Application",{"path":1417,"title":1418},"\u002Fchangelog\u002F2026\u002F05\u002Fsingle-sso-provider","Single SSO provider for all users",{"path":1420,"title":1421},"\u002Fchangelog\u002F2026\u002F06\u002Fdark-mode","Dark Mode",{"path":1423,"title":1424},"\u002Fchangelog\u002F2026\u002F06\u002Fdevice-agent-v4-released","Device Agent v4 released",{"path":1426,"title":1427},"\u002Fchangelog\u002F2026\u002F06\u002Fgeneric-git-server-support","Connect Pipelines to Any Git Server",{"path":1429,"title":1430},"\u002Fchangelog\u002F2026\u002F06\u002Fjuly-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on July 11th, 2026",{"path":1432,"title":1433},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups","Application Roles from SSO Groups",{"path":1435,"title":1436},"\u002Fchangelog\u002F2026\u002F07\u002Fdevice-agent-onboarding","Getting started with FlowFuse straight from the terminal",{"path":1438,"title":1439},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-enhancements","FlowFuse Expert Enhancements",{"path":1441,"title":1442},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation","FlowFuse Expert Can Now Work With Your Tables",{"path":1444,"title":1445},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats","Team Scoped Personal Access Tokens",{"path":1447,"title":1448},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards","A Dedicated Home for Your Dashboards",[],1786105897691]