Federation: governed agents on your own network

Run LumenFlow's governed agents inside your own private network, connected back to the cloud control plane. Federation keeps execution and data on your side of the boundary while policy, approvals, and evidence stay centrally governed.

Governance across a boundary#

Some teams cannot send work to a hosted runtime — the agents need to run inside a private network, next to internal systems and data. Federation is the architecture for that: the agents run on your side; the LumenFlow control plane still governs them.

What stays where#

  • On your network: the agent execution and the systems it touches.
  • In the control plane: policy, approvals, identity, and the evidence record.

The two connect over a governed link, so you get private-network execution without losing central oversight or the audit trail.

When to use it vs the hosted runtime#

  • Use the hosted runtime when work can run in LumenFlow's cloud — it is the simplest path.
  • Use federation when execution must stay inside your network for data-residency, security, or connectivity reasons.

See Connected-Runtime Enrollment and the Connected Runtime Reference Bridge for setup.