ory /hydra
Internet-scale OpenID Certified™ OpenID Connect and OAuth2.1 provider that integrates with your user management through headless APIs. Solve OIDC/OAuth2 user cases over night. Consume as a service on Ory Network or self-host. Trusted by OpenAI and many others for scale and security. Written in Go.
★ 17,668⑂ 1,624👁 235⑃ 1,952● 1,618▤ 205
+4
日增长
17,668
stars
1,624
forks
235
watchers
1,952
prs
1,618
issues
205
releases
README
Chat ·
Discussions ·
Newsletter ·
Docs ·
Try Ory Network ·
Jobs
Ory Hydra is a hardened, OpenID Certified OAuth 2.0 Server and OpenID Connect
Provider optimized for low-latency, high throughput, and low resource
consumption. It connects to your existing identity provider through a login and
consent app, giving you absolute control over the user interface and experience.
---
- What is Ory Hydra?
- Why Ory Hydra
- OAuth2 and OpenID Connect: Open Standards
- OpenID Connect Certified
- Deployment options
- Use Ory Hydra on the Ory Network
- Self-host Ory Hydra
- Quickstart
- Who is using Ory Hydra
- Ecosystem
- Ory Kratos: Identity and User Infrastructure and Management
- Ory Hydra: OAuth2 & OpenID Connect Server
- Ory Oathkeeper: Identity & Access Proxy
- Ory Keto: Access Control Policies as a Server
- Documentation
- Developing Ory Hydra
- Security
- Disclosing vulnerabilities
- Telemetry
- Libraries and third-party projects
What is Ory Hydra?
Ory Hydra is a server implementation of the OAuth 2.0 authorization framework
and the OpenID Connect Core 1.0. It follows
cloud architecture best practices
and focuses on:
- OAuth 2.0 and OpenID Connect flows
- Token issuance and validation
- Client management
- Consent and login flow orchestration
- JWKS management
- Low latency and high throughput
We recommend starting with the
Ory Hydra introduction docs to learn more
about its architecture, feature set, and how it compares to other systems.
Why Ory Hydra
Ory Hydra is designed to:
- Be a standalone OAuth 2.0 and OpenID Connect server without user management
- Connect to any existing identity provider through a login and consent app
- Give you absolute control over the user interface and experience flows
- Work with any authentication endpoint:
Ory Kratos,
authboss,
User Frosting, or your proprietary system
- Scale to large numbers of clients and tokens
- Fit into modern cloud native environments such as Kubernetes and managed
platforms
OAuth2 and OpenID Connect: Open Standards
Ory Hydra implements Open Standards set by the IETF:
- The OAuth 2.0 Authorization Framework
- OAuth 2.0 Threat Model and Security Considerations
- OAuth 2.0 Token Revocation
- OAuth 2.0 Token Introspection
- OAuth 2.0 for Native Apps
- OAuth 2.0 Dynamic Client Registration Protocol
- OAuth 2.0 Dynamic Client Registration Management Protocol
- Proof Key for Code Exchange by OAuth Public Clients
- JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants
and the OpenID Foundation:
- OpenID Connect Core 1.0
- OpenID Connect Discovery 1.0
- OpenID Connect Dynamic Client Registration 1.0
- OpenID Connect Front-Channel Logout 1.0
- OpenID Connect Back-Channel Logout 1.0
OpenID Connect Certified
Ory Hydra is an OpenID Foundation
certified OpenID Provider (OP).
The following OpenID profiles are certified:
- Basic OpenID Provider
(response types code)
- Implicit OpenID Provider
(resTop issues
#1218Support RFC8693: Token Exchange45 comments · 2018-12-08#3955The current challenge is too long and may be mistakenly identified as risky by the browser9 comments · 2025-03-04#4091Post Quantum Roadmap8 comments · 2026-04-14#4061Support "Client ID Metadata Document" (CIMD)8 comments · 2026-01-17#3703Reading cookie in cross-site context will be blocked in future Chrome versions7 comments · 2024-01-25#3622Opentelemetry spans names have changed when changed tracing_provider7 comments · 2023-08-30#3132Cannot force front/back-channel logout with id_token_hint when "Remember Me" is off6 comments · 2022-06-01#3671When the database cannot be connected, /oauth2/token returns a 401 status code instead of 5005 comments · 2023-11-24
Discussions
#4140Ory Open Source release cadence from 20272 comments · 2026-11-12#4138Support prompt=none with skip_consent clients1 comments · 2026-10-30#4107Timeout issue - refresh_token flow takes more than 10s1 comments · 2026-06-12#4103Best Practice for Using Ory Hydra/Kratos on Android POS Devices Without Browser-Based Login1 comments · 2026-05-20#4096Suddenly throwing temporarily_unavailable errors1 comments · 2026-04-22#4081Building a Centralized Identity and Authorization Platform with Ory0 comments · 2026-03-13#4074User sessions getting logged out after upgrading Hydra from v2.2.0 to v25.4 (self-hosted on Kubernetes)0 comments · 2026-03-02#4072MySQL 8.4 warnings about invalid foreign keys0 comments · 2026-02-26
Latest release
v26.2.0 v26.2.0 2026-03-20v26.2.0 Bug Fixes - Always retry curl invocations to surmount transient third-party failures (c28a6c8): - Broken older down migrations (8ed407d): - Context passing and limit response size (f33d6a8): - Context passing in jsonnetsecure (5884774): - Correctly detect when to use self-signed certificates (6f9af27): - Correctly scan SQL NULL into go JSON types (163c579): - Data race in hydra-oss test (262f85b): - deps: Update dependency prettier to v3.7.4 (106865d): - Do not cache pairwise subject algorithm (a341867): - Down migrations in newer MySQL versions (5b0360d): - Fix benchmark