[{"data":1,"prerenderedAt":284},["ShallowReactive",2],{"application-guide-nav":3,"application-guide-flowfuse-ot-architectures":101},[4,11,15,21,24,30,35,41,46,52,57,63,68,74,79,85,91,97],{"guide":5,"slug":6,"title":7,"navOrder":8,"blurb":9,"path":10},"flowfuse","overview","Overview",1,"Turn an app idea into FlowFuse pieces you can name and say in one sentence.","\u002Fapplication-guide\u002Fflowfuse\u002Foverview\u002F",{"guide":12,"slug":6,"title":7,"navOrder":8,"blurb":13,"path":14},"node-red","Turn an architecture sentence into a clean flow shape you can read at a glance.","\u002Fapplication-guide\u002Fnode-red\u002Foverview\u002F",{"guide":5,"slug":16,"title":17,"navOrder":18,"blurb":19,"path":20},"foundations","Foundations",2,"The foundation to build on: what FlowFuse is, its core pieces, and how code is shared across teams.","\u002Fapplication-guide\u002Fflowfuse\u002Ffoundations\u002F",{"guide":12,"slug":16,"title":17,"navOrder":18,"blurb":22,"path":23},"The handful of concepts you need to build with Node-RED, and how they fit together.","\u002Fapplication-guide\u002Fnode-red\u002Ffoundations\u002F",{"guide":5,"slug":25,"title":26,"navOrder":27,"blurb":28,"path":29},"app-delivery-methods","App delivery methods",3,"Two different units of code, delivered two ways: ship the whole app, or publish one reusable piece.","\u002Fapplication-guide\u002Fflowfuse\u002Fapp-delivery-methods\u002F",{"guide":12,"slug":31,"title":32,"navOrder":27,"blurb":33,"path":34},"flow-shape","Flow shape","Turn an architecture sentence into a flow you can read at a glance.","\u002Fapplication-guide\u002Fnode-red\u002Fflow-shape\u002F",{"guide":5,"slug":36,"title":37,"navOrder":38,"blurb":39,"path":40},"hardware-apps","Hardware apps",4,"The three shapes a FlowFuse app takes when it runs on a device.","\u002Fapplication-guide\u002Fflowfuse\u002Fhardware-apps\u002F",{"guide":12,"slug":42,"title":43,"navOrder":38,"blurb":44,"path":45},"design-patterns","Design patterns","The moves that turn a flow into something you can reuse, test and hand off.","\u002Fapplication-guide\u002Fnode-red\u002Fdesign-patterns\u002F",{"guide":5,"slug":47,"title":48,"navOrder":49,"blurb":50,"path":51},"software-apps","Software apps",5,"The three shapes a FlowFuse app takes when it runs on the platform.","\u002Fapplication-guide\u002Fflowfuse\u002Fsoftware-apps\u002F",{"guide":12,"slug":53,"title":54,"navOrder":49,"blurb":55,"path":56},"handling-data","Handling data","Sort data by what it is for before you tune anything.","\u002Fapplication-guide\u002Fnode-red\u002Fhandling-data\u002F",{"guide":5,"slug":58,"title":59,"navOrder":60,"blurb":61,"path":62},"data-plane","Data plane",6,"Before you pick where things run, decide how data is handled.","\u002Fapplication-guide\u002Fflowfuse\u002Fdata-plane\u002F",{"guide":12,"slug":64,"title":65,"navOrder":60,"blurb":66,"path":67},"operating-flows","Operating flows","Four operational habits that keep a flow running when the real world pushes back.","\u002Fapplication-guide\u002Fnode-red\u002Foperating-flows\u002F",{"guide":5,"slug":69,"title":70,"navOrder":71,"blurb":72,"path":73},"architectures","Architectures",7,"The same building blocks, arranged for where they run.","\u002Fapplication-guide\u002Fflowfuse\u002Farchitectures\u002F",{"guide":12,"slug":75,"title":76,"navOrder":71,"blurb":77,"path":78},"worked-example","Worked example","The shape rules and patterns applied end to end.","\u002Fapplication-guide\u002Fnode-red\u002Fworked-example\u002F",{"guide":5,"slug":80,"title":81,"navOrder":82,"blurb":83,"path":84},"it-architectures","IT architectures",8,"Hosting the platform and serving the wider organisation.","\u002Fapplication-guide\u002Fflowfuse\u002Fit-architectures\u002F",{"guide":5,"slug":86,"title":87,"navOrder":88,"blurb":89,"path":90},"ot-architectures","OT architectures",9,"How FlowFuse deploys in operational-technology environments, near the equipment.","\u002Fapplication-guide\u002Fflowfuse\u002Fot-architectures\u002F",{"guide":5,"slug":92,"title":93,"navOrder":94,"blurb":95,"path":96},"iiot-architectures","IIoT architectures",10,"Distributed edge nodes, each doing one small job, feeding one central system.","\u002Fapplication-guide\u002Fflowfuse\u002Fiiot-architectures\u002F",{"guide":5,"slug":75,"title":76,"navOrder":98,"blurb":99,"path":100},11,"OEE, end to end — two packages, two connections.","\u002Fapplication-guide\u002Fflowfuse\u002Fworked-example\u002F",{"id":102,"title":87,"blocks":103,"blurb":89,"extension":280,"guide":5,"meta":281,"navOrder":88,"slug":86,"stem":282,"__hash__":283},"applicationGuide\u002Fapplication-guide\u002Fflowfuse\u002F09-ot-architectures.yml",[104,107,272],{"type":105,"kicker":87,"body":106},"prose","How FlowFuse deploys in operational-technology environments, near the equipment. Read each diagram bottom-up: equipment on the floor, the platform above. The Remote Instance is the execution layer that lives down in OT.",{"type":108,"panels":109},"tabs",[110,158,202,238],{"label":111,"kicker":112,"diagram":113,"summary":156,"useWhen":157},"Edge · server in IT","Server in IT, execution in OT",{"lanes":114,"legend":147},[115,122,124,133,135],{"label":116,"tone":117,"nodes":118},"IT infrastructure","it",[119],{"title":120,"sub":121,"tone":117},"FlowFuse server","in IT infrastructure",{"link":123},"manages across the boundary",{"label":125,"tone":126,"nodes":127},"OT environment","ot",[128,131,132],{"title":129,"sub":130,"tone":126},"Remote Instance","on OT equipment",{"title":129,"sub":130,"tone":126},{"title":129,"sub":130,"tone":126},{"link":134},"reads",{"label":136,"tone":137,"nodes":138},"Equipment","neutral",[139,143,145],{"title":140,"sub":141,"tone":142},"PLCs","Line A","muted",{"title":140,"sub":144,"tone":142},"Line B",{"title":140,"sub":146,"tone":142},"Line C",[148,150,152,154],{"label":149,"tone":117},"IT zone",{"label":151,"tone":126},"OT zone",{"label":153,"tone":137},"Authenticated",{"label":155,"tone":142},"Local wire","The FlowFuse server lives up in the IT infrastructure; the Remote Instances live down in the OT environment on the equipment. The server deploys to and manages them across the IT\u002FOT boundary, while each Remote Instance keeps running locally if the link drops.","IT owns and hosts the platform, but execution must sit next to the machines in OT.",{"label":159,"kicker":160,"diagram":161,"summary":200,"useWhen":201},"Edge · server in OT \u002F DMZ","Platform inside the plant, exposed through a DMZ",{"lanes":162,"legend":194},[163,169,171,177,179,188,189],{"label":164,"tone":117,"nodes":165},"IT · corporate network",[166],{"title":167,"sub":168,"tone":117},"Corporate systems","MES \u002F ERP \u002F dashboards",{"link":170},"controlled uplink · firewall",{"label":172,"tone":173,"nodes":174},"DMZ · firewall-segregated","dmz",[175],{"title":120,"sub":176,"tone":117},"in the DMZ",{"link":178},"firewall",{"label":180,"tone":126,"nodes":181},"OT network",[182,184,186],{"title":129,"sub":183,"tone":126},"IPC · Area 1",{"title":129,"sub":185,"tone":126},"IPC · Area 2",{"title":129,"sub":187,"tone":126},"embedded · Area 3",{"link":134},{"label":136,"tone":137,"nodes":190},[191,192,193],{"title":140,"tone":142},{"title":140,"tone":142},{"title":140,"tone":142},[195,196,198,199],{"label":149,"tone":117},{"label":197,"tone":173},"DMZ",{"label":151,"tone":126},{"label":155,"tone":142},"The FlowFuse server sits inside the plant, firewall-segregated in a DMZ, with a controlled uplink to corporate systems and Remote Instances on IPCs and embedded hardware in the OT network below. Nothing reaches OT except through the firewalls.","Security policy keeps the platform inside the plant boundary, exposed only through a DMZ.",{"label":203,"kicker":204,"diagram":205,"summary":236,"useWhen":237},"Air-gapped","No internet, in or out",{"lanes":206,"legend":232},[207,212,213,219,221,227,228],{"label":208,"tone":137,"nodes":209},"Internet",[210],{"title":208,"sub":211,"tone":142},"blocked",{"link":211},{"label":214,"tone":126,"nodes":215},"OT network · no internet",[216],{"title":217,"sub":218,"tone":126},"FlowFuse","self-managed · on-site",{"link":220},"deploys",{"label":222,"tone":126,"nodes":223},"Site apps",[224],{"title":225,"sub":226,"tone":126},"Instances","site apps",{"link":134},{"label":136,"tone":137,"nodes":229},[230],{"title":140,"sub":231,"tone":142},"equipment",[233,234,235],{"label":151,"tone":126},{"label":153,"tone":137},{"label":155,"tone":142},"The DMZ pattern taken to its extreme: a self-managed FlowFuse runs on a server inside an isolated OT network with no internet at all. It manages that site's instances and devices entirely within the OT boundary — nothing goes in or out.","Site security policy forbids any internet traffic in or out of the OT network.",{"label":239,"kicker":240,"diagram":241,"summary":270,"useWhen":271},"Edge · hardware-saving","One server near the line, several Hosted Instances on it",{"lanes":242,"legend":267},[243,248,250,260,262],{"label":244,"tone":126,"nodes":245},"OT · on-site, close to the equipment",[246],{"title":120,"sub":247,"tone":126},"on-site · near the line",{"link":249},"runs",{"label":251,"tone":137,"nodes":252},"Hosted Instances doing the edge work",[253,256,258],{"title":254,"sub":255},"Hosted Instance","does Line A's work",{"title":254,"sub":257},"does Line B's work",{"title":254,"sub":259},"does Line C's work",{"link":261},"talks to equipment",{"label":136,"tone":137,"nodes":263},[264,265,266],{"title":140,"sub":141,"tone":142},{"title":140,"sub":144,"tone":142},{"title":140,"sub":146,"tone":142},[268,269],{"label":151,"tone":126},{"label":155,"tone":142},"Instead of a Remote Instance on every device, deploy one FlowFuse server close to the line and run several Hosted Instances on it — each doing the work an edge device would have done, talking to its equipment directly. Fewer physical boxes to buy and maintain, same separation of concerns.","You want the edge workloads consolidated onto nearby server hardware to cut device count.",{"type":273,"columns":8,"items":274},"linkCards",[275],{"title":276,"body":277,"link":278},"Where does the data live?","Every architecture here sits on the same data plane — built-in Tables & Broker, or bring your own over Project Link.",{"label":279,"to":62},"Data plane →","yml",{},"application-guide\u002Fflowfuse\u002F09-ot-architectures","5HgPB2JozqrfyXJQgYkvyoASgGHcM409LI6J5Lt4-80",1786134120511]