Bring your own compute (BYOC)

Run governed work on your own machines. LumenFlow's cloud issues a scoped authorization envelope — permissions, budget, a kill switch, and a confinement posture — to a local runner, then ingests per-action evidence and cost back. Your compute, LumenFlow's governance.

Your compute, governed#

Bring-your-own-compute (BYOC) lets governed work run on infrastructure you own — a developer machine, your own servers — while LumenFlow's control plane still sets the rules and keeps the record.

How it works#

  1. The cloud issues a governed authorization envelope for the run: which capabilities are allowed, the budget, a kill switch, and how the work is confined.
  2. A local runner executes inside that envelope.
  3. Each tool call streams evidence and cost back to the cloud, so the work is as auditable as anything run in the hosted runtime.

Why use it#

  • Keep data and execution on your own hardware for residency or security reasons.
  • Use spare or specialised local compute while keeping central governance.
  • Prove what ran locally with the same evidence chain as everything else.

See Connected Compute and Connected-Runtime Enrollment to connect a runner.