App delivery methods

Snapshots & pipelines — promote a complete, versioned project through dev → staging → prod to every place that runs it.

Take the whole app — every flow, setting and dependency — as a versioned snapshot, then promote that one controlled build through pipeline stages to every place that should run it.

Use it when — You're shipping a complete application and every site should run the same, controlled version.

How it works — A pipeline promotes a snapshot dev → staging → production; each target is parameterised by its own env vars, so one controlled build serves every site.

Major components

• Snapshot — the whole app, frozen as one versioned build
• Pipeline — promotes that snapshot through dev → staging → prod
• Dev instance — where you build and test the project
• Remote / Hosted Instances — the fleet each snapshot rolls out to

Where config & data live depends on the kind of app you're shipping — a hardware app tied to a device, or a software app on the platform. See Hardware apps → and Software apps →.

More phases when you need them — a pipeline isn't limited to two stages. Add the phases your process needs — an extra staging tier, an approval gate, per-region rollouts — each one a controlled promotion of the same golden build:

Subflow export — publish one piece as a package the team installs, like a shared library.

Package a single piece of a flow — a block of logic or UI — as a reusable subflow, export it as a custom node other apps install, and pull it in instead of copying code between projects.

Use it when — A part of an app should be reused across many apps and upgraded in one place — a shared library, not a whole application.

How it works — Export the subflow as a custom node — an installable package apps pull in like any library dependency. Apps install it and the Bill of Materials tracks every version in use. Share an example flow in the Team Library to show how to wire it up.

Major components

• Subflow — the one reusable piece you package
• Custom node — the installable package your subflow is exported to
• Team Library — example flows the team shares (a custom node can ship with one to show its use)
• Instances — the apps that install and run the piece
• Bill of Materials — tracks which version each app runs

Where config & data live

• Config — the subflow's instance properties / env where it's installed.
• Distribution — export once as a custom node; apps install and upgrade from it, like a library.