Features

Agent Sdk

Dedicated SDK for agentic workflows — agent sessions, token lifecycle, and authorization requests

Token Delegation

Issue scoped tokens an agent can use downstream without exposing user credentials

Human In The Loop

Pause agent execution and require explicit user approval before proceeding

Fga

Fine-Grained Authorization — relationship-based or attribute-based access control, not just role-based

Mcp Support

Unverified — check source_urls

Async Authorization

Non-blocking approval workflows — agent continues and gets notified when approval is granted

Ory

Ory is the dominant open-source identity stack for teams that need to run their own infrastructure. It's a suite of components: Kratos (identity management), Hydra (OAuth 2.0/OIDC), Keto (FGA via SpiceDB-compatible model), and Oathkeeper (API gateway / access proxy).

For agents in regulated industries or organizations that can't use cloud-hosted identity providers, Ory is the most capable self-hosted option. The FGA via Keto is powerful — it uses Google Zanzibar's relationship-based model, the same foundation as Auth0 FGA and Google's own IAM.

The complexity cost is real. Running Ory in production requires Kubernetes experience and ongoing ops investment. There's no hosted agent SDK, and human-in-the-loop approval flows need to be built on top of the underlying primitives.

Agent-specific features:

OAuth 2.0 token delegation via Hydra
Relationship-based FGA via Keto (Zanzibar model)
API access control via Oathkeeper
Full infrastructure control for compliance-sensitive deployments

Ory

Best for

Limitations

Features

Frameworks

SDK Languages

Compliance

Ory