Keel
The Keel Platform

Identity infrastructure
for the agentic era.

One platform to identify, govern and observe every human, service and AI agent. Give each a real identity, control what it can do and know, and see what it actually did.

Become a design partnerExplore the platform

Built on open standards: OAuth, OpenID Connect, MCP authorization, token exchange and shared signals.

The shift

Your applications have more than users now.

Identity systems were built for people logging in. Agents now act on people's behalf, at machine speed, across every system they can reach.

80:1

machine identities for every human identity in the enterprise

Palo Alto Networks, Feb 2026
40%

of enterprise apps will include task-specific AI agents by end of 2026, up from under 5% in 2025

Gartner
67%

of employees using AI on corporate devices do it through personal, unmanaged accounts

Verizon 2026 DBIR
The problem

Agents run on borrowed, invisible access.

Four failure modes every security team recognizes. Each one is an identity problem, which is why identity is the right place to solve it.

01

Shared keys

Agents call systems with static API keys or service accounts that can see far more than the person who asked.

02

Lost delegation

User to agent to agent: by the second hop, no system knows which person the agent is acting for, or why.

03

No runtime control

Policies live in documents. Nothing stops an agent mid-task, caps what it can do or revokes it everywhere at once.

04

No record

After an incident, nobody can reconstruct what the agent saw, what it did or which rule allowed it.

One platform

One identity layer for humans and agents.

Every actor authenticates through KeelAuth and gets credentials from KeelKey. Registry knows which agents exist. Governance decides what each may do. Intelligence watches what each actually does, and the observations change the governance. It is a loop.

Every actorHumans · Services · AI agents
Foundation · who an actor is and what it holds
KeelAuthIdentity, authorization and delegated accessKeelKeySecrets, keys, certificates and signing
The loop · see, decide, observe
Keel RegistryEvery agent, its owner and its lifecycleKeel GovernancePolicy, approvals and the kill switchKeel IntelligenceBehavior, anomalies and the audit ledger
Context GatewayGovernance enforced on every agent request for enterprise data: who, for whom, and why
Your enterprise data and toolsSearch · Warehouses · SaaS apps · MCP servers
See how the platform fits together
Five products

Start with one. Expand to all five.

Most customers start with KeelAuth or Registry and expand. Each product works on its own and gets stronger with the others.

Identity

KeelAuth

Authentication and authorization for humans, services and AI agents.

  • Login, SSO, SCIM, passkeys
  • Agent identities
  • Delegation chains
  • MCP authorization
Explore KeelAuth
Keys and secrets

KeelKey

Secrets, keys, certificates and signing, governed across the vaults you already run.

  • Governs cloud vaults
  • Short-lived agent credentials
  • Quorum approvals
  • Keys, certs, signing
Explore KeelKey
Inventory

Keel Registry

Find, own and retire every agent and workload.

  • Every agent and owner
  • Shadow agent discovery
  • Tool and data map
  • Lifecycle and retirement
Explore Keel Registry
Control

Keel Governance

Decide what agents may do, and enforce it at runtime.

  • Policy as code
  • Approvals and limits
  • Kill switch
  • Context Gateway add-on
Explore Keel Governance
Visibility

Keel Intelligence

See what every agent actually did, and catch what looks wrong.

  • Per-agent timelines
  • Behavior baselines
  • Anomaly and risk scoring
  • Audit ledger
Explore Keel Intelligence
Governance add-on

Context Gateway

Govern what your agents can know, on every request.

  • Identity, delegation and purpose per request
  • Redaction and data-flow control
  • One audit record per packet
Explore Context Gateway
See it work

Delegation, kept through every hop.

When a person asks an agent to act, and that agent calls another, Keel keeps the person and the purpose attached. This is how.

Delegated token · decodedIllustrative
{
  "sub": "user:nurse.reviewer",
  "act": {
    "sub": "agent:formulary-lookup",
    "act": { "sub": "agent:claims-assistant" }
  },
  "authorization_details": [{
    "type": "context_access",
    "purpose": "prior-auth-review",
    "sources": ["formulary", "chart-notes"]
  }],
  "exp": "now + 5 minutes"
}

sub is the person. act records each agent acting on their behalf, using the standard OAuth token-exchange format.

The token names the person, every agent in the chain, the purpose and the scope. It uses the standard OAuth token-exchange format, so nothing proprietary has to be adopted.

Governance policy is checked when the token is issued, when credentials are issued and, through the Context Gateway, on every request for enterprise data.

Context Gateway All five examples
Example 4Any enterpriseIllustrative scenario

Finding and stopping a shadow agent

Situation. Someone on a data team spins up an autonomous agent in a notebook, gives it a personal API key and points it at member data.

  1. 1 · Found
    Keel Registry

    Discovery spots an autonomous agent calling internal systems with a personal key and no owner in the Registry.

  2. 2 · Flagged
    Keel Intelligence

    It read 18,000 records in nine minutes and tried an external webhook.

  3. 3 · Stopped
    Keel Governance

    Security pulls the kill switch, approved by a 2-of-3 quorum. Tokens, credentials and context access are revoked everywhere.

Outcome. Today, stopping a rogue agent means hunting down every key it touched. With Keel it is one action. Full revocation in under 60 seconds is our design target.

All examples →
Land with identity, expand to control

Two ways in. One platform.

Developers adopt KeelAuth to ship enterprise-ready login. Security teams add the Registry, Governance and KeelKey to control the agents behind it.

01

Keel Developer

Enterprise-ready auth for your app.

Developers and B2B and B2C SaaS teams
02

Keel Agent Identity

Real identities and an inventory for your agents.

AI platform teams
03

Keel Agent Control

Enforce what agents can do and know.

CISOs
04

Keel Enterprise

Govern a regulated agent estate end to end.

CISOs, risk and compliance
See the packages →
Open by design

Fits the stack you already run.

Keel federates with the identity provider you use for employees, governs the cloud vaults you already have, and sits in front of the MCP servers, search and data platforms your agents use. Standards are the design basis; confirm specific connectors with the team.

OAuth 2.1OpenID ConnectSAML 2.0SCIM 2.0Passkeys (WebAuthn)Token Exchange (RFC 8693)Rich Authorization Requests (RFC 9396)MCP authorizationShared Signals / CAEPSPIFFEOpenTelemetryOCSF

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.

Become a design partnerTalk to the team