[{"data":1,"prerenderedAt":1407},["ShallowReactive",2],{"blog-\u002Fblog\u002F2025\u002F12\u002Fwhat-is-teep":3,"featureCatalog":477,"changelog-titles":872,"blog-all-for-related":1406},{"id":4,"title":5,"authors":6,"body":8,"cta":451,"date":452,"description":453,"extension":454,"features":451,"image":455,"lastUpdated":456,"meta":457,"navigation":467,"path":468,"release":451,"seo":469,"sitemap":470,"stem":471,"subtitle":472,"tags":473,"tldr":475,"video":451,"__hash__":476},"blog\u002Fblog\u002F2025\u002F12\u002Fwhat-is-teep.md","What is TEEP? Calculation, Benchmarks & TEEP vs OEE (2026)",[7],"sumit-shinde",{"type":9,"value":10,"toc":435},"minimark",[11,26,29,32,37,49,52,56,59,64,67,71,78,84,87,103,106,113,117,120,208,213,216,236,239,243,246,251,271,278,283,304,307,311,314,317,349,352,356,359,362,365,369,372,375,378,382,385,388,392,395,398,416,428,432],[12,13,14,15,20,21,25],"p",{},"Total Effective Equipment Performance (TEEP) is a manufacturing KPI used to understand how much of an equipment investment is actually being utilized. While most manufacturers rely on ",[16,17,19],"a",{"href":18},"\u002Fblog\u002F2025\u002F04\u002Fbuilding-oee-dashboard-with-flowfuse-part-1\u002F#what-is-oee","Overall Equipment Effectiveness (OEE)"," to assess shop-floor performance, years of real-world use have revealed a critical blind spot: OEE only measures how well equipment runs ",[22,23,24],"em",{},"when it is scheduled to run",". It says nothing about the many hours assets sit idle due to planning decisions, demand patterns, labor availability, or maintenance strategy.",[12,27,28],{},"This gap matters. In many factories, equipment represents the largest capital investment on the balance sheet, yet significant capacity remains unused outside scheduled production hours. TEEP addresses this gap by extending measurement beyond scheduled production and into total calendar time, providing visibility into both operational performance and unused capacity.",[12,30,31],{},"To understand how TEEP does this, it’s important to be precise about what the metric actually measures.",[33,34,36],"h2",{"id":35},"what-is-teep","What is TEEP?",[12,38,39,40,44,45,48],{},"TEEP measures the percentage of ",[41,42,43],"strong",{},"total calendar time"," that equipment spends producing good parts at the correct speed. Unlike OEE, which evaluates performance only during planned production, TEEP includes ",[41,46,47],{},"every hour of the day",", whether production was scheduled or not. That means all 168 hours in a week and all 8,760 hours in a year are part of the calculation.",[12,50,51],{},"This distinction is fundamental. If a factory operates a single shift per day, OEE evaluates only those eight scheduled hours and ignores the remaining sixteen. TEEP counts them all. As a result, TEEP reveals how much of the equipment’s full potential is actually being used, not just how well it performs during active shifts.",[33,53,55],{"id":54},"teep-formula-and-calculation","TEEP Formula and Calculation",[12,57,58],{},"The math works the same way as OEE:",[12,60,61],{},[41,62,63],{},"TEEP = Availability × Performance × Quality",[12,65,66],{},"But availability now means operating time divided by total calendar time, not just scheduled time. If a production line runs 120 hours per week at full speed with no defects, it has 71.4% TEEP (120 divided by 168). The other 48 hours might be maintenance time, unplanned downtime, or time when no production was scheduled.",[33,68,70],{"id":69},"why-teep-matters","Why TEEP Matters",[12,72,73,74,77],{},"TEEP matters because it connects operational performance to ",[41,75,76],{},"business value",", not just shop-floor efficiency. While OEE shows how well equipment runs during scheduled shifts, it says nothing about how much of the asset you're actually using relative to what you paid for it. TEEP fills that gap.",[12,79,80,81],{},"For capital-intensive manufacturing, this difference is critical. Equipment often represents millions in investment, yet much of that capacity may sit idle due to scheduling choices, demand patterns, labor availability, or maintenance strategy. TEEP makes this visible. It answers the executive-level question: ",[41,82,83],{},"\"Are we getting a return on our equipment, or is capacity hiding in plain sight?\"",[12,85,86],{},"TEEP is especially valuable when:",[88,89,90,94,97,100],"ul",{},[91,92,93],"li",{},"Customer demand is increasing and capacity feels tight",[91,95,96],{},"Management is considering adding shifts or buying new equipment",[91,98,99],{},"Capital expenditure decisions need justification",[91,101,102],{},"Different plants or lines need to be compared at a high level",[12,104,105],{},"In many cases, TEEP reveals that the fastest and cheapest way to increase output is not buying new machines, but better utilizing the ones already installed. A modest TEEP improvement can unlock significant production capacity without additional capital investment.",[12,107,108,109,112],{},"Importantly, TEEP is not about pushing equipment to run 24\u002F7 at all costs. Instead, it provides the data needed to make ",[41,110,111],{},"intentional, informed decisions"," about scheduling, staffing, maintenance, and growth.",[33,114,116],{"id":115},"teep-vs-oee-key-differences","TEEP vs OEE: Key Differences",[12,118,119],{},"OEE and TEEP both measure equipment performance, but they look at different things. The big difference is what time period they measure against.",[121,122,123,139],"table",{},[124,125,126],"thead",{},[127,128,129,133,136],"tr",{},[130,131,132],"th",{},"Feature",[130,134,135],{},"OEE",[130,137,138],{},"TEEP",[140,141,142,156,169,182,195],"tbody",{},[127,143,144,150,153],{},[145,146,147],"td",{},[41,148,149],{},"What it measures",[145,151,152],{},"How well equipment runs during scheduled time",[145,154,155],{},"How much of total time equipment actually produces",[127,157,158,163,166],{},[145,159,160],{},[41,161,162],{},"Time counted",[145,164,165],{},"Only planned production hours",[145,167,168],{},"Every hour (24\u002F7, all year)",[127,170,171,176,179],{},[145,172,173],{},[41,174,175],{},"Who uses it",[145,177,178],{},"Production supervisors and operators",[145,180,181],{},"Executives and plant managers",[127,183,184,189,192],{},[145,185,186],{},[41,187,188],{},"Typical numbers",[145,190,191],{},"60-85% is good",[145,193,194],{},"30-80% depending on shifts",[127,196,197,202,205],{},[145,198,199],{},[41,200,201],{},"Main question answered",[145,203,204],{},"\"How efficiently did we use our scheduled time?\"",[145,206,207],{},"\"How much are we actually using this equipment?\"",[12,209,210],{},[41,211,212],{},"Here's another simple example:",[12,214,215],{},"Your packaging line runs one 8-hour shift per day, Monday through Friday. In one week:",[88,217,218,221,224,230],{},[91,219,220],{},"You scheduled 40 hours of production",[91,222,223],{},"Equipment actually ran well for 34 hours",[91,225,226,229],{},[41,227,228],{},"Your OEE: 85%"," - Great! The production team did an excellent job during their shift.",[91,231,232,235],{},[41,233,234],{},"Your TEEP: 20%"," - The equipment was productive for 34 out of 168 total hours in the week.",[12,237,238],{},"Both numbers are correct and useful. OEE shows your production team is doing their job well. TEEP shows the equipment sits unused most of the time. Whether that's okay depends on customer demand, labor costs, and your business strategy.",[33,240,242],{"id":241},"what-is-a-good-teep-score","What Is a Good TEEP Score?",[12,244,245],{},"One of the most common questions manufacturers ask is: \"What TEEP score should we target?\" The answer depends entirely on your industry, shift strategy, and business model.",[12,247,248],{},[41,249,250],{},"Industry-Specific TEEP Benchmarks:",[88,252,253,259,265],{},[91,254,255,258],{},[41,256,257],{},"Continuous process industries"," (paper mills, chemical plants, refineries): 80-90% TEEP for critical equipment. These operations are designed for 24\u002F7 production, and high TEEP reflects the economics of continuous processing.",[91,260,261,264],{},[41,262,263],{},"Two-shift batch manufacturers"," (automotive parts, packaging, electronics): 40-60% TEEP is typical. Even with excellent operational performance, running two 8-hour shifts five days per week caps theoretical maximum TEEP at 48%.",[91,266,267,270],{},[41,268,269],{},"Single-shift operations"," (job shops, specialized manufacturing): 25-35% TEEP is common and often optimal. Running one 8-hour shift per day limits maximum TEEP to about 24% even with perfect execution.",[12,272,273,274,277],{},"The key insight: ",[41,275,276],{},"good TEEP is relative, not absolute",". A 35% TEEP might represent world-class performance for a single-shift custom manufacturer, while 65% TEEP could indicate serious underutilization for a continuous process line.",[12,279,280],{},[41,281,282],{},"What matters most is:",[284,285,286,292,298],"ol",{},[91,287,288,291],{},[41,289,290],{},"Trend analysis",": Is your TEEP improving or declining over time?",[91,293,294,297],{},[41,295,296],{},"Internal benchmarking",": How does similar equipment compare within your facility?",[91,299,300,303],{},[41,301,302],{},"Business alignment",": Does your TEEP support your capacity strategy and customer demand patterns?",[12,305,306],{},"Don't chase arbitrary TEEP targets. Instead, use TEEP to understand whether your equipment utilization matches your business strategy, identify capacity constraints before they become critical, and make informed decisions about shift additions or capital investments.",[33,308,310],{"id":309},"how-to-use-both-metrics","How to Use Both Metrics",[12,312,313],{},"Most companies track both OEE and TEEP. OEE stays the main tool for production supervisors and operators who focus on running equipment well during scheduled time. TEEP gives executives information they need for planning capacity, deciding on equipment purchases, and analyzing whether to expand into new markets.",[12,315,316],{},"To calculate TEEP correctly, you need to track time carefully. Many manufacturing systems already sort downtime into planned and unplanned categories for OEE. TEEP needs more detail:",[88,318,319,325,331,337,343],{},[91,320,321,324],{},[41,322,323],{},"Scheduled production time",": When equipment runs or could start running right away",[91,326,327,330],{},[41,328,329],{},"Planned maintenance",": Regular maintenance windows",[91,332,333,336],{},[41,334,335],{},"Changeovers",": Time spent switching between different products",[91,338,339,342],{},[41,340,341],{},"No orders",": Equipment sits idle because not enough customers want products",[91,344,345,348],{},[41,346,347],{},"Operational limits",": Problems with other equipment, not enough workers, or other constraints",[12,350,351],{},"Without clear categories, TEEP can unfairly punish good operational decisions. Equipment that creates bottlenecks should show high TEEP. Other equipment may correctly show lower numbers.",[33,353,355],{"id":354},"real-world-examples","Real-World Examples",[12,357,358],{},"TEEP works best in industries where equipment can run around the clock. Paper mills, chemical plants, and steel factories typically target higher TEEP values for their main production equipment since continuous operation makes business sense for these processes.",[12,360,361],{},"Industries that make distinct products in batches usually see lower numbers. This makes sense when you think about it: a factory running two eight-hour shifts, five days per week, can only reach about 48% TEEP even if everything runs perfectly during those scheduled hours.",[12,363,364],{},"The automotive industry shows why context matters. Assembly lines often run two shifts per day. Even with excellent operational performance during scheduled production time, TEEP numbers naturally stay lower. This reflects intentional business decisions about shift schedules, labor costs, and maintenance planning rather than poor performance.",[33,366,368],{"id":367},"common-mistakes-to-avoid","Common Mistakes to Avoid",[12,370,371],{},"Several problems come up when companies use TEEP incorrectly. One major mistake is using TEEP to judge daily operations. Production workers cannot control customer demand or high-level scheduling decisions. Holding supervisors responsible for TEEP creates bad incentives to build unnecessary inventory or skip planned maintenance.",[12,373,374],{},"Another common error is ignoring the bigger picture. Equipment designed to handle product changes, quality testing, or work with other equipment should not be compared to equipment that runs continuously. A 35% TEEP might be the best possible number for a packaging line that serves multiple production lines.",[12,376,377],{},"Finally, many companies make the mistake of treating TEEP as a fixed target. TEEP helps you compare performance over time or across similar equipment. A dropping TEEP trend means you should investigate. But any single TEEP number needs context to understand what it means.",[33,379,381],{"id":380},"using-teep-for-capacity-planning","Using TEEP for Capacity Planning",[12,383,384],{},"TEEP helps most when planning capacity. When customer demand gets close to what you can produce, companies face a big decision: spend money to expand capacity or accept slower growth. TEEP analysis clarifies this choice by showing how much extra capacity exists in current equipment.",[12,386,387],{},"A factory with 65% TEEP across major equipment could theoretically increase production by 54% without buying new equipment, assuming customer demand exists and operational problems can be solved. Whether this capacity can actually be used depends on shift schedules, worker availability, maintenance needs, and product mix, but TEEP shows the theoretical maximum.",[33,389,391],{"id":390},"setting-up-teep-measurement","Setting Up TEEP Measurement",[12,393,394],{},"Companies that want accurate TEEP need good data collection systems. Writing down times by hand produces unreliable results. Automated data capture from equipment computers, control systems, or manufacturing software provides the foundation for accurate calculations.",[12,396,397],{},"The money spent on measurement systems should match decision-making needs. Companies making frequent capacity investment decisions benefit from real-time TEEP monitoring. Organizations with stable capacity and clear bottlenecks might find quarterly manual calculations work fine.",[12,399,400,401,405,406,410,411,415],{},"Building TEEP dashboards has become much simpler with modern tools. FlowFuse offers a practical solution for companies that want real-time equipment monitoring without complex programming. The platform bridges the gap between OT (Operational Technology) on the factory floor and IT systems in the office. It connects directly to your equipment, whether through ",[16,402,404],{"href":403},"\u002Fsolutions\u002Fscada\u002F","PLCs, SCADA systems",", or ",[16,407,409],{"href":408},"\u002Fsolutions\u002Fmes\u002F","machine controllers and MES platforms",", and creates visual dashboards that track performance metrics. You can see how straightforward the process is by looking at their ",[16,412,414],{"href":413},"\u002Fblueprints\u002Fmanufacturing\u002Foee-dashboard\u002F","OEE dashboard blueprint",". The same approach works for TEEP, connect your data sources, set up the calculations, and view your equipment utilization in real-time. This makes professional-grade monitoring accessible even for smaller manufacturers or companies without dedicated programming staff.",[12,417,418],{},[22,419,420],{},[41,421,422,423,427],{},"Want to see how TEEP monitoring would work for your specific equipment and production environment? ",[16,424,426],{"href":425},"\u002Fbook-demo\u002F","Book a demo"," with FlowFuse to explore how you can track equipment utilization, identify capacity opportunities, and make data-driven decisions about your manufacturing assets.",[33,429,431],{"id":430},"the-bottom-line","The Bottom Line",[12,433,434],{},"TEEP extends equipment measurement from operational efficiency to overall asset use. It does not replace OEE but adds to it by answering questions OEE cannot answer. When used carefully with proper context, TEEP gives manufacturing leaders clear visibility into total equipment productivity. It helps inform capacity investment decisions with solid numbers. The value is not in achieving high percentages but in understanding what those percentages reveal about equipment use, customer demand, and operational constraints.",{"title":436,"searchDepth":437,"depth":437,"links":438},"",4,[439,441,442,443,444,445,446,447,448,449,450],{"id":35,"depth":440,"text":36},2,{"id":54,"depth":440,"text":55},{"id":69,"depth":440,"text":70},{"id":115,"depth":440,"text":116},{"id":241,"depth":440,"text":242},{"id":309,"depth":440,"text":310},{"id":354,"depth":440,"text":355},{"id":367,"depth":440,"text":368},{"id":380,"depth":440,"text":381},{"id":390,"depth":440,"text":391},{"id":430,"depth":440,"text":431},null,"2025-12-19","Your equipment sits idle 16+ hours daily. TEEP in 2026 measures this, OEE ignores it. Get the formula, learn when 35% TEEP beats 60%, and turn hidden capacity into profit without capital investment.","md","\u002Fblog\u002F2025\u002F12\u002Fimages\u002Fwhat-is-teep.png","2026-06-17",{"keywords":458,"excerpt":459},"TEEP, total effective equipment performance, TEEP calculation, TEEP vs OEE, OEE vs TEEP, equipment utilization, capacity planning, TEEP formula, TEEP benchmark, TEEP monitoring, overall equipment effectiveness, TEEP dashboard",{"type":9,"value":460},[461],[12,462,14,463,20,465,25],{},[16,464,19],{"href":18},[22,466,24],{},true,"\u002Fblog\u002F2025\u002F12\u002Fwhat-is-teep",{"title":5,"description":453},{"loc":468},"blog\u002F2025\u002F12\u002Fwhat-is-teep","If you're tracking OEE, you're only seeing half the picture.",[474],"flowfuse","TEEP (Total Effective Equipment Performance) measures the percentage of total calendar time (all 8,760 hours a year) that equipment spends producing good parts at speed, calculated as Utilization x OEE (Availability x Performance x Quality). Unlike OEE, which only looks at scheduled production time, TEEP exposes idle capacity created by shift patterns, demand, and maintenance strategy. TEEP scores are always lower than OEE and are most useful for capacity planning and deciding whether to add shifts before buying new equipment.","X3TNrQhUhMWO0i0nTyRrifP_T0X4CG--SbFYDiwoS4E",{"id":478,"extension":479,"meta":480,"sections":481,"stem":870,"__hash__":871},"featureCatalog\u002Ffeature-catalog.yml","yml",{},[482,533,634,696,773,852],{"id":483,"title":484,"features":485},"ai-automation","AI & Automation",[486,496,506,516,522,528],{"id":487,"title":488,"description":489,"docsLink":490,"changelog":491,"tiers":495},"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",[492],{"url":493,"release":494},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner\u002F","2.28",{"edge":467,"hub":467,"fleet":467},{"id":497,"title":498,"description":499,"docsLink":500,"changelog":501,"subfeature":467,"showOnPricing":504,"tiers":505},"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",[502],{"url":503,"release":494},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context\u002F",false,{"edge":467,"hub":467,"fleet":467},{"id":507,"title":508,"description":509,"docsLink":510,"changelog":511,"subfeature":467,"showOnPricing":504,"tiers":515},"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",[512],{"url":513,"release":514},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building\u002F","2.30",{"edge":467,"hub":467,"fleet":467},{"id":517,"title":518,"description":519,"docsLink":520,"subfeature":467,"beta":467,"showOnPricing":504,"tiers":521},"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":467,"hub":467,"fleet":467},{"id":523,"title":524,"description":525,"docsLink":526,"tiers":527},"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":467,"hub":467,"fleet":467},{"id":529,"title":530,"description":531,"tiers":532},"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":467,"hub":467,"fleet":467},{"id":534,"title":535,"features":536},"build","Build",[537,543,549,559,565,571,575,581,587,595,601,605,609,618,626],{"id":538,"title":539,"description":540,"docsLink":541,"tiers":542},"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":467,"hub":504,"fleet":467},{"id":544,"title":545,"description":546,"docsLink":547,"tiers":548},"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":467,"hub":467,"fleet":467},{"id":550,"title":551,"description":552,"docsLink":553,"changelog":554,"tiers":558},"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",[555],{"url":556,"release":557},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation\u002F","2.33",{"edge":467,"hub":467,"fleet":467},{"id":560,"title":561,"description":562,"docsLink":563,"tiers":564},"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":467,"hub":467,"fleet":467},{"id":566,"title":567,"description":568,"docsLink":569,"showOnPricing":504,"tiers":570},"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":467,"hub":467,"fleet":467},{"id":572,"title":573,"showOnPricing":504,"tiers":574},"static-assets","Static Assets",{"edge":467,"hub":467,"fleet":467},{"id":576,"title":577,"description":578,"docsLink":579,"tiers":580},"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":467,"hub":467,"fleet":467},{"id":582,"title":583,"description":584,"docsLink":585,"tiers":586},"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":467,"hub":467,"fleet":467},{"id":588,"title":589,"description":590,"changelog":591,"subfeature":467,"showOnPricing":504,"tiers":594},"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.",[592],{"url":593,"release":557},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards\u002F",{"edge":467,"hub":467,"fleet":467},{"id":596,"title":597,"description":598,"docsLink":599,"tiers":600},"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":467,"hub":467,"fleet":467},{"id":602,"title":603,"subfeature":467,"showOnPricing":504,"tiers":604},"blueprints-ot-apps","Blueprints - OT APPS",{"edge":467,"hub":504,"fleet":467},{"id":606,"title":607,"subfeature":467,"showOnPricing":504,"tiers":608},"blueprints-it-apps","Blueprints - IT APPS",{"edge":504,"hub":467,"fleet":504},{"id":610,"title":611,"description":612,"changelog":613,"showOnPricing":504,"tiers":617},"immersive-editor-snapshots","Snapshot Details in Immersive Editor","View and manage snapshot details directly inside the immersive editor without leaving your editing session.",[614],{"url":615,"release":616},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor\u002F","2.29",{"edge":467,"hub":467,"fleet":467},{"id":619,"title":620,"description":621,"changelog":622,"showOnPricing":504,"tiers":625},"immersive-editor-drawer","Customisable Immersive Editor Drawer","Pin, move, resize, or full-screen the immersive editor drawer. Your preferences are remembered between sessions.",[623],{"url":624,"release":514},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer\u002F",{"edge":467,"hub":467,"fleet":467},{"id":627,"title":628,"description":629,"changelog":630,"showOnPricing":504,"tiers":633},"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.",[631],{"url":632,"release":616},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title\u002F",{"edge":467,"hub":467,"fleet":467},{"id":635,"title":636,"features":637},"deploy","Deploy",[638,644,653,659,665,671,677,683,688],{"id":639,"title":640,"description":641,"docsLink":642,"tiers":643},"hosted-instances","Cloud Instances","Run Node-RED instances managed and hosted by FlowFuse.","\u002Fdocs\u002Fuser\u002Fintroduction\u002F#creating-a-node-red-instance",{"edge":467,"hub":467,"fleet":467},{"id":645,"title":646,"description":647,"docsLink":648,"changelog":649,"tiers":652},"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",[650],{"url":651,"release":494},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options\u002F",{"edge":467,"hub":504,"fleet":467},{"id":654,"title":655,"description":656,"docsLink":657,"tiers":658},"custom-hostnames","Custom Hostnames","Access your Node-RED application via your own domain name.","\u002Fdocs\u002Fuser\u002Fcustom-hostnames\u002F",{"edge":504,"hub":467,"fleet":504},{"id":660,"title":661,"description":662,"docsLink":663,"tiers":664},"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":467,"hub":504,"fleet":467},{"id":666,"title":667,"description":668,"docsLink":669,"showOnPricing":504,"tiers":670},"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":467,"hub":467,"fleet":467},{"id":672,"title":673,"description":674,"docsLink":675,"tiers":676},"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":467,"hub":467,"fleet":467},{"id":678,"title":679,"description":680,"docsLink":681,"tiers":682},"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":504,"hub":467,"fleet":504},{"id":684,"title":685,"description":686,"docsLink":681,"subfeature":467,"showOnPricing":504,"tiers":687},"git-integration-github","GitHub","Push and pull snapshots to GitHub repositories through DevOps Pipeline Git Stages.",{"edge":504,"hub":467,"fleet":504},{"id":689,"title":690,"description":691,"docsLink":681,"changelog":692,"subfeature":467,"showOnPricing":504,"tiers":695},"git-integration-azure","Azure DevOps","Push and pull snapshots to Azure DevOps repositories through DevOps Pipeline Git Stages.",[693],{"url":694,"release":616},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops\u002F",{"edge":504,"hub":467,"fleet":504},{"id":697,"title":698,"features":699},"operate-maintain","Operate & Maintain",[700,706,712,717,725,729,733,738,744,750,755,761,765,769],{"id":701,"title":702,"description":703,"docsLink":704,"tiers":705},"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":467,"hub":467,"fleet":467},{"id":707,"title":708,"description":709,"docsLink":710,"subfeature":467,"showOnPricing":504,"tiers":711},"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":467,"hub":467,"fleet":467},{"id":713,"title":714,"description":715,"docsLink":710,"subfeature":467,"showOnPricing":504,"tiers":716},"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":467,"hub":467,"fleet":467},{"id":718,"title":719,"description":720,"changelog":721,"subfeature":467,"showOnPricing":504,"tiers":724},"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.",[722],{"url":723,"release":616},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer\u002F",{"edge":467,"hub":467,"fleet":467},{"id":726,"title":727,"subfeature":467,"showOnPricing":504,"tiers":728},"version-history-timeline","Version History Timeline",{"edge":467,"hub":467,"fleet":467},{"id":730,"title":731,"tiers":732},"unlimited-workflow-executions","Unlimited Workflow Executions",{"edge":467,"hub":467,"fleet":467},{"id":734,"title":735,"description":736,"tiers":737},"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":467,"hub":504,"fleet":467},{"id":739,"title":740,"description":741,"docsLink":742,"tiers":743},"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":467,"hub":504,"fleet":467},{"id":745,"title":746,"description":747,"docsLink":748,"tiers":749},"high-availability","High Availability","Leverage horizontal scaling for reliable and scalable processing of your data through Node-RED.","\u002Fdocs\u002Fuser\u002Fhigh-availability\u002F",{"edge":504,"hub":467,"fleet":504},{"id":751,"title":752,"description":753,"tiers":754},"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":467,"hub":467,"fleet":467},{"id":756,"title":757,"description":758,"docsLink":759,"subfeature":467,"showOnPricing":504,"tiers":760},"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":467,"hub":467,"fleet":467},{"id":762,"title":763,"subfeature":467,"showOnPricing":504,"tiers":764},"email-alerts","Email Alerts",{"edge":467,"hub":467,"fleet":467},{"id":766,"title":767,"showOnPricing":504,"tiers":768},"api-debug-length-limit","API\u002FDebug Length Limit",{"edge":467,"hub":467,"fleet":467},{"id":770,"title":771,"tiers":772},"protected-instances","Protected Instances",{"edge":504,"hub":467,"fleet":504},{"id":774,"title":775,"features":776},"govern-secure","Govern and Secure",[777,786,792,798,803,809,815,821,829,835,841,847],{"id":778,"title":779,"description":780,"docsLink":781,"changelog":782,"tiers":785},"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",[783],{"url":784,"release":557},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups\u002F",{"edge":467,"hub":467,"fleet":467},{"id":787,"title":788,"description":789,"docsLink":790,"tiers":791},"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":467,"hub":467,"fleet":467},{"id":793,"title":794,"description":795,"docsLink":796,"tiers":797},"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":504,"hub":467,"fleet":467},{"id":799,"title":800,"description":801,"tiers":802},"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":467,"hub":504,"fleet":504},{"id":804,"title":805,"description":806,"docsLink":807,"tiers":808},"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":467,"hub":467,"fleet":467},{"id":810,"title":811,"description":812,"docsLink":813,"tiers":814},"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":467,"hub":467,"fleet":467},{"id":816,"title":817,"description":818,"docsLink":819,"subfeature":467,"showOnPricing":504,"tiers":820},"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":467,"hub":467,"fleet":467},{"id":822,"title":823,"description":824,"changelog":825,"subfeature":467,"showOnPricing":504,"tiers":828},"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.",[826],{"url":827,"release":557},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats\u002F",{"edge":467,"hub":467,"fleet":467},{"id":830,"title":831,"description":832,"docsLink":833,"showOnPricing":504,"tiers":834},"team-members","Team Members","Invite multiple team members to collaborate on the same Node-RED flows.","\u002Fdocs\u002Fuser\u002Fteam\u002F#teams",{"edge":467,"hub":467,"fleet":467},{"id":836,"title":837,"description":838,"docsLink":839,"showOnPricing":504,"tiers":840},"endpoint-security","Endpoint Security","Secure HTTP endpoints for hosted Node-RED instances using FlowFuse credentials.","\u002Fdocs\u002Fuser\u002Finstance-settings\u002F#security",{"edge":467,"hub":467,"fleet":467},{"id":842,"title":843,"description":844,"docsLink":845,"tiers":846},"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":504,"hub":467,"fleet":504},{"id":848,"title":849,"description":850,"tiers":851},"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":504,"hub":467,"fleet":504},{"id":853,"title":854,"features":855},"support","Support",[856,861,865],{"id":857,"title":858,"docsLink":859,"tiers":860},"installation-support","Installation Support","\u002Fdocs\u002Finstall\u002Fintroduction\u002F#do-you-need-help-installation-service",{"edge":467,"hub":467,"fleet":467},{"id":862,"title":863,"showOnPricing":504,"tiers":864},"live-chat-support","Live Chat Support",{"edge":467,"hub":467,"fleet":467},{"id":866,"title":867,"docsLink":868,"tiers":869},"enterprise-support","Enterprise Support","\u002Fdocs\u002Fpremium-support\u002F",{"edge":467,"hub":467,"fleet":467},"feature-catalog","0AnkhTIPCECCwP9NmbTWP5HvRYx4FTSao4lG93-HaWM",[873,876,879,882,885,888,890,893,896,899,902,904,907,910,913,916,919,922,925,928,931,934,937,940,943,946,949,952,955,958,961,964,967,970,973,976,979,982,985,988,991,994,997,1000,1003,1006,1009,1012,1015,1017,1020,1023,1026,1029,1032,1035,1038,1040,1043,1046,1049,1052,1055,1057,1060,1063,1066,1069,1072,1075,1078,1081,1084,1087,1089,1092,1095,1098,1101,1104,1107,1110,1113,1116,1119,1122,1125,1128,1131,1133,1136,1139,1142,1145,1148,1151,1154,1157,1160,1163,1166,1169,1172,1175,1178,1181,1184,1187,1189,1192,1195,1198,1201,1204,1207,1210,1212,1215,1218,1221,1224,1227,1230,1233,1236,1239,1242,1245,1248,1251,1254,1257,1260,1263,1266,1269,1272,1275,1278,1281,1284,1287,1290,1293,1296,1299,1302,1305,1308,1311,1314,1317,1320,1323,1326,1329,1332,1335,1338,1341,1344,1347,1350,1353,1356,1359,1362,1364,1367,1370,1373,1376,1379,1382,1385,1388,1391,1394,1397,1400,1403],{"path":874,"title":875},"\u002Fchangelog\u002F2023\u002F09\u002Fcustom-node-support","Custom Node Support",{"path":877,"title":878},"\u002Fchangelog\u002F2023\u002F09\u002Fdevops-actions","DevOps Pipeline with action selection",{"path":880,"title":881},"\u002Fchangelog\u002F2023\u002F09\u002Fintroduction-enterprise-tier","Introducing the Enterprise Tier",{"path":883,"title":884},"\u002Fchangelog\u002F2023\u002F09\u002Fpipeline-api","API Endpoint for DevOps Pipeline",{"path":886,"title":887},"\u002Fchangelog\u002F2023\u002F09\u002Fsnapshots-devices","Usability improvements to Device Management",{"path":889,"title":597},"\u002Fchangelog\u002F2023\u002F10\u002Fblueprints",{"path":891,"title":892},"\u002Fchangelog\u002F2023\u002F10\u002Fcertified-nodes","Certified Nodes",{"path":894,"title":895},"\u002Fchangelog\u002F2023\u002F10\u002Fdevice-snapshot-selection","Enhanced Snapshot Selection",{"path":897,"title":898},"\u002Fchangelog\u002F2023\u002F10\u002Fpath-bug-fix","Device Agent path bug fix",{"path":900,"title":901},"\u002Fchangelog\u002F2023\u002F10\u002Fresource-alerts","Resource Monitoring in Audit Log",{"path":903,"title":788},"\u002Fchangelog\u002F2023\u002F11\u002F2fa",{"path":905,"title":906},"\u002Fchangelog\u002F2023\u002F11\u002Fdefault-editor","Device Editor enabled by default",{"path":908,"title":909},"\u002Fchangelog\u002F2023\u002F11\u002Fdevices-in-pipelines","Devices in DevOps Pipelines",{"path":911,"title":912},"\u002Fchangelog\u002F2023\u002F11\u002Fproject-nodes-devices","Project Nodes for Devices",{"path":914,"title":915},"\u002Fchangelog\u002F2023\u002F12\u002Fbilling","No Credit Card required for billing",{"path":917,"title":918},"\u002Fchangelog\u002F2023\u002F12\u002Fblueprint-selection","Blueprint Selection Update",{"path":920,"title":921},"\u002Fchangelog\u002F2023\u002F12\u002Fdevice-groups","Device Groups",{"path":923,"title":924},"\u002Fchangelog\u002F2023\u002F12\u002Femail-alerting-node-red-crash","Email Alerts for Audit Log Events",{"path":926,"title":927},"\u002Fchangelog\u002F2023\u002F12\u002Fnode-red-updated","Node-RED 3.1.3 now available",{"path":929,"title":930},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-audit-log","Introducing the Device Auditlog Feature",{"path":932,"title":933},"\u002Fchangelog\u002F2024\u002F01\u002Fdevice-groups-snapshot","Device Groups - Automatic snapshot assignment",{"path":935,"title":936},"\u002Fchangelog\u002F2024\u002F01\u002Ffleet-mode","Renaming \"Default Device Mode\" to \"Fleet Mode\"",{"path":938,"title":939},"\u002Fchangelog\u002F2024\u002F01\u002Fhelm-v2","Helm Chart v2.0",{"path":941,"title":942},"\u002Fchangelog\u002F2024\u002F01\u002Fnew-blueprints","New Blueprints added",{"path":944,"title":945},"\u002Fchangelog\u002F2024\u002F01\u002Fsecurity-updates","Security Updates",{"path":947,"title":948},"\u002Fchangelog\u002F2024\u002F01\u002Fsso-team-membership","Managing Team Membership via SSO",{"path":950,"title":951},"\u002Fchangelog\u002F2024\u002F01\u002Fstreamlined-device-assignment","Streamlined Device assignment",{"path":953,"title":954},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-auto-snapshot","Device Auto Snapshots",{"path":956,"title":957},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-instance-audit-logs","Device Instance Audit Logging",{"path":959,"title":960},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-onboarding-improvements","Device Onboarding Improvements",{"path":962,"title":963},"\u002Fchangelog\u002F2024\u002F02\u002Fdevice-pricing-change","Pricing change for Devices",{"path":965,"title":966},"\u002Fchangelog\u002F2024\u002F02\u002Finstance-auto-snapshots","Instance Auto Snapshots",{"path":968,"title":969},"\u002Fchangelog\u002F2024\u002F02\u002Fpostgresql-upgrade","PostgreSQL Version update",{"path":971,"title":972},"\u002Fchangelog\u002F2024\u002F03\u002Fbearer-token-authentication","Bearer Token Authentication for Node-RED Instances",{"path":974,"title":975},"\u002Fchangelog\u002F2024\u002F03\u002Finstance-protection-mode","Instance Protection Mode",{"path":977,"title":978},"\u002Fchangelog\u002F2024\u002F03\u002Flimits-debug-payload","Configure HTTP Payload and Debug Message size",{"path":980,"title":981},"\u002Fchangelog\u002F2024\u002F03\u002Frestart-devices-remotly","Remote Device Restart",{"path":983,"title":984},"\u002Fchangelog\u002F2024\u002F04\u002Fcustom-nodes-on-devices","Custom Nodes Support on Devices",{"path":986,"title":987},"\u002Fchangelog\u002F2024\u002F04\u002Fdevice-auto-snapshot","Direct Dashboard Access",{"path":989,"title":990},"\u002Fchangelog\u002F2024\u002F04\u002Fimproving-device-groups","Improving Device Groups",{"path":992,"title":993},"\u002Fchangelog\u002F2024\u002F04\u002Fpricing-change","Pricing change Enterprise & Teams Tier",{"path":995,"title":996},"\u002Fchangelog\u002F2024\u002F04\u002Ftougher-rate-limiting","Tougher Rate Limiting on Public Routes",{"path":998,"title":999},"\u002Fchangelog\u002F2024\u002F05\u002Finstance-healthcheck","Customizing instance health-check settings",{"path":1001,"title":1002},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-blueprints","Blueprints added to Library",{"path":1004,"title":1005},"\u002Fchangelog\u002F2024\u002F05\u002Flibrary-flowviewer","Team Library - Flow Viewer",{"path":1007,"title":1008},"\u002Fchangelog\u002F2024\u002F05\u002Fmanaging-node-red-version-on-devices","Managing Node-RED versions on Devices",{"path":1010,"title":1011},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements","Snapshot Improvements",{"path":1013,"title":1014},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-improvements-pt3","Snapshot Upload",{"path":1016,"title":1014},"\u002Fchangelog\u002F2024\u002F05\u002Fsnapshot-upload",{"path":1018,"title":1019},"\u002Fchangelog\u002F2024\u002F06\u002Fdevice-agent-proxy-support","Running the Device Agent behind an HTTP proxy",{"path":1021,"title":1022},"\u002Fchangelog\u002F2024\u002F06\u002Flibrary-blueprints","Custom hostnames for your instances",{"path":1024,"title":1025},"\u002Fchangelog\u002F2024\u002F06\u002Fmultiline-env-vars","Multi-line Environment Variables",{"path":1027,"title":1028},"\u002Fchangelog\u002F2024\u002F06\u002Fsnapshot-flow-compare","Compare Snapshots flows",{"path":1030,"title":1031},"\u002Fchangelog\u002F2024\u002F07\u002Fapplications-search","Applications Search",{"path":1033,"title":1034},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-group-clear-snapshot","Device Groups Snapshots",{"path":1036,"title":1037},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-delete","Managing devices",{"path":1039,"title":1037},"\u002Fchangelog\u002F2024\u002F07\u002Fdevice-management-bulk-move",{"path":1041,"title":1042},"\u002Fchangelog\u002F2024\u002F07\u002Fedit-snapshots","Edit Snapshots",{"path":1044,"title":1045},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant","The FlowFuse Expert",{"path":1047,"title":1048},"\u002Fchangelog\u002F2024\u002F07\u002Fflowfuse-assistant-json","FlowFuse Expert Writes JSON",{"path":1050,"title":1051},"\u002Fchangelog\u002F2024\u002F07\u002Fimmersive-editor","Immersive Editor Experience",{"path":1053,"title":1054},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-inbox","Notifications Inbox",{"path":1056,"title":1054},"\u002Fchangelog\u002F2024\u002F07\u002Fnotifications-update",{"path":1058,"title":1059},"\u002Fchangelog\u002F2024\u002F07\u002Fpersistent-storage","Persistent Storage on FlowFuse Cloud",{"path":1061,"title":1062},"\u002Fchangelog\u002F2024\u002F07\u002Fsso","Single Sign On Updates",{"path":1064,"title":1065},"\u002Fchangelog\u002F2024\u002F08\u002Fbill-of-materials","Bill of Materials",{"path":1067,"title":1068},"\u002Fchangelog\u002F2024\u002F08\u002Fenterprise-license-update","Enforcing Enterprise Restrictions",{"path":1070,"title":1071},"\u002Fchangelog\u002F2024\u002F08\u002Fldap-sso-groups","LDAP Single Sign On Updates",{"path":1073,"title":1074},"\u002Fchangelog\u002F2024\u002F08\u002Fstatic-file-service-navigation-visibility","Static File Service Navigation and Visibility",{"path":1076,"title":1077},"\u002Fchangelog\u002F2024\u002F10\u002Fdevice-group-env-vars","Environment Variables for your Device Groups",{"path":1079,"title":1080},"\u002Fchangelog\u002F2024\u002F10\u002Fmqtt-service","MQTT Broker Service",{"path":1082,"title":1083},"\u002Fchangelog\u002F2024\u002F10\u002Fnotifications-bulk-actions","Managing Notifications",{"path":1085,"title":1086},"\u002Fchangelog\u002F2024\u002F10\u002Fsnapshot-download-upload-options","Snapshot Upload and Download Improvements",{"path":1088,"title":727},"\u002Fchangelog\u002F2024\u002F10\u002Fversion-history-timeline",{"path":1090,"title":1091},"\u002Fchangelog\u002F2024\u002F11\u002Faudit-log-hierarchy","Audit logs show hierarchical events",{"path":1093,"title":1094},"\u002Fchangelog\u002F2024\u002F11\u002Fdevice-agent-release","Device Agent 3.0 released",{"path":1096,"title":1097},"\u002Fchangelog\u002F2024\u002F11\u002Fmqtt-topic-hierarchy","MQTT Topic Hierarchy view",{"path":1099,"title":1100},"\u002Fchangelog\u002F2024\u002F11\u002Fteam-search","Team-wide search",{"path":1102,"title":1103},"\u002Fchangelog\u002F2024\u002F12\u002Fdashboad-iframe","Allow Dashboards to be embedded in iFrames",{"path":1105,"title":1106},"\u002Fchangelog\u002F2024\u002F12\u002Fdevice-editor-cache","Device Editor Access Speed Up",{"path":1108,"title":1109},"\u002Fchangelog\u002F2024\u002F12\u002Fteam-bom-timeline","Team BOM and Pipeline Views",{"path":1111,"title":1112},"\u002Fchangelog\u002F2025\u002F01\u002Ffree-tier-onboarding","New Onboarding Tour for Free Tier Users",{"path":1114,"title":1115},"\u002Fchangelog\u002F2025\u002F01\u002Fhidden-env-vars","Hidden Environment Variables",{"path":1117,"title":1118},"\u002Fchangelog\u002F2025\u002F01\u002Fimproved-diagnostics","Improved Diagnostics",{"path":1120,"title":1121},"\u002Fchangelog\u002F2025\u002F01\u002Fteam-level-groups","Team level view of Groups",{"path":1123,"title":1124},"\u002Fchangelog\u002F2025\u002F02\u002Fadditional-device-version-history-events","New Remote Instances Version History Events",{"path":1126,"title":1127},"\u002Fchangelog\u002F2025\u002F02\u002Fbroker-error-feedback","Improved Broker Connection Feedback",{"path":1129,"title":1130},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-agent-updates","FlowFuse User Authentication on Remote Instances",{"path":1132,"title":727},"\u002Fchangelog\u002F2025\u002F02\u002Fdevice-version-history-timeline",{"path":1134,"title":1135},"\u002Fchangelog\u002F2025\u002F02\u002Fexternal-brokers","External MQTT Brokers",{"path":1137,"title":1138},"\u002Fchangelog\u002F2025\u002F02\u002Fmqtt-schema-suggestions","MQTT Smart Schema Suggestions",{"path":1140,"title":1141},"\u002Fchangelog\u002F2025\u002F02\u002Fresend-and-extend-team-invitation-expiration","Re-send Team Invitations",{"path":1143,"title":1144},"\u002Fchangelog\u002F2025\u002F02\u002Fschema-docs","Personalized Schema Documentation",{"path":1146,"title":1147},"\u002Fchangelog\u002F2025\u002F02\u002Ftopic-hierarchy-search","Search & Filter for Topic Hierarchy List",{"path":1149,"title":1150},"\u002Fchangelog\u002F2025\u002F03\u002Fcontainer-tags","Changes to tags for flowfuse\u002Fnode-red",{"path":1152,"title":1153},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-groups","Multiple Device Groups in a pipeline",{"path":1155,"title":1156},"\u002Fchangelog\u002F2025\u002F03\u002Fdevice-local-login","Local Login for Remote Instances",{"path":1158,"title":1159},"\u002Fchangelog\u002F2025\u002F03\u002Ffree-tier","Free Tier now more accessible to all",{"path":1161,"title":1162},"\u002Fchangelog\u002F2025\u002F03\u002Fresource-notifications","Resource Alerts",{"path":1164,"title":1165},"\u002Fchangelog\u002F2025\u002F03\u002Fsnapshot-filter","Filtering Snapshots",{"path":1167,"title":1168},"\u002Fchangelog\u002F2025\u002F03\u002Fteam-npm-registry","NPM Package Hosting",{"path":1170,"title":1171},"\u002Fchangelog\u002F2025\u002F03\u002Ftopic-deletion","MQTT Topic Management",{"path":1173,"title":1174},"\u002Fchangelog\u002F2025\u002F04\u002Fdevice-provisioning","Remote Instance Provisioning",{"path":1176,"title":1177},"\u002Fchangelog\u002F2025\u002F04\u002Fgit-integration","Git Integration with Pipelines",{"path":1179,"title":1180},"\u002Fchangelog\u002F2025\u002F04\u002Finstance-log-browsing","Better Node-RED log handling",{"path":1182,"title":1183},"\u002Fchangelog\u002F2025\u002F05\u002Fimport-node-red-flows","Import Node-RED Flows During Remote Instance Setup",{"path":1185,"title":1186},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant","FlowFuse Expert just got smarter",{"path":1188,"title":1186},"\u002Fchangelog\u002F2025\u002F06\u002Fflowfuse-assistant-2",{"path":1190,"title":1191},"\u002Fchangelog\u002F2025\u002F06\u002Fgit-integration","Pulling snapshots from Git with Pipelines",{"path":1193,"title":1194},"\u002Fchangelog\u002F2025\u002F06\u002Finstance-performance-memory","Memory Metrics in Instance Performance View",{"path":1196,"title":1197},"\u002Fchangelog\u002F2025\u002F06\u002Fnew-home-page","Introducing the New Home Page Experience",{"path":1199,"title":1200},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance","Team Performance Feature",{"path":1202,"title":1203},"\u002Fchangelog\u002F2025\u002F06\u002Fteam-performance-view","Instance Performance View",{"path":1205,"title":1206},"\u002Fchangelog\u002F2025\u002F06\u002Fui-refresh","Navigation UI Refresh",{"path":1208,"title":1209},"\u002Fchangelog\u002F2025\u002F07\u002Fbrowse-node-red-flows","Browse for Node-RED Flows During Remote Instance Setup",{"path":1211,"title":551},"\u002Fchangelog\u002F2025\u002F07\u002Fflowfuse-tables",{"path":1213,"title":1214},"\u002Fchangelog\u002F2025\u002F07\u002Fimport-blueprints","Import blueprints directly into your existing instances",{"path":1216,"title":1217},"\u002Fchangelog\u002F2025\u002F07\u002Fsimplified-applications-overview","Simplified Applications Page with Summary Tiles",{"path":1219,"title":1220},"\u002Fchangelog\u002F2025\u002F07\u002Fsmart-suggestions","Smart Suggestions",{"path":1222,"title":1223},"\u002Fchangelog\u002F2025\u002F07\u002Fteam-to-pro-plan-rename","Team Plan Renamed to Pro Plan",{"path":1225,"title":1226},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-hosted","Generate snapshot descriptions with AI",{"path":1228,"title":1229},"\u002Fchangelog\u002F2025\u002F08\u002Fai-generated-snapshot-descriptions-remote","AI Snapshot Descriptions Now Work with Remote Instances",{"path":1231,"title":1232},"\u002Fchangelog\u002F2025\u002F08\u002Fdevice-performance","FlowFuse Remote Instance Performance Data",{"path":1234,"title":1235},"\u002Fchangelog\u002F2025\u002F08\u002Fdirect-sso","Direct SSO Login",{"path":1237,"title":1238},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-assistant","FlowFuse Expert documents your flows",{"path":1240,"title":1241},"\u002Fchangelog\u002F2025\u002F08\u002Fflowfuse-mqtt","FlowFuse MQTT",{"path":1243,"title":1244},"\u002Fchangelog\u002F2025\u002F08\u002Fhttp-cors","Configure HTTP CORS",{"path":1246,"title":1247},"\u002Fchangelog\u002F2025\u002F08\u002Fsubflow-export","Export SubFlow as Node-RED module",{"path":1249,"title":1250},"\u002Fchangelog\u002F2025\u002F08\u002Ftables-assistant","FlowFuse Tables with a little help from the Assistant",{"path":1252,"title":1253},"\u002Fchangelog\u002F2025\u002F09\u002Fexpose-saml-groups-to-dashboard","Allow SSO groups to be shared with the Node-RED Dashboard",{"path":1255,"title":1256},"\u002Fchangelog\u002F2025\u002F09\u002Finline-assist","FlowFuse Expert can help you write code",{"path":1258,"title":1259},"\u002Fchangelog\u002F2025\u002F09\u002Fretiring-flowforge-device-agent","No more @flowforge\u002Fflowforge-device-agent releases",{"path":1261,"title":1262},"\u002Fchangelog\u002F2025\u002F09\u002Frevised-instance-snapshot-ui","Streamlined Snapshot Management",{"path":1264,"title":1265},"\u002Fchangelog\u002F2025\u002F09\u002Fteam-broker-async-api","Capture Async API data from FlowFuse Team Broker",{"path":1267,"title":1268},"\u002Fchangelog\u002F2025\u002F10\u002Fapplication-level-rbac","Application-level access control for Enterprise teams",{"path":1270,"title":1271},"\u002Fchangelog\u002F2025\u002F10\u002Fbulk-device-group-assignment","Easier Access to Bulk Device Group Management",{"path":1273,"title":1274},"\u002Fchangelog\u002F2025\u002F10\u002Fduplicate-instances-across-applications","Duplicate Instances Across Different Applications",{"path":1276,"title":1277},"\u002Fchangelog\u002F2025\u002F10\u002Fimport-flows-on-instance-creation","Import flows during instance creation",{"path":1279,"title":1280},"\u002Fchangelog\u002F2025\u002F10\u002Fmcp-nodes","FlowFuse MCP Server Nodes",{"path":1282,"title":1283},"\u002Fchangelog\u002F2025\u002F10\u002Fonnx-nodes","FlowFuse AI Nodes",{"path":1285,"title":1286},"\u002Fchangelog\u002F2025\u002F10\u002Fsettings-page-device-group-management","Device Group Management from Settings Page",{"path":1288,"title":1289},"\u002Fchangelog\u002F2025\u002F11\u002Fff-expert-update","FlowFuse Expert Update",{"path":1291,"title":1292},"\u002Fchangelog\u002F2025\u002F11\u002Fminimum-nodejs-version","Node.js v20 Minimum Version Requirement",{"path":1294,"title":1295},"\u002Fchangelog\u002F2025\u002F11\u002Fsso-session","SSO control over Session life",{"path":1297,"title":1298},"\u002Fchangelog\u002F2025\u002F12\u002Fff-expert-mcp-insights","FlowFuse Expert: Now with MCP-Powered Insights",{"path":1300,"title":1301},"\u002Fchangelog\u002F2025\u002F12\u002Fscheduled-maintenance","Scheduled Maintenance Mode",{"path":1303,"title":1304},"\u002Fchangelog\u002F2026\u002F01\u002Fdevice-agent-containers","Device Agent Docker Containers updated",{"path":1306,"title":1307},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-manage-palette","FlowFuse Expert: Enhanced Palette Integration",{"path":1309,"title":1310},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-nr-actions","FlowFuse Expert: Integration with Node-RED",{"path":1312,"title":1313},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-palette-queries","FlowFuse Expert: Palette Queries",{"path":1315,"title":1316},"\u002Fchangelog\u002F2026\u002F01\u002Fff-expert-select-flows","FlowFuse Expert: Ask about your flows",{"path":1318,"title":1319},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-rbacs","FlowFuse Expert: MCP-Powered Insights with RBACs",{"path":1321,"title":1322},"\u002Fchangelog\u002F2026\u002F01\u002Fmcp-security","FlowFuse Expert: MCP-Powered Insights",{"path":1324,"title":1325},"\u002Fchangelog\u002F2026\u002F02\u002Fdevice-agent-nodejs-options","Set Node.js Options for Remote Instances",{"path":1327,"title":1328},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-debug-log-context","FlowFuse Expert: Helping you make sense of your debug log",{"path":1330,"title":1331},"\u002Fchangelog\u002F2026\u002F02\u002Fff-expert-update-banner","FlowFuse Expert: Never Miss an Update",{"path":1333,"title":1334},"\u002Fchangelog\u002F2026\u002F02\u002Fha-instance-rolling-restart","HA Hosted Instance Rolling Restart",{"path":1336,"title":1337},"\u002Fchangelog\u002F2026\u002F02\u002Fremote-instances-immersive-editor","Immersive Mode for Remote Instances",{"path":1339,"title":1340},"\u002Fchangelog\u002F2026\u002F02\u002Frestoring-snapshots-to-remote-instances","Restoring snapshots to developer-mode Remote Instances",{"path":1342,"title":1343},"\u002Fchangelog\u002F2026\u002F03\u002Fazure-dev-ops-gitops","Azure DevOps Pipeline support",{"path":1345,"title":1346},"\u002Fchangelog\u002F2026\u002F03\u002Fdeveloper-mode-in-immersive-editor","Developer Mode Now Accessible from the Immersive Editor",{"path":1348,"title":1349},"\u002Fchangelog\u002F2026\u002F03\u002Fembedded-editor-tab-title","Embedded Editor Now Shows Active Tab",{"path":1351,"title":1352},"\u002Fchangelog\u002F2026\u002F03\u002Fmarch-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on March 28th, 2026",{"path":1354,"title":1355},"\u002Fchangelog\u002F2026\u002F03\u002Fsnapshot-detail-modal-immersive-editor","View Snapshot Details in the Immersive Editor",{"path":1357,"title":1358},"\u002Fchangelog\u002F2026\u002F04\u002Fexpert-action-links","FlowFuse expert action links",{"path":1360,"title":1361},"\u002Fchangelog\u002F2026\u002F04\u002Fhosted-instance-url-env-var","Hosted Instances know their own URL",{"path":1363,"title":620},"\u002Fchangelog\u002F2026\u002F04\u002Fimmersive-editor-drawer",{"path":1365,"title":1366},"\u002Fchangelog\u002F2026\u002F04\u002Fsnapshot-diff-viewer","Richer snapshot comparison view",{"path":1368,"title":1369},"\u002Fchangelog\u002F2026\u002F05\u002Fai-opt-out","AI Feature Opt-Out for Teams",{"path":1371,"title":1372},"\u002Fchangelog\u002F2026\u002F05\u002Fexpert-application-building","FlowFuse Expert Builds Your Application",{"path":1374,"title":1375},"\u002Fchangelog\u002F2026\u002F05\u002Fsingle-sso-provider","Single SSO provider for all users",{"path":1377,"title":1378},"\u002Fchangelog\u002F2026\u002F06\u002Fdark-mode","Dark Mode",{"path":1380,"title":1381},"\u002Fchangelog\u002F2026\u002F06\u002Fdevice-agent-v4-released","Device Agent v4 released",{"path":1383,"title":1384},"\u002Fchangelog\u002F2026\u002F06\u002Fgeneric-git-server-support","Connect Pipelines to Any Git Server",{"path":1386,"title":1387},"\u002Fchangelog\u002F2026\u002F06\u002Fjuly-scheduled-maintenance","Updated: Upcoming Scheduled Server Maintenance on July 11th, 2026",{"path":1389,"title":1390},"\u002Fchangelog\u002F2026\u002F07\u002Fapplication-sso-groups","Application Roles from SSO Groups",{"path":1392,"title":1393},"\u002Fchangelog\u002F2026\u002F07\u002Fdevice-agent-onboarding","Getting started with FlowFuse straight from the terminal",{"path":1395,"title":1396},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-enhancements","FlowFuse Expert Enhancements",{"path":1398,"title":1399},"\u002Fchangelog\u002F2026\u002F07\u002Fexpert-tables-automation","FlowFuse Expert Can Now Work With Your Tables",{"path":1401,"title":1402},"\u002Fchangelog\u002F2026\u002F07\u002Fscoped-pats","Team Scoped Personal Access Tokens",{"path":1404,"title":1405},"\u002Fchangelog\u002F2026\u002F07\u002Fteam-and-application-dashboards","A Dedicated Home for Your Dashboards",[],1786105897981]