[{"data":1,"prerenderedAt":225},["ShallowReactive",2],{"application-guide-nav":3,"application-guide-flowfuse-foundations":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":17,"blocks":103,"blurb":19,"extension":221,"guide":5,"meta":222,"navOrder":18,"slug":16,"stem":223,"__hash__":224},"applicationGuide\u002Fapplication-guide\u002Fflowfuse\u002F02-foundations.yml",[104,163,186,193,209,213],{"type":105,"heading":106,"lanes":107,"legend":156},"diagram","The big picture",[108,125,127,134,136],{"label":109,"tone":110,"nodes":111},"FlowFuse platform — runs and connects your Node-RED instances","it",[112,115,118,122],{"title":113,"sub":114,"tone":110},"Hosted Instance","one or many, in the cloud",{"title":116,"sub":117,"tone":110},"Dashboard","live operator UI",{"title":119,"sub":120,"tone":121},"Team Broker","MQTT message bus","broker",{"title":123,"sub":124,"tone":110},"FlowFuse Tables","shared SQL database",{"link":126},"Device Agent — bridges platform to the edge",{"label":128,"tone":129,"nodes":130},"Remote Instances — one per device, across sites","ot",[131],{"title":132,"sub":133,"tone":129},"Remote Instance","one per device, across sites",{"link":135},"reads",{"label":137,"tone":138,"nodes":139},"Edge hardware","neutral",[140,144,147,150,153],{"title":141,"sub":142,"tone":143},"PLC","controller","muted",{"title":145,"sub":146,"tone":143},"IO module","sensors & actuators",{"title":148,"sub":149,"tone":143},"Gateway","protocol bridge",{"title":151,"sub":152,"tone":143},"Embedded","microcontroller",{"title":154,"sub":155,"tone":143},"LoRaWAN GW","wireless sensors",[157,159,161],{"label":158,"tone":110},"Platform",{"label":160,"tone":129},"Edge",{"label":162,"tone":143},"Hardware",{"type":164,"heading":165,"columns":18,"items":166},"cards","The core pieces",[167,170,173,175,178,181,184],{"title":168,"body":169},"Single platform","Manage, secure, and govern everything from one place.",{"title":171,"body":172},"Instances","Node-RED runtimes. A Hosted Instance runs on FlowFuse-managed infrastructure (cloud or your own server); a Remote Instance runs on your own edge hardware via the Device Agent. Same Node-RED, managed the same way — they differ only in where the runtime lives.",{"title":119,"body":174},"A shared message bus that ties data together across sites.",{"title":176,"body":177},"Database","One shared operational data store.",{"title":179,"body":180},"Dashboards","Operator-facing UIs for the people who run it.",{"title":182,"body":183},"Edge & device management","Deploy and manage across many devices, lines, and plants.",{"title":132,"body":185},"A Remote Instance lives in both worlds — edge execution down in OT, or an on-prem worker under an IT\u002Fcloud platform.",{"type":187,"heading":188,"body":189,"link":190},"note","In the FlowFuse docs","That's the mental model in plain language. For the full glossary — every FlowFuse piece and term (Applications, Instances, Snapshots, Pipelines, Team Broker, Tables, Devices and more) — see the FlowFuse Concepts documentation.",{"label":191,"to":192},"FlowFuse Concepts documentation →","\u002Fdocs\u002Fuser\u002Fconcepts\u002F",{"type":194,"heading":195,"items":196},"steps","The method, in four moves",[197,200,203,206],{"title":198,"body":199},"Say what it does","One plain sentence. No nouns you would have to explain.",{"title":201,"body":202},"Pick the package","Match it to a package — often several (most real apps are more than one piece).",{"title":204,"body":205},"Decide where data goes","Choose the target(s): FlowFuse Tables (relational), an external time-series DB, the Team Broker, or a single service.",{"title":207,"body":208},"Read off the sentence","Package plus target is the architecture, stated in one line.",{"type":210,"heading":211,"body":212},"prose","How code gets shared","Two ways code moves in FlowFuse: promote a whole app through environments, or compose an app from shared parts. Both live on the App delivery methods page — and when dev and prod sit on separate servers, a GitHub bridge (an architecture decision) carries the versioned code between them.",{"type":214,"columns":8,"items":215},"linkCards",[216],{"title":217,"body":218,"link":219},"See the delivery methods","Whole app or reusable pieces — how a build reaches every place that should run it.",{"label":220,"to":29},"App delivery methods →","yml",{},"application-guide\u002Fflowfuse\u002F02-foundations","2Gv4EtI9n0U8CYsoGsInkpgiogW7qtuC3jzd1xymWi4",1786132520467]