[{"data":1,"prerenderedAt":173},["ShallowReactive",2],{"application-guide-nav":3,"application-guide-flowfuse-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":70,"blocks":103,"blurb":72,"extension":169,"guide":5,"meta":170,"navOrder":71,"slug":69,"stem":171,"__hash__":172},"applicationGuide\u002Fapplication-guide\u002Fflowfuse\u002F07-architectures.yml",[104,107,122,125,128,164],{"type":105,"body":106},"prose","Every FlowFuse deployment is the same building blocks — instances, broker, data, edge — arranged for where it runs. Read any diagram as a vertical stack, then pick the world you're designing for.",{"type":108,"columns":27,"items":109},"linkCards",[110,114,118],{"title":87,"body":111,"link":112},"Near the equipment — edge deployments with the server in IT or in an OT\u002FDMZ, hardware-saving consolidation, and air-gapped sites.",{"label":113,"to":90},"View OT →",{"title":81,"body":115,"link":116},"Hosting and governing — on-prem, your cloud per-site, hosting choice at scale, enterprise governance, and secure data exposure.",{"label":117,"to":84},"View IT →",{"title":93,"body":119,"link":120},"The live data backbone — a Unified Namespace where edge publishes once and many subscribe, across every site.",{"label":121,"to":96},"View IIoT →",{"type":105,"heading":123,"body":124},"Separating dev from prod","A modifier for any of the three worlds above. When your development server is a different server from production — dev in IT or the cloud, prod down in OT or air-gapped — a GitHub bridge carries the same versioned code across the boundary.",{"type":105,"kicker":126,"body":127},"Modifier · works across OT, IT & IIoT — GitHub bridge","A pipeline pushes your dev work up to a repo; each site's instance pulls it back down. One versioned source of truth — with review, history and rollback in Git — and dev kept safely off the production deployment servers.",{"type":129,"lanes":130,"legend":161},"diagram",[131,138,140,148,150],{"label":132,"tone":133,"nodes":134},"Dev · one build","it",[135],{"title":136,"sub":137,"tone":133},"Dev instance","develop once",{"link":139},"pipeline push",{"label":141,"tone":142,"nodes":143},"Versioned source of truth","neutral",[144],{"title":145,"sub":146,"tone":147},"GitHub","versioned source of truth","muted",{"link":149},"pull",{"label":151,"tone":152,"nodes":153},"Sites · prod instances (OT & IT)","ot",[154,157,159],{"title":155,"sub":156,"tone":152},"Instance","Site A · OT",{"title":155,"sub":158,"tone":133},"Site B · IT",{"title":155,"sub":160,"tone":152},"Site C · OT",[162],{"label":163,"tone":142},"push \u002F pull",{"type":165,"body":166,"link":167},"note","Once code is on a server, it ships via snapshots or subflows.",{"label":168,"to":29},"App delivery methods →","yml",{},"application-guide\u002Fflowfuse\u002F07-architectures","beG7pb1COiHM-af3Ijmt85ZdNzlAhMPI9Lu-j454SwQ",1786134120511]