Keel
Platform

Identify, govern and observe every human, service and agent.

Enterprises already govern people. Keel lets them govern agents the same way, across every cloud and platform, without waiting for each vendor to build its own controls.

How it fits together

Five products, one loop.

KeelAuth and KeelKey are the foundation every actor passes through. Governance sits at the center of the loop, using Registry's inventory and Intelligence's risk signals to decide what identities and credentials can do.

One system of record

The delegation chain and the audit trail only work if the same system issues the identity, makes the decision and records the result.

Neutral across platforms

Platform vendors will build agent identity for their own estates. Most enterprises run several clouds, SaaS platforms and agent frameworks, and need one control plane across all of them.

Enforced, not just reported

Policy is checked at token issuance, at credential issuance and on every request for enterprise data, so a change takes effect on the agent's next request.

The agent lifecycle

From registration to retirement.

Keel covers the full life of an agent, not one moment. The loop closes when risk signals from Intelligence raise an agent's tier or trigger suspension, and the kill switch revokes identity, credentials and context access together.

  1. 1Keel Registry

    Register

    A team proposes an agent with owner, purpose, data classes and tools. Discovery also finds agents nobody declared.

  2. 2Keel Governance

    Approve

    Onboarding policy applies by risk tier. High-risk agents need approval; the most sensitive need a quorum.

  3. 3KeelAuth

    Identify

    The agent gets its own identity. Only registered, approved agents can get tokens.

  4. 4KeelKey

    Credential

    Short-lived, scoped credentials for exactly the systems the agent may reach.

  5. 5KeelAuth

    Act on behalf

    When a user invokes the agent, token exchange carries the user, the delegation chain and the purpose.

  6. 6Keel Governance

    Enforce

    Policy is checked at token issuance, at credential issuance and on every request for enterprise context.

  7. 7Keel Intelligence

    Observe

    Every event is recorded with identity and policy context. Behavior is baselined and drift is flagged.

  8. 8Keel Governance

    Respond

    Risk signals raise the agent's tier or suspend it. The kill switch revokes identity, credentials and context access together.

  9. 9Keel Registry

    Retire

    When the owner retires the agent, or an attestation lapses, everything it held is revoked.

Where Keel fits

Built for agents, across every platform.

KeelPlatform suitesNon-human identity toolsDeveloper auth
Humans and agents in one identity modelYesPartialAgents onlyHumans only
Delegation chain kept through every hopYesPartialNoNo
Enforces at runtime, not only detectsYesOwn estateMostly detectLogin time
Works across clouds, SaaS and frameworksYesOwn platformYesYes
Developer-first APIs and SDKsYesLimitedLimitedYes

Keel's assessment of publicly described capabilities by category, as of Q3 2026. This landscape moves quickly; the durable edge is the delegation model and the governance loop, not any single feature.

How we sequence the build

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.