Enterprise Platform

Engineering Runtime works first as a local Community product. Enterprise adds an optional Control Plane for fleet presence and centrally published policy and configuration. It does not create a second execution path: commands and capabilities still execute, evaluate policy, and record audit evidence locally.

Community and Enterprise

	Community/local	Enterprise-managed Runtime
Account or Control Plane	Not required	Company Control Plane required for registration/sync/heartbeat
Policy and configuration	Operator-selected local files	Last verified signed Control Plane generation
Authority transition	—	Explicit authenticated runtime portal register, sticky for that Runtime Home
Audit	Local journal, audit commands, and configured stdout	Same local behavior; external audit export is a separate OpenTelemetry integration
Network	Only the engineering platform being operated	Adds authenticated registration, manual sync, and heartbeat

The public demo is static sample data. The public API site is a read-only contract reference and cannot execute requests. The real Enterprise app is a separate authenticated surface.

Start with Set up an Enterprise Runtime, then read Control Plane and Control Plane configuration.

Operational examples on this site were verified against Runtime 0.9.8. After bootstrap, the version-exact files in Runtime Home win.