Skip to content

See the Control Plane Portal

Read the architecture here. See the operator view there.

The pages before this one describe what a Control Plane is and what it deliberately is not.

The portal is that description rendered as a working interface.

Open the portal

Take me to the portal →

Opens portal.engineeringruntime.com in a new tab.

What you will see

Screen What it shows
Dashboard Fleet health, recent operations, policy version in use
Runtime Fleet Which Runtimes are active, and which policy version each one holds
Providers The engineering platforms the organization has wired up
Capabilities The Engineering Capabilities available across the fleet
Policies The published policy version that every Runtime pulls
Audit Every allow, deny, success, and failure, with executor attribution

What it is not

Sample build — fixture data only

The portal is a sample build of the Control Plane UI for a fictional organization.

No Runtime is connected. Nothing you see is stored. It is not a system of record, and it is not a live environment.

It exists so the governance model can be looked at rather than only read about.

Execution never goes through it

Everything on the portal is observation and distribution.

Engineering Runtime      ← executes, evaluates policy locally, writes audit locally

        │  optional, over HTTPS

        ▼

Control Plane Portal     ← publishes policy, collects audit, shows the fleet

A Runtime with no Control Plane is fully governed.

The portal adds shared policy and shared visibility — never a second execution path.

Connecting a Runtime

The Control Plane client ships with the Runtime and is off by default.

runtime portal status    # is the client enabled, and what is it pointed at
runtime portal sync      # pull the published policy and cache it locally

Policy is pulled only when you ask.

Configuration keys, environment variables, and failure behaviour live in the technical documentation.

Design Principle

Policy is distributed centrally. Policy is enforced locally.

A portal you can browse must never become a dependency of an operation you run.

Next