[{"data":1,"prerenderedAt":215},["ShallowReactive",2],{"application-guide-nav":3,"agmd-flowfuse-architectures":118},[4,12,16,22,25,31,36,42,47,53,58,64,70,75,81,87,93,98,103,108,112],{"guide":5,"slug":6,"title":7,"navOrder":8,"parent":9,"blurb":10,"path":11},"flowfuse","overview","Overview",1,null,"The map of the FlowFuse guide — apps, architectures, and a worked example.","\u002Fapplication-guide\u002Fflowfuse\u002Foverview\u002F",{"guide":13,"slug":6,"title":7,"navOrder":8,"parent":9,"blurb":14,"path":15},"node-red","The map of the Node-RED guide — the pattern families that turn an app into a clean flow.","\u002Fapplication-guide\u002Fnode-red\u002Foverview\u002F",{"guide":5,"slug":17,"title":18,"navOrder":19,"parent":9,"blurb":20,"path":21},"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":13,"slug":17,"title":18,"navOrder":19,"parent":9,"blurb":23,"path":24},"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":26,"title":27,"navOrder":28,"parent":9,"blurb":29,"path":30},"app-delivery-methods","App delivery methods",3,"Two different units of code, delivered two ways. Ship the whole app — a complete, versioned project promoted through environments — or publish one reusable piece — a package the whole team installs and upgrades in one place. Pick by what you're shipping: the app, or a part of it.","\u002Fapplication-guide\u002Fflowfuse\u002Fapp-delivery-methods\u002F",{"guide":13,"slug":32,"title":33,"navOrder":28,"parent":9,"blurb":34,"path":35},"patterns","Patterns","The moves that turn an architecture into a clean, reusable flow — find the seams and reuse well, then handle data on the right paths.","\u002Fapplication-guide\u002Fnode-red\u002Fpatterns\u002F",{"guide":5,"slug":37,"title":38,"navOrder":39,"parent":26,"blurb":40,"path":41},"hardware-apps","Hardware apps",3.1,"The three shapes a FlowFuse app takes when it runs on a device. Pick by how much varies per site: nothing (Packaged App), a few settings (Configurable App), or you assemble it yourself (Edge Building Block).","\u002Fapplication-guide\u002Fflowfuse\u002Fhardware-apps\u002F",{"guide":13,"slug":43,"title":44,"navOrder":39,"parent":32,"blurb":45,"path":46},"design-patterns","Design patterns","The structural choices you select for a flow: find the seams it breaks into, then reuse each piece at the lightest level that solves it — link in\u002Fout, link call, subflow, or packaged node.","\u002Fapplication-guide\u002Fnode-red\u002Fdesign-patterns\u002F",{"guide":5,"slug":48,"title":49,"navOrder":50,"parent":26,"blurb":51,"path":52},"software-apps","Software apps",3.2,"The three shapes a FlowFuse app takes when it runs on the platform. Pick by what it needs: a headless job (Packaged App), a user-facing app driven by data (Data-Driven App), or a reusable piece other apps embed (Shared Building Block).","\u002Fapplication-guide\u002Fflowfuse\u002Fsoftware-apps\u002F",{"guide":13,"slug":54,"title":55,"navOrder":50,"parent":32,"blurb":56,"path":57},"handling-data","Handling data","Classify each signal by shape, purpose and direction, then pick the methods it needs — separate the paths, pace the flow, hold state in context, and manage config. The methods you select to move a flow's data.","\u002Fapplication-guide\u002Fnode-red\u002Fhandling-data\u002F",{"guide":13,"slug":59,"title":60,"navOrder":61,"parent":32,"blurb":62,"path":63},"good-form","Good form",3.3,"A clean flow isn't luck — it's a handful of habits. Wire for reading, lay it out on a grid, decouple UI from logic, catch errors where you can see them, and keep data on a stable contract. Follow these and a flow stays readable, reusable, and out of spaghetti.","\u002Fapplication-guide\u002Fnode-red\u002Fgood-form\u002F",{"guide":5,"slug":65,"title":66,"navOrder":67,"parent":9,"blurb":68,"path":69},"data-plane","Data plane",4,"Before you pick where things run, decide how data is handled. Two stores come built into every FlowFuse server install — the Team Broker and relational Tables — exposed to every instance with nothing extra to stand up. Everything else you bring your own: run it (a time-series DB, an existing database, a model) and expose it to the fleet over Project Link, no inbound ports. This is the data plane the architectures on the next pages all sit on.","\u002Fapplication-guide\u002Fflowfuse\u002Fdata-plane\u002F",{"guide":13,"slug":71,"title":72,"navOrder":67,"parent":9,"blurb":73,"path":74},"worked-examples","Worked examples","Turn an app concept into a Node-RED flow — or a few — leaning on the design patterns and data handling. The method, then the OEE apps end to end.","\u002Fapplication-guide\u002Fnode-red\u002Fworked-examples\u002F",{"guide":13,"slug":76,"title":77,"navOrder":78,"parent":71,"blurb":79,"path":80},"oee-edge-aggregator","OEE - Edge Aggregator",4.1,"The edge app from the OEE use case as a Node-RED flow — a straight-line flow packaged as a subflow and configured per line (its PLC tags, via a config UI and a get-config node), with the data treated as a stream and its counts held in context.","\u002Fapplication-guide\u002Fnode-red\u002Foee-edge-aggregator\u002F",{"guide":13,"slug":82,"title":83,"navOrder":84,"parent":71,"blurb":85,"path":86},"oee-central-dashboard","OEE - Central Dashboard",4.2,"The cloud app from the OEE use case as a Node-RED flow — one link out fanning to two link ins on separate tabs (dashboard and batched history), so the live and history paths stay separate and easy to read.","\u002Fapplication-guide\u002Fnode-red\u002Foee-central-dashboard\u002F",{"guide":5,"slug":88,"title":89,"navOrder":90,"parent":9,"blurb":91,"path":92},"architectures","Architectures",5,"Every FlowFuse deployment is the same building blocks arranged for where it runs — pick the world you're designing for.","\u002Fapplication-guide\u002Fflowfuse\u002Farchitectures\u002F",{"guide":5,"slug":94,"title":95,"navOrder":96,"parent":88,"blurb":9,"path":97},"it-architectures","IT architectures",5.1,"\u002Fapplication-guide\u002Fflowfuse\u002Fit-architectures\u002F",{"guide":5,"slug":99,"title":100,"navOrder":101,"parent":88,"blurb":9,"path":102},"ot-architectures","OT architectures",5.2,"\u002Fapplication-guide\u002Fflowfuse\u002Fot-architectures\u002F",{"guide":5,"slug":104,"title":105,"navOrder":106,"parent":88,"blurb":9,"path":107},"iiot-architectures","IIoT architectures",5.3,"\u002Fapplication-guide\u002Fflowfuse\u002Fiiot-architectures\u002F",{"guide":5,"slug":71,"title":72,"navOrder":109,"parent":9,"blurb":110,"path":111},6,"Start from a use case, break it into apps, and draw the architecture that ties them together — the same method a FlowFuse Proof of Value runs.","\u002Fapplication-guide\u002Fflowfuse\u002Fworked-examples\u002F",{"guide":5,"slug":113,"title":114,"navOrder":115,"parent":71,"blurb":116,"path":117},"worked-example","OEE, end to end",6.1,"One use case — OEE across three lines — broken into two apps and two shared services, then drawn out end to end.","\u002Fapplication-guide\u002Fflowfuse\u002Fworked-example\u002F",{"id":119,"title":89,"blurb":91,"body":120,"description":129,"extension":208,"guide":5,"meta":209,"navOrder":90,"navTitle":89,"navigation":210,"parent":9,"path":211,"seo":212,"slug":88,"stem":213,"__hash__":214},"applicationGuideDoc\u002Fapplication-guide\u002Fflowfuse\u002Farchitectures.md",{"type":121,"value":122,"toc":202},"minimark",[123,126,130,144,154,164,169,172,177,182,185,192],[124,125,89],"h1",{"id":88},[127,128,129],"p",{},"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.",[131,132,134],"callout",{"icon":133},"i-lucide-arrow-right",[127,135,136,143],{},[137,138,139],"strong",{},[140,141,142],"a",{"href":102},"OT architectures →"," — Near the equipment — edge deployments with the server in IT or in an OT\u002FDMZ, hardware-saving consolidation, and air-gapped sites.",[131,145,146],{"icon":133},[127,147,148,153],{},[137,149,150],{},[140,151,152],{"href":97},"IT architectures →"," — Hosting and governing — on-prem, your cloud per-site, hosting choice at scale, enterprise governance, and secure data exposure.",[131,155,156],{"icon":133},[127,157,158,163],{},[137,159,160],{},[140,161,162],{"href":107},"IIoT architectures →"," — The live data backbone — a Unified Namespace where edge publishes once and many subscribe, across every site.",[165,166,168],"h2",{"id":167},"separating-dev-from-prod","Separating dev from prod",[127,170,171],{},"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 behind a tighter network boundary — a GitHub bridge carries the same versioned code across the boundary. (A truly air-gapped site can't pull from GitHub; there, code crosses by offline snapshot import instead.)",[173,174,176],"h3",{"id":175},"github-bridge","GitHub bridge",[127,178,179],{},[137,180,181],{},"Modifier · works across OT, IT & IIoT.",[127,183,184],{},"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.",[186,187],"arch-diagram",{":edges":188,":groups":189,":legend":190,":nodes":191},"[{\"from\":\"dev\",\"to\":\"github\",\"label\":\"pipeline push\",\"dashed\":true,\"accent\":\"red\"},{\"from\":\"github\",\"to\":\"siteA\",\"label\":\"pull\",\"dashed\":true,\"accent\":\"red\"},{\"from\":\"github\",\"to\":\"siteB\",\"dashed\":true,\"accent\":\"red\"},{\"from\":\"github\",\"to\":\"siteC\",\"dashed\":true,\"accent\":\"red\"}]","[{\"label\":\"Dev · one build\",\"nodes\":[\"dev\"]},{\"label\":\"Sites · prod instances (OT & IT)\",\"nodes\":[\"siteA\",\"siteB\",\"siteC\"]}]","[{\"line\":\"red\",\"dashed\":true,\"label\":\"push \u002F pull\"}]","[{\"id\":\"dev\",\"label\":\"Dev instance\",\"sub\":\"develop once\",\"accent\":\"indigo\",\"col\":2,\"row\":1},{\"id\":\"github\",\"label\":\"GitHub\",\"sub\":\"versioned source of truth\",\"accent\":\"slate\",\"col\":2,\"row\":2},{\"id\":\"siteA\",\"label\":\"Instance\",\"sub\":\"Site A · OT\",\"accent\":\"indigo\",\"col\":1,\"row\":3},{\"id\":\"siteB\",\"label\":\"Instance\",\"sub\":\"Site B · IT\",\"accent\":\"indigo\",\"col\":2,\"row\":3},{\"id\":\"siteC\",\"label\":\"Instance\",\"sub\":\"Site C · OT\",\"accent\":\"indigo\",\"col\":3,\"row\":3}]",[131,193,194],{"icon":133},[127,195,196,201],{},[137,197,198],{},[140,199,200],{"href":30},"App delivery methods →"," — Once code is on a server, it ships via snapshots or subflows.",{"title":203,"searchDepth":67,"depth":67,"links":204},"",[205],{"id":167,"depth":19,"text":168,"children":206},[207],{"id":175,"depth":28,"text":176},"md",{},true,"\u002Fapplication-guide\u002Fflowfuse\u002Farchitectures",{"title":89,"description":129},"application-guide\u002Fflowfuse\u002Farchitectures","YyHre383bjqS2XFkX3g1oJSzpUZlwxdrv5HW2wMIawg",1787068105385]