kratos

ory/kratos

Headless cloud-native authentication and identity management written in Go. Scales to a billion+ users. Replace Homegrown, Auth0, Okta, Firebase with better UX and DX. Passkeys, Social Sign In, OIDC, Magic Link, Multi-Factor Auth, SMS, SAML, TOTP, and more. Runs everywhere, runs best on Ory Network.

Ship status

Slowed

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

Last push
29 Jul 2026
106 days ago
Ship score
24/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 13,895 → 13,951 (29 Sep – 10 Nov 2026)
+34 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
14K
Forks
1.2K
Open issues
242
Watchers
112
Primary language
Go
Created
29 May 2018
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. 98 startups in the directory ship primarily in Go.

Topics

#hacktoberfest#identity#identity-management#login#profile-management#registration#user#user-management#user-profile#user-profiles#users

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 96%, self-hostable 81%, 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/kratos, as served from the URL below.
[![OSSEAN: slowed](https://ossean.com/badge/ory/kratos.svg)](https://ossean.com/ory/kratos)

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.