hydra

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.

Ship status

Slowed

Last push 31–120 days ago. Quiet, not gone.

Last push
29 Jul 2026
105 days ago
Ship score
24/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 17,575 → 17,655 (29 Sep – 10 Nov 2026)
+51 stars in the 28 days to 10 Nov 2026

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
17.7K
Forks
1.6K
Open issues
91
Watchers
235
Primary language
Go
Created
22 May 2015
Owner
ory · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 99 startups in the directory ship primarily in Go.

Topics

#authorization#cloud#docker#federation#hydra#identity#mcp#oauth#oauth-provider#oauth2#oauth2-provider#oauth2-server#oidc#openid#openid-connect#openid-connect-provider#openid-provider#security#server#sso

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 22 Sep 2026 — os_startup 98%, self-hostable 94%, hosted offering 94%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the Sep 2025 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: slowed — last push 29 Jul 2026This is the badge for ory/hydra, as served from the URL below.
[![OSSEAN: slowed](https://ossean.com/badge/ory/hydra.svg)](https://ossean.com/ory/hydra)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.