[{"data":1,"prerenderedAt":244},["ShallowReactive",2],{"application-guide-nav":3,"application-guide-flowfuse-it-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":81,"blocks":103,"blurb":83,"extension":240,"guide":5,"meta":241,"navOrder":82,"slug":80,"stem":242,"__hash__":243},"applicationGuide\u002Fapplication-guide\u002Fflowfuse\u002F08-it-architectures.yml",[104,107,232],{"type":105,"kicker":81,"body":106},"prose","How FlowFuse deploys for IT — hosting the platform and serving the wider organisation. Read each diagram bottom-up: the platform above, the instances and services it serves below.",{"type":108,"panels":109},"tabs",[110,149,179,205],{"label":111,"kicker":112,"diagram":113,"summary":147,"useWhen":148},"On-prem IT","On-prem IT data center · self-managed",{"lanes":114,"legend":140},[115,121,123,132,134],{"label":112,"tone":116,"nodes":117},"it",[118],{"title":119,"sub":120,"tone":116},"FlowFuse platform","on your own servers",{"link":122},"hosts",{"label":124,"tone":125,"nodes":126},"Apps","neutral",[127,130,131],{"title":128,"sub":129},"Hosted Instance","app",{"title":128,"sub":129},{"title":128,"sub":129},{"link":133},"served to",{"label":135,"tone":125,"nodes":136},"IT users",[137],{"title":135,"sub":138,"tone":139},"dashboards & tools","muted",[141,143,145],{"label":142,"tone":116},"IT zone",{"label":144,"tone":125},"Authenticated",{"label":146,"tone":139},"Serves","The whole FlowFuse platform runs on the company's own servers in their IT data center. It hosts the apps as Hosted Instances and serves them to IT users. Nothing leaves the building unless you choose to connect it.","IT wants to own and run the platform entirely in-house, on their own infrastructure.",{"label":150,"kicker":151,"diagram":152,"summary":177,"useWhen":178},"Cloud + per-site","Cloud · your own AWS account",{"lanes":153,"legend":171},[154,159,161],{"label":151,"tone":155,"nodes":156},"cloud",[157],{"title":119,"sub":158,"tone":155},"your cloud account",{"link":160},"Device Agent · per site",{"label":162,"tone":116,"nodes":163},"Sites · IT layer — one Remote Instance each",[164,167,169],{"title":165,"sub":166,"tone":116},"Remote Instance","Site A · IT layer",{"title":165,"sub":168,"tone":116},"Site B · IT layer",{"title":165,"sub":170,"tone":116},"Site C · IT layer",[172,174,175],{"label":173,"tone":155},"Cloud",{"label":142,"tone":116},{"label":176,"tone":125},"Device Agent · deploy\u002Fmanage","The FlowFuse platform runs in the company's own cloud account (e.g. AWS) and deploys and manages a Remote Instance in each site's IT layer via the Device Agent. The cloud platform governs and deploys; each site's instance runs locally and keeps working on its own even if the link drops.","The platform lives in your cloud, but each site needs its own instance in its IT layer.",{"label":180,"kicker":181,"diagram":182,"summary":203,"useWhen":204},"Scaled-out · hosting choice","Platform · host it where you want",{"lanes":183,"legend":200},[184,188,190],{"label":181,"tone":116,"nodes":185},[186],{"title":119,"sub":187,"tone":116},"own infra · your AWS · FlowFuse SaaS",{"link":189},"supports",{"label":191,"tone":125,"nodes":192},"IT services across the org",[193,196,198],{"title":194,"sub":195},"IT service","team A",{"title":194,"sub":197},"team B",{"title":194,"sub":199},"team C",[201,202],{"label":142,"tone":116},{"label":144,"tone":125},"One FlowFuse platform supports IT services across the whole organisation, and you choose where it runs: your own infrastructure, your own AWS, or FlowFuse's SaaS. Same platform, same apps, wherever it is hosted.","Supporting IT broadly and you want freedom to host the platform on-prem, in your cloud, or as SaaS.",{"label":206,"kicker":207,"diagram":208,"summary":230,"useWhen":231},"Enterprise governance","Enterprise · one platform · central governance · one standard",{"lanes":209,"legend":226},[210,214,216],{"label":207,"tone":116,"nodes":211},[212],{"title":119,"sub":213,"tone":116},"role-based access · one standard",{"link":215},"governs · isolates",{"label":217,"tone":125,"nodes":218},"Teams — each a site or business unit, isolated by role-based access",[219,222,224],{"title":220,"sub":221},"Team A","site \u002F business unit · instances & applications",{"title":223,"sub":221},"Team B",{"title":225,"sub":221},"Team C",[227,228],{"label":142,"tone":116},{"label":229,"tone":125},"Governed · RBAC","One FlowFuse platform serves the whole company. Each site or business unit is its own team — its own instances and applications — isolated by role-based access and unified under central governance and one standard.","Central governance and one standard across many sites, with each team's work kept separate.",{"type":233,"columns":8,"items":234},"linkCards",[235],{"title":236,"body":237,"link":238},"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":239,"to":62},"Data plane →","yml",{},"application-guide\u002Fflowfuse\u002F08-it-architectures","1AL7ilK03DbiyWvQohxqkqIizKOchGERX8K852zaQdA",1786134120511]