Overview

Whole app

A complete, versioned project promoted through dev, staging and prod — via snapshots & pipelines.

App delivery methods →

Pieces

A reusable piece packaged to the Team Library, installed like a shared library — via subflow export.

App delivery methods →

Packaged App

Sealed product on a Remote Instance, identical on every device.

Hardware apps →

Configurable App

Same build on a Remote Instance, tuned by a per-site config file that lives on the device.

Hardware apps →

Edge Building Block

A reusable edge block you wire into your own upstream flows.

Hardware apps →

Packaged App

Headless job on a Hosted or Remote Instance, no screen.

Software apps →

Data-Driven App

User-facing app on a Hosted Instance, backed by data.

Software apps →

Shared Building Block

Reusable UI or logic many Hosted Instances embed.

Software apps →

Built in — Tables

Relational records — built into every FlowFuse install, exposed to every instance.

Data plane →

Built in — Broker / UNS

Team Broker — built into every FlowFuse install; publish once, many subscribe.

Data plane →

Time-series

External today — no built-in TSDB; run Timescale/Quest and expose it to the fleet.

Data plane →

Bring your own

Expose any other store or service (SQL, ML, gateway) over Project Link.

Data plane →

OT architectures

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

View OT →

IT architectures

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

View IT →

IIoT architectures

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

View IIoT →