Two public programmatic surfaces#
LumenFlow exposes two programmatic surfaces today:
- Control-plane SDK v1 for connected runtimes that enroll into the hosted control plane
- Workspace product routes for authenticated exports, billing, and dashboard-managed operations
Authentication#
Connected runtime auth#
Connected runtimes use a workspace API key. You receive the plaintext token when you create a workspace or regenerate the key.
Dashboard auth#
Operator-facing product routes use your authenticated dashboard session. Those routes are for the hosted product surfaces, not for long-running external runtimes.
What the control-plane SDK exposes#
| Surface | What it provides |
|---|---|
| Bootstrap | A ready-to-run connect command plus the generated workspace config block |
| Desired state | Canonical config and policy fetch paths |
| Observed state | Sessions, heartbeat, events, evidence, and telemetry sync paths |
| Governance headers | Contract version, runtime model, authority mode, and reconciliation posture |
What connected runtimes report back#
Connected runtimes can sync:
- liveness and heartbeat state
- active sessions
- governed events and action outcomes
- evidence and proof artifacts
- runtime telemetry
Rate limits and availability#
Traffic limits vary by plan and workspace. Free is intended for evaluation, Team supports sustained operator traffic, and Enterprise is the path for higher-volume governed runtimes or custom throughput needs.
Next step#
If you want to connect your own runtime, start with Governed Runtimes Overview and then follow the Control-Plane SDK Quickstart.