Enterprise Control Plane¶
The Enterprise Control Plane is the optional management layer around a fleet of Engineering Runtime installations. It consists of an authenticated app-ui and an independently authenticated app-api: the hosted UI is protected by its own access gate, and the backend still verifies every operational request itself.
It does not execute engineering operations. Runtime remains the execution boundary.
api.engineeringruntime.com is only a static, read-only OpenAPI reference. It
has no live backend, authorization action or Try/Execute feature. The app-api
deployment URL is deployment configuration and is not published here.
Current availability¶
| Capability | Status |
|---|---|
| Administrator login | Available — produces a one-hour app session |
| Policy and configuration publishing | Available — platform administrators publish independent immutable versions; each publish creates a signed, atomic combined generation |
| Runtime Portal keys | Available — create a show-once key for each Runtime, inspect its binding and state, replace it, or revoke it |
| Fleet | Available — registered Runtime installations appear through authenticated heartbeat |
| Providers view | Available — from the selected released Runtime specification |
| Capabilities view | Available — from the deployment's pinned company registry |
| Audit view | Sample data only — clearly labeled sanitized examples. No Runtime audit events are uploaded to app-api |
| SSO / OIDC, organization RBAC | Not available |
| Signing-key rotation, staged/cohort rollout | Not available |
| Durable SaaS audit storage/search, OpenTelemetry audit export | Not available |
See Enterprise availability and roadmap for sequencing.
Execution remains local¶
A managed Runtime still evaluates policy and executes operations where Runtime is installed.
Control Plane
|
| signed policy/config generations
v
Runtime
|
| local/platform auth + context
v
Engineering systems
The Control Plane is not a second execution path and is not a credential vault for the platforms underneath Runtime. GitHub credentials remain GitHub credentials, Kubernetes identity remains Kubernetes identity, and cloud credentials remain owned by their native mechanisms.
Trust boundary¶
- Runtime Portal keys are stored by app-api as verifiers, not plaintext. A key authenticates only registration, heartbeat and governance sync for one Runtime. It never delivers or reads audit data.
- The policy/config signing private key is a separate deployment secret. Runtime pins the matching public key during registration and verifies every generation (signature, organization, schema versions, digests and monotonic version) before applying it.
- Local audit records stay on the Runtime host;
engrt auditremains authoritative.
Registration and sync details are on Connect the Control Plane.
When the Control Plane is unavailable¶
- Normal command execution does not depend on the Control Plane. Heartbeat is attempted after the local audit record is durable, and a heartbeat failure does not change the command outcome.
- A failed
engrt portal synckeeps the last verified generation in force. Generations do not expire in the current contract. - Invalid or corrupted managed state fails closed — Runtime stops rather than falling back to local policy.
- Registration and sync are explicit commands, and their failures are reported.
Demo deployment limitations¶
The hosted low-cost demo uses ephemeral storage and a single app-api instance. A container replacement loses portal users, Runtime registrations, key verifiers and published records. Affected Runtimes must re-register; see Enterprise setup for demo-reset recovery. This is disclosed demo behavior, not durable Enterprise storage. Customer production deployments require an agreed durable store.
Operational examples on this site were verified against Runtime 0.14.0. After bootstrap, the version-exact files in Runtime Home win.