Developers · Govern + Operate

Two products.
Clear authority.

Connect operations to governance without treating discovery as permission.

Govern and Operate have separate identity, permissions and records. Select the product whose interface you need, or review the combined integration boundary.

Keep each product contract explicit

Govern can govern agents you already run. Operate can manage private work and configured HTTP agents independently. The combined evaluation adds reviewed Govern execution bindings to supported Operate work. It does not turn earlier operational history into governed evidence.

Each product owns its authentication, permissions and records. A token for one product or resource is not a token for another. Linking requires authorization from each product's owner; an unavailable Govern service cannot authorize fallback execution.

Shared workspace under implementation

The common workspace is being implemented to present the modules the signed-in person may access. Adding a product will expose its available modules after configuration and authorization. Installation or purchase alone will not grant private project, task or governance access.

The current Govern APIs, SDKs, CLI and MCP remain documented independently. Operate developer interfaces and shared appearance are under implementation. Use the release's supported interface and compatibility matrix supplied in the evaluation package, rather than assuming feature parity.