Govern agent state before execution gets messy.
One hosted control plane for agent identity, scoped rules, skills, guidance, releases, and verification across runtimes.
Clear objects, clear desired state, clear verification after release.
Identity, rules, skills, guidance, and releases sit at the center.
Manage the objects that decide who an agent is, what it can use, and how changes move into runtime state.
Enrollment, SSH keys, API keys, and ownership records.
Organization, team, project, workspace, and agent rules with clear inheritance.
Folder-based skill packages with SKILL.md, scripts, references, and assets.
Best practice and judgment that can be shared across scopes without turning into hard policy.
Show what changed, what matched, and what needs attention.
The control plane stays useful when teams can see desired state, actual state, and drift in the same place.
The manifest the control plane intends each agent to hold.
The local state the sync client reports after applying files and config.
A visible mismatch between expected and actual artifacts or settings.
A reversible path when a release needs to be replaced quickly.
Use control plane, control center, governor, manager, and mission control as related terms.
The page intentionally uses product language buyers already understand.
The product story stays consistent across public pages, docs, and the console.
Use the platform page as a hub, then branch into focused long-tail pages.
Move from the platform overview into the pages that explain each part of the object model.