Skip to content

Enterprise

Enterprise here means one thing: an organization runs the same runtime binary as everybody else, and adds a Control Plane on top of it — published policy, fleet visibility, audit history and API keys, scoped to that organization.

The runtime does not require any of this

runtime is a local binary. Install it, bootstrap a Runtime Home, and every command works with no account, no network and no Control Plane. Everything on these pages is optional and additive — see Installation to start without it.

First-time: wire an agent to /api/v1

Goal: get one enterprise agent talking to the org Control Plane — not the open demo surface.

1. Install + bootstrap runtime (local)
2. In app. → API Keys → issue ONE org license key
3. On the agent, set the local portal wire:
     RUNTIME_PORTAL_ENABLED=true
     RUNTIME_PORTAL_BASE_URL=https://api.engineeringruntime.com   # or your company app-api
     RUNTIME_PORTAL_PATH_PREFIX=/api/v1
     RUNTIME_PORTAL_API_KEY=…   # from vault (binary support landing with auth work)
4. runtime portal status && runtime portal sync
5. Confirm the agent on app. → Fleet
Do Don't
Point base_url at api. (or your app-api) Point at app. or demo. UI hosts
Use /api/v1 for real org agents Use /api/public for production enterprise
Keep portal URL + key local (env or portal-only $RUNTIME_CONFIG_FILE) Expect bootstrap or portal sync to install the wire
Share one org key via vault / CI Issue a key per agent

Step-by-step (inputs, commands, failures, what works today): Set up an enterprise agent.

Client reference: Connect the Control Plane.

Pages in this section

  • Set up an enterprise agent

    First-time path: enable the portal, point at /api/v1, org license key, sync, and verify Fleet.

  • Control Plane

    What the Enterprise Control Plane is, how access is issued, and an honest table of what works today versus what is not built yet.

  • Current availability & roadmap

    Dated sequencing — what is next (SSO, organization onboarding, RBAC enforcement) and what is deliberately later.

The three hostnames

Host What it is Who can use it
api.engineeringruntime.com The shared Control Plane API — policies, audit, fleet, catalog, auth, plus published contracts Open surfaces (/api/public, portal, /metadata*) are public; /api/v1 is the enterprise agent surface
demo.engineeringruntime.com Demo UI — Static fixtures or Live Demo against /api/public Anyone, no account
app.engineeringruntime.com The enterprise UI — organization-scoped dashboards over /api/v1 Invitation only, after organization onboarding

Point a runtime at the API origin, never at a UI hostname. Humans use app.; agents use api. + path_prefix=/api/v1.

Community and Enterprise

Community Enterprise
Runtime binary Same binary Same binary
Portal Off (default) On — local RUNTIME_PORTAL_* or portal-only config file
API surface /api/public (optional demo) /api/v1 + org license key
Policy Local / compiled-in defaults Published from Control Plane, pulled with runtime portal sync
Audit Local logs/audit.log (always written first) Local log plus a best-effort uplink to the org's audit history
UI demo. app.
Account None needed Issued after onboarding

Editions comparison and the product narrative live on the main site: Community and Enterprise. This section stays operational — what exists, what it does, and how to connect an agent the first time.