Skip to main content
FlowFuse Application Guide
FlowFuse Application GuideFlowFuse Application Guide
Two guides for the decisions you make before you start building: which FlowFuse pieces an app is made of, where they run, and what a flow should look like once it is. This is the material we walk through during a proof of concept, written down so you can work through it yourself.
FlowFuse Guide
Turn an app idea into FlowFuse pieces you can name and say in one sentence.
- OverviewTurn an app idea into FlowFuse pieces you can name and say in one sentence.
- FoundationsThe foundation to build on: what FlowFuse is, its core pieces, and how code is shared across teams.
- App delivery methodsTwo different units of code, delivered two ways: ship the whole app, or publish one reusable piece.
- Hardware appsThe three shapes a FlowFuse app takes when it runs on a device.
- Software appsThe three shapes a FlowFuse app takes when it runs on the platform.
- Data planeBefore you pick where things run, decide how data is handled.
- ArchitecturesThe same building blocks, arranged for where they run.
- IT architecturesHosting the platform and serving the wider organisation.
- OT architecturesHow FlowFuse deploys in operational-technology environments, near the equipment.
- IIoT architecturesDistributed edge nodes, each doing one small job, feeding one central system.
- Worked exampleOEE, end to end — two packages, two connections.
Node-RED Guide
Turn an architecture sentence into a clean flow shape you can read at a glance.
- OverviewTurn an architecture sentence into a clean flow shape you can read at a glance.
- FoundationsThe handful of concepts you need to build with Node-RED, and how they fit together.
- Flow shapeTurn an architecture sentence into a flow you can read at a glance.
- Design patternsThe moves that turn a flow into something you can reuse, test and hand off.
- Handling dataSort data by what it is for before you tune anything.
- Operating flowsFour operational habits that keep a flow running when the real world pushes back.
- Worked exampleThe shape rules and patterns applied end to end.