Govern your team’s AI agents at scale

Platform

One control plane for your agent fleet

Eight modules, one org-scoped console and API.

• Centralized policy

  Author governance rules once. Fleet compiles them into signed policy bundles and distributes them to every enrolled agent in your org.

• Merkle-chained audit

  Administrative actions and every step of an agent update go into a merkle-chained audit record, so a change to history breaks the chain.

• MDM agent rollouts

  Create a rollout with a target ssg version and an agent selector. Each matched agent receives an update task on its next heartbeat.

• SSO & RBAC

  Single sign-on over OIDC or SAML. Role-based access separates org admins from members.

• Natural-language fleet query

  Ask a question in plain English. Fleet turns it into a filter, shows you the generated filter, and returns the matching agents.

• Static and dynamic groups

  A static group holds a list of agents. A dynamic group holds a filter that Fleet re-evaluates each time you read the group.

• Coverage assurance

  Declare the machines that should run an agent. Fleet compares that list with the enrolled agents and reports the dark assets.

• One-click self-enroll

  A developer connects their own machine from the Workspace dashboard. The enrollment grant is single-use and expires in 5 minutes.

How it works

Enroll, govern, audit

Three steps from a new machine to an audited fleet.

1. 01

   Enroll

   Developers connect machines in one click. You can also declare the machines that should run an agent, and Fleet reports which ones are not enrolled.

2. 02

   Govern

   Publish signed policy bundles and create rollouts that move agents to a target ssg version. Agents receive changes on their next heartbeat.

3. 03

   Audit

   Administrative actions and update lifecycle events are merkle-chained. The coverage report lists the dark assets.

Security architecture

Built to fail closed

Enterprise orgs get a dedicated tenant Worker through Workers for Platforms.

• Regional database pools

  An org can be assigned to a database pool in US West or EU West. An org with no pool assigned uses the shared database.

• Ed25519-signed policy bundles

  Fleet signs every policy bundle with Ed25519 before it reaches an agent.

• Fail-closed MCP server

  The MCP server is read-only and org-scoped: every tool takes an org id. It refuses all requests until a bearer token is set.

• Updates on the next heartbeat

  An update reaches an agent on its next heartbeat, within 5 minutes. The agent rejects any target version that is not strict semver.