Skip to content
Flow Docs
Flow home Back to the main Flow site

Template Hub

The Template Hub browses downloadable flow templates the same way the Model Hub browses models. A template embeds a complete flow graph, including its nodes, connections, and configuration, that you clone, parameterize, and run.

How it works today

Section titled “How it works today”
  • The catalog is served by the Flow Hub service, a separately deployed registry host, when one is configured in Settings (Flow Hub section). The desktop syncs the template, model, and node registries into a local snapshot. It checks memory first, then the disk cache, then the embedded catalog as the offline floor. Browsing keeps working with no connection and falls back to last-good data.
  • The hub is organized like the Model Hub. It has Browse / Installed / Updates tabs plus My templates, and each entry has an expandable detail view that shows the description, author, category, version history, a read-only flow preview sketch, and governance badges.
  • Add to collection copies the template into your local templates directory. The template then appears in the Load modal alongside your own saved flows. Updates are version-aware and will not overwrite local edits unless you confirm.
  • Node-type guard: if you load a template whose nodes reference an unsupported or not-installed node type, the load is rejected with a clear error. Templates cannot silently degrade.
  • Templates contain flow structure only, never runtime data.

Publishing and approval

Section titled “Publishing and approval”

My templates lists your locally saved flows. Publish sends one to the Hub, where it lands as a pending version. A preflight shows the proposed version (monotonic per template) and the governance report before you commit. Hub admins review pending versions in the Hub’s web UI and approve or reject them. Only approved versions appear in the public catalog. The desktop tracks your publishes and shows each version’s review state.

The same lifecycle covers all three registries. The Node Hub publishes installed node schemes, and model entries are authored in the Hub’s admin UI. This includes the verification toggle that drives the approved-model set that this page’s governance badges check.

Governance badges

Section titled “Governance badges”

Every catalog entry carries a recorded governance report, evaluated with the same rules on the Hub and on the client:

  • Contract-safe means every AI node is contract-bound and has an explicit fail-edge fallback path.
  • Approved models means every referenced model id (including fallbacks) is a verified entry of the Hub’s models registry.

Non-compliant templates can still be published. Reviewers see the issue list, and approving one requires an explicit override.

Templates and source control

Section titled “Templates and source control”

Every saved template writes a sibling .flow DSL file alongside its JSON record, so flows are immediately reviewable in git through pull requests, code owners, and branch promotion. The template is the unit of team-level reuse. You hand a teammate the flow instead of a pile of CLI history.

The version-drift story

Section titled “The version-drift story”

A template can pin the toolkit or artifact versions it was validated against and fetch them fresh per run. That avoids the classic failure mode where a stale local copy produces silently-wrong results weeks later. When the template owner ships an update, every clone picks it up from the hub on its next sync. You make one central update instead of N independent rediscoveries. See the fleet-scan tutorial.

Section titled “Related”