[{"data":1,"prerenderedAt":211},["ShallowReactive",2],{"application-guide-nav":3,"application-guide-flowfuse-overview":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":7,"blocks":103,"blurb":9,"extension":207,"guide":5,"meta":208,"navOrder":8,"slug":6,"stem":209,"__hash__":210},"applicationGuide\u002Fapplication-guide\u002Fflowfuse\u002F01-overview.yml",[104,112,126,144,161,185,200],{"type":105,"columns":8,"items":106},"linkCards",[107],{"title":108,"body":109,"link":110},"New to FlowFuse? Start with the Foundations","What FlowFuse is and its core pieces — the grounding for everything in this guide.",{"label":111,"to":20},"Foundations →",{"type":105,"heading":113,"columns":18,"items":114},"Apps — app delivery methods",[115,121],{"title":116,"body":117,"link":118},"Whole app","A complete, versioned project promoted through dev, staging and prod — via snapshots & pipelines.",{"label":119,"to":120},"App delivery methods →","\u002Fapplication-guide\u002Fflowfuse\u002Fapp-delivery-methods\u002F#whole-app",{"title":122,"body":123,"link":124},"Pieces","A reusable piece packaged to the Team Library, installed like a shared library — via subflow export.",{"label":119,"to":125},"\u002Fapplication-guide\u002Fflowfuse\u002Fapp-delivery-methods\u002F#pieces",{"type":105,"heading":37,"columns":27,"items":127},[128,134,139],{"title":129,"body":130,"link":131},"Packaged App","Sealed product on a Remote Instance, identical on every device.",{"label":132,"to":133},"Hardware apps →","\u002Fapplication-guide\u002Fflowfuse\u002Fhardware-apps\u002F#packaged-app",{"title":135,"body":136,"link":137},"Configurable App","Same build on a Remote Instance, tuned by a per-site config file that lives on the device.",{"label":132,"to":138},"\u002Fapplication-guide\u002Fflowfuse\u002Fhardware-apps\u002F#configurable-app",{"title":140,"body":141,"link":142},"Edge Building Block","A reusable edge block you wire into your own upstream flows.",{"label":132,"to":143},"\u002Fapplication-guide\u002Fflowfuse\u002Fhardware-apps\u002F#edge-building-block",{"type":105,"heading":48,"columns":27,"items":145},[146,151,156],{"title":129,"body":147,"link":148},"Headless job on a Hosted or Remote Instance, no screen.",{"label":149,"to":150},"Software apps →","\u002Fapplication-guide\u002Fflowfuse\u002Fsoftware-apps\u002F#packaged-app",{"title":152,"body":153,"link":154},"Data-Driven App","User-facing app on a Hosted Instance, backed by data.",{"label":149,"to":155},"\u002Fapplication-guide\u002Fflowfuse\u002Fsoftware-apps\u002F#data-driven-app",{"title":157,"body":158,"link":159},"Shared Building Block","Reusable UI or logic many Hosted Instances embed.",{"label":149,"to":160},"\u002Fapplication-guide\u002Fflowfuse\u002Fsoftware-apps\u002F#shared-building-block",{"type":105,"heading":162,"columns":38,"items":163},"Architectures — data plane, how data is handled",[164,170,175,180],{"title":165,"body":166,"link":167},"Built in — Tables","Relational records — built into every FlowFuse install, exposed to every instance.",{"label":168,"to":169},"Data plane →","\u002Fapplication-guide\u002Fflowfuse\u002Fdata-plane\u002F#relational",{"title":171,"body":172,"link":173},"Built in — Broker \u002F UNS","Team Broker — built into every FlowFuse install; publish once, many subscribe.",{"label":168,"to":174},"\u002Fapplication-guide\u002Fflowfuse\u002Fdata-plane\u002F#broker-uns",{"title":176,"body":177,"link":178},"Time-series","External today — no built-in TSDB; run Timescale\u002FQuest and expose it to the fleet.",{"label":168,"to":179},"\u002Fapplication-guide\u002Fflowfuse\u002Fdata-plane\u002F#time-series",{"title":181,"body":182,"link":183},"Bring your own","Expose any other store or service (SQL, ML, gateway) over Project Link.",{"label":168,"to":184},"\u002Fapplication-guide\u002Fflowfuse\u002Fdata-plane\u002F#bring-your-own",{"type":105,"heading":186,"columns":27,"items":187},"Architectures — execution plane, where it runs",[188,192,196],{"title":87,"body":189,"link":190},"Near the equipment — edge with the server in IT or an OT\u002FDMZ, hardware-saving consolidation, and air-gapped sites.",{"label":191,"to":90},"View OT →",{"title":81,"body":193,"link":194},"Hosting & governing — on-prem, your cloud per-site, hosting choice at scale, and enterprise governance.",{"label":195,"to":84},"View IT →",{"title":93,"body":197,"link":198},"The live data backbone — a Unified Namespace where edge publishes once and many subscribe, across every site.",{"label":199,"to":96},"View IIoT →",{"type":105,"heading":201,"columns":8,"items":202},"Examples",[203],{"title":76,"body":204,"link":205},"OEE, end to end — the full chain from edge to broker to cloud to history.",{"label":206,"to":100},"Worked example →","yml",{},"application-guide\u002Fflowfuse\u002F01-overview","d-UdYXvJGiO03KSuCFlYTdh0yEFjtOi-HNBsp09NJoQ",1786132520467]