HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ory
kratos
Go2020–2025
ory / kratos

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.

32Distinct people
36Mentions
0Explicit recommenders
14KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year36 dated mentions

Observed mentions: 2020-08-29 06:10:06 UTC to 2025-11-13 14:14:36 UTC.

02468102020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 3 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC404
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC808
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC615
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC927
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC532
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC422

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Chat · Discussions · Newsletter · Docs · Try Ory Network · Jobs Ory Kratos is an API first identity and user management system for cloud native applications. It centralizes login, registration, recovery, verification, and profile management flows so your services consume them instead of reimplementing them. Table of contents What is Ory Kratos? Why Ory Kratos Migrating from Auth0, Okta, and similar providers Deployment options Use Ory Kratos on the Ory Network Self-host Ory Kratos Quickstart Who is using it? What is Ory Kratos? Ory Kratos is an API first identity and user management system that follows cloud architecture best practices. It focuses on core identity workflows that almost every application needs: Self service login and registration Account verification and recovery Multi factor authentication Profile and account management Identity schemas and traits Admin APIs for lifecycle management We recommend starting with the Ory Kratos introduction docs to learn more about its architecture, feature set, and how it compares to other systems. Why Ory Kratos Ory Kratos is designed to: Remove identity logic from your application code and expose it over HTTP APIs Work well with any UI framework through browser based and native app flows Scale to large numbers of identities and devices Integrate with the rest of the Ory stack for OAuth2, OpenID Connect, and access control Fit into modern cloud native environments such as Kubernetes and managed platforms Migrating from Auth0, Okta, and similar providers If you are migrating from Auth0, Okta, or another identity provider that uses OAuth2 / OpenID Connect based login, consider using Ory Hydra + Ory Kratos together: Ory Hydra acts as the OAuth2 and OpenID Connect provider and can replace most authorization server and token issuing capabilities of your existing IdP. Ory Kratos provides identity, credentials, and user-facing flows (login, registration, recovery, verification, profile management). This combination is often a drop-in replacement for OAuth2 and OpenID Connect capabilities at the protocol level. In practice, you update client configuration and endpoints to point to Hydra, migrate identities into Kratos, and keep your applications speaking the same OAuth2 / OIDC protocols they already use. Deployment options You can run Ory Kratos in two main ways: As a managed service on the Ory Network As a self hosted service under your own control, with or without the Ory Enterprise License Use Ory Kratos on the Ory Network The Ory Network is the fastest way to use Ory services in production. Ory Identities is powered by the open source Ory Kratos server and is API compatible. The Ory Network provides: Identity and credential management that scales to billions of users and devices Registration, login, and account management flows for passkeys, biometrics, social login, SSO, and multi factor authentication Prebuilt login, registration, and account management pages and components OAuth2 and OpenID Connect for single sign on, API access, and machine to machine authorization Low latency permission checks based on the Zanzibar model with the Ory Permission Language GDPR friendly storage with data locality and compliance in mind Web based Ory Console and Ory CLI for administration and operations Cloud native APIs compatible with the open source servers Fair, usage based pricing Sign up for a free developer account to get started. Self-host Ory Kratos You can run Ory Kratos yourself for full control over infrastructure, deployment, and customization. The install guide explains how to: Install Kratos on Linux, macOS, Windows, and Docker Configure databases such as PostgreSQL, MySQL, and CockroachDB Deploy to Kubernetes and other orchestration systems Build Kratos from source This guide uses the open source distribution to get you started without license requirements. It is a great fit for individuals, researchers, hackers, and companies that want to experiment, prototype, or run unimportant workloads without SLAs. You get the full core engine, and you are free to inspect, extend, and build it from source. If you run Kratos as part of a business-critical system, for example login and account recovery for all your users, you should use a commercial agreement to reduce operational and security risk. The Ory Enterprise License (OEL) layers on top of self-hosted Kratos and provides: Additional enterprise features that are not available in the open source version such as SCIM, SAML, organization login ("SSO"), CAPTCHAs and more Regular security releases, including CVE patches, with service level agreements Support for advanced scaling, multi-tenancy, and complex deployments Premium support options with SLAs, direct access to engineers, and onboarding help Access to a private Docker registry with frequent and vetted, up-to-date enterprise builds For guaranteed CVE fixes, current enterprise builds, advanced features, and support in production, you need a valid Ory Enterprise License and access to the Ory Enterprise Docker registry. To learn more, contact the Ory team. Quickstart Install the Ory CLI and create a new project to try Ory Identities. # Install the Ory CLI if you do not have it yet: bash <(curl https://raw.githubusercontent.com/ory/meta/master/install.sh) -b . ory sudo mv ./ory /usr/local/bin/ # Sign in or sign up ory auth # Create a new project ory create project --create-workspace "Ory Open Source" --name "GitHub Quickstart" --use-project ory open ax login Who is using it? The Ory community stands on the shoulders of individuals, companies, and maintainers. The Ory team thanks everyone involved - from submitting bug reports and feature requests, to contributing patches and documentation. The Ory community counts more than 50.000 members and is growing. The Ory stack protects 7.000.000.000+ API requests every day across thousands of companies. None of this would have been possible without each and everyone
Read the full README on GitHub

What Hacker News says

6 sources
Congratulations on Kratos coming out of Beta. We evaluated Ory a few months ago. My understanding: 1. Ory Kratos provides session-based authentication and user management. 2. Ory Hydra is a self-managed server that secures access to your applications and APIs with OAuth 2.0 and OpenID Connect. Basically we want to replace AWS Cognito (which is pretty much abandonware) to secure our API so we needed both applications. Unfortunately we had to put our efforts on hold: 1. Bugs around traits meant we had issues around password change, password recovery and email change/reverifications for our use-case 2. Lack of documentation prevented us making progress on 2FA/WebAuthn 3. Bearer token/Oauth consent flow wasn't available without a lot of work because Kratos and Hydra are not "integrated" [1]. Someone shows how they rolled their own integration
Read the rest
[2]. I'd love for someone to advise that we were wrong or misunderstood things or that things have moved on since then! [1] https://github.com/ory/kratos/issues/273 [2] https://blog.px.dev/open-source-auth/
In Show HN: Ory Kratos – Open-source identity server written in Go
Congrats on the launch! I'm curious about how this compares to existing Auth microservice solutions like Ory Kratos[0][1]. For the "short-lived tokens" that you mention, is that similar to Ory Kratos used with Ory Oathkeeper[2][3] with JWTs? That's a similar approach that I've seen companies like Uber taking for their microservice Auth. 0: https://www.ory.sh/kratos/ 1: https://github.com/ory/kratos 2: https://www.ory.sh/docs/kratos/guides/zero-trust-iap-proxy-i... 3: https://github.com/ory/oathkeeper
In Launch HN: PropelAuth (YC W22) – End-to-end auth service for B2B products
> Cool to see such a comprehensive guide! At the same time, are people seriously still pushing OAuth2 for first party auth? Shouldn’t everyone know by one that OAuth does not solve... I assume you are using "Auth" for authentication, and not authorization (as OAuth does). Indeed, OAuth does zero for first or third party authentication of users - authentication is a set of extensions provided by OpenID Connect. The reason people use OpenID Connect as the API for first party authentication is because you _need_ an API for integrating externalized authentication systems, and (excluding SAML) every other system is proprietary with minimal cross-vendor support. However, that OpenID Connect API only provides for authentication with a few (possibly supported) hints for behavior. It is up to the OpenID Provider software to provide all the IAM fea
Read the rest
tures you mention - registration, account recover, profile management, multi-factor authentication, etc. There is no standard for registration, account recovery, profile management, or MFA because all of these are business processes or user experience customizations - they are software, not protocols. That is why OpenID Connect is used to integrate with a piece of off-the-shelf software which implements your business policy and which is customized for your desired experience. At most, you see things like https://github.com/w3c/webappsec-change-password-url - website configuration to tell a password manager where to navigate the browser in order to change the user's password. > I think it’s exciting to see new open source projects like https://github.com/ory/kratos or https://github.com/supertokens/supertokens-core that finally break up this misconception! These both have the same architecture as say an Auth0. Supertokens API provides a proprietary alternative to a constrained OpenID Connect protocol. Kratos has a companion project which exposes the server via OpenID Connect. The supertokens API may have been easier for _them_ to implement than all of the potential OAuth and OpenID Connect extensions, but when going with constrained profiles like the OpenID Connect Basic Client Profile it would be difficult to be substantially simpler without being less secure.
In The Modern Guide to OAuth

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.