ory/hydra

Internet-scale OpenID Certified™ OpenID Connect and OAuth2.1 provider that integrates with your user management through headless APIs. Solve OIDC/OAuth2...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 60 minutes ago
Added to GitGenius on September 3rd, 2026
Created on May 22nd, 2015
Open Issues & Pull Requests: 96 (+0)
GitHub issues: Enabled
Number of forks: 1,608
Total Stargazers: 17,523 (+0)
Total Subscribers: 241 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Ory Hydra is an OpenID Certified OAuth 2.0 and OpenID Connect provider optimized for low-latency, high-throughput operation and minimal resource consumption.

Hydra addresses the need for a standalone authorization server that handles OAuth 2.0 and OpenID Connect flows without bundling user management. It connects to your existing identity provider through headless login and consent APIs, letting you retain complete control over authentication UI and user experience. The server manages token issuance and validation, client registration, consent orchestration, and JWKS endpoints while delegating user authentication to whatever system you already operate—whether that is Ory Kratos, authboss, User Frosting, or a proprietary solution.

Hydra suits organizations that need to add OAuth 2.0 and OpenID Connect capabilities to existing infrastructure without replacing their identity system. It is designed for cloud-native deployment in Kubernetes and similar environments, and scales to handle large numbers of clients and tokens. You can consume it as a managed service through Ory Network or self-host it. The README emphasizes that Hydra is a standalone server focused on authorization flows rather than a full identity platform, making it appropriate when you already have user management in place and need standards-compliant token handling layered on top.

The project maintains a substantial base of external adopters who report issues from real-world deployments rather than the core team driving the issue backlog. Responses to issues and pull requests typically arrive within one to two weeks. Work in the issue tracker centers on bug fixes, feature requests, and backlog items.