Skip to content

Community and Enterprise

The same Runtime everywhere. The Control Plane is what a company adds.

Engineering Runtime is one binary with one execution model.

Adding a Control Plane does not fork it, replace it, or give it a second execution path.

It adds shared policy and shared visibility on top of the Runtime that was already governing every operation locally.

In one line

Promise
Community The full Runtime on your machine — local policy, local audit, no Control Plane required
Team / Enterprise The same Runtime, plus a Control Plane so the organization shares one policy and sees every operation

Adoption is progressive.

Start locally.

Add the Control Plane when governance has to span more than one machine.

Usage model

Community — local governance

Laptop / CI agent

  Runtime Home

    ├── config.yaml            ← configuration, edited locally
    ├── policy-config.yaml     ← policy, edited locally
    └── logs/audit.log         ← audit, stays on the machine

Everything the Runtime needs is on disk.

Policy is evaluated before every operation.

Every operation is audited.

Nothing calls out to a Control Plane, because nothing needs to.

This is the complete Runtime — not a trial edition of it.

Team and Enterprise — shared governance

Control Plane

  publish policy version

        │  sync

        ▼

Each Runtime

  cached policy            ← evaluated locally, offline-safe

        │  uplink

        ▼

Central audit + fleet view

Rules are changed once.

Humans, pipelines, and AI agents all follow the same version after refresh.

The Runtime still evaluates locally, and still writes its audit locally first.

What each edition covers

Capability Community Team Enterprise
Runtime CLI Yes Yes Yes
Providers and Engineering Capabilities Yes Yes Yes
Policy before every operation Yes — local file Yes — published centrally, cached locally Yes
Audit for every operation Yes — local log Local plus central Local plus central, with retention and search
Control Plane required No Yes, for central governance Yes, for central governance
One shared policy across all Runtimes No — per machine Yes Yes
Policy versions, publish, rollback Manual file edit Central publish Central publish with approval workflows
Fleet, Providers, Capabilities, Audit views — Yes Yes
Human, CI/CD, and AI attribution in audit Local fields Visible centrally Central, with AI governance reporting
Organizations and multi-tenancy No Basic Yes
SSO and RBAC No Direction Yes
Compliance reporting No Light Yes
Durable storage and audit at scale No Yes Yes

Team sits between the two.

It is shared policy and central audit without every enterprise compliance feature on the first day.

Where to start

If you are Start with
An individual engineer or open-source user Community — install the Runtime, keep policy on disk
A platform or developer-experience team standardizing engineering operations Team — Control Plane with shared policy and central audit
A regulated or multi-team organization needing SSO, organizations, and audit retention Enterprise

Moving between them is a configuration change.

It is not a migration, and it is not a different product.

What is available today

Available now:

  • The Runtime, with local policy and local audit
  • Providers, Engineering Capabilities, and the same execution path for humans, CI/CD, and AI
  • The Control Plane client in the Runtime — runtime portal status and runtime portal sync

Not yet publicly available:

  • The Control Plane server itself
  • SSO, RBAC, and organizations
  • Automatic fleet-wide policy refresh — policy is pulled explicitly today
  • Compliance reporting and audit search at scale

The distinction is deliberate.

Everything a Runtime needs to be governed already ships.

Everything a company adds on top is additive.

Technical details

You want Go to
Control Plane configuration and commands Control Plane (Portal)
Policy file structure and evaluation Policy
Runtime Home layout Runtime Home
Running the Runtime in CI/CD CI/CD
Running the Runtime behind an AI agent AI Agent
Full technical documentation docs.engineeringruntime.com

Design Principle

Configuration belongs to the enterprise. Capabilities belong to the Runtime.

An edition changes what an organization shares.

It never changes how an operation executes.

Next