FlowFuse Guide

Architectures

The same building blocks, arranged for where they run.

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.

OT architectures

Near the equipment — edge deployments with the server in IT or in an OT/DMZ, hardware-saving consolidation, and air-gapped sites.

View OT →

IT architectures

Hosting and governing — on-prem, your cloud per-site, hosting choice at scale, enterprise governance, and secure data exposure.

View IT →

IIoT architectures

The live data backbone — a Unified Namespace where edge publishes once and many subscribe, across every site.

View IIoT →

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.

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.

Dev · one build

Dev instance

develop once

pipeline push

Versioned source of truth

GitHub

versioned source of truth

pull

Sites · prod instances (OT & IT)

Instance

Site A · OT

Instance

Site B · IT

Instance

Site C · OT

push / pull

Once code is on a server, it ships via snapshots or subflows.

App delivery methods →