Find, own and retire every agent and workload.
Keel Registry is the system of record for every AI agent and workload: what exists, who owns it, what it can reach and where it is in its lifecycle. It discovers agents nobody declared and keeps the inventory current.
Why Keel Registry
You cannot govern what you cannot see. Registry is the inventory that Governance enforces against and Intelligence monitors, tied directly to KeelAuth identities, so registration and access are the same act.
- Who it's for
- CISOs and AI platform teams that need control over a growing agent estate, often driven by audit or AI-regulation requirements.
- Build phase
- Phase 2 · Visibility. See the roadmap
- First release scope
- Planned first release: discovery from KeelAuth token logs, two cloud accounts and one SaaS agent platform; MCP server inventory; dependency graph; owner and lifecycle states; inventory export.
What changes with Keel
| Problem | Today | With Keel |
|---|---|---|
| Shadow agents | Teams launch agents in SaaS tools, scripts and frameworks with no central record. | Discovery across clouds, SaaS, code repositories and identity logs. |
| No ownership | Agents outlive the people and projects that created them. | Every agent has a named owner and a review date. |
| Unknown blast radius | No one knows which tools, data and MCP servers an agent can touch. | A dependency graph from agent to tools, sources, secrets and other agents. |
| No lifecycle | Agents are never retired and credentials stay live. | States from proposed to retired, with retirement revoking access. |
| Audit and regulation | Auditors and AI regulations ask for an inventory of AI systems and their risk level. | Exportable inventory with classification and risk tier. |
Shadow agents
Today · Teams launch agents in SaaS tools, scripts and frameworks with no central record.
With Keel · Discovery across clouds, SaaS, code repositories and identity logs.
No ownership
Today · Agents outlive the people and projects that created them.
With Keel · Every agent has a named owner and a review date.
Unknown blast radius
Today · No one knows which tools, data and MCP servers an agent can touch.
With Keel · A dependency graph from agent to tools, sources, secrets and other agents.
No lifecycle
Today · Agents are never retired and credentials stay live.
With Keel · States from proposed to retired, with retirement revoking access.
Audit and regulation
Today · Auditors and AI regulations ask for an inventory of AI systems and their risk level.
With Keel · Exportable inventory with classification and risk tier.
What Keel Registry does
Inventory
- Agent and workload records: purpose, owner, team, model, framework, environment, risk tier, data classes
- Registration through API, SDK, CI/CD and a self-service portal
- Classification by autonomy level (assistive, supervised, autonomous) and data sensitivity
Discovery
- Scans cloud accounts, agent frameworks, SaaS platforms with built-in agents and identity logs
- Flags unregistered agents, unknown MCP servers and orphaned credentials
Mapping
- Dependency graph: agent to tools, MCP servers, context sources, secrets, other agents and models
- Declared versus observed access, with drift highlighted
Lifecycle
- States: proposed, approved, active, suspended, retired
- Owner attestation on a schedule; unattested agents suspended automatically
- Retirement revokes identities and credentials in KeelAuth and KeelKey
How it works with the rest of Keel
Each Keel product feeds the others. The delegation chain and the audit trail only work when the same system issues the identity, makes the decision and records the result.
Built on standards you can evaluate
Nothing proprietary to adopt. These are the specifications the design is based on.
Put your first agent under control.
Join the design partner program: 90 days from federating your identity provider to a governed agent in production planning, with a named Keel engineer.