{"slug": "ory", "name": "Ory", "category": "security", "category_name": "Security and passwords", "description": "", "recommenders": 1, "commenters": 3, "warners": 1, "score": 0.138, "rising": -0.33, "first": "2026-06-11", "latest": "2026-08-28", "why": "I love Ory and I'm always amazed by your new releases!", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 1, "neutral": 0, "compare": 1, "warn": 1}, "spark": [0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0], "listed": false, "loved": [], "caveat": "", "short_quote": "I love Ory and I'm always amazed by your new releases!", "icon": false, "domain": null, "github_repo": null, "official_url": "", "pricing": "", "aliases": ["Ory"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 775873489, "item_id": 48492093, "url": "https://news.ycombinator.com/item?id=48492093", "by": "denysvitali", "date": "2026-06-11", "stance": "recommend", "quote": "I love Ory and I'm always amazed by your new releases!", "excerpt": "So this seems to be M2M tokens - what about the, arguably more common, use case of creating a short lived or simply ephemeral token to allow an AI agent to use a service (e.g: GitHub) without the possibility to have it leak a valid upstream token in a commit message? My solution to this particular problem is gh-proxy - but of course GitHub is only one of the 100s of services that one might want this for. https://gith", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: Open-source API Key server written in Go by Ory"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 791695697, "item_id": 49480981, "url": "https://news.ycombinator.com/item?id=49480981", "by": "sceptic123", "date": "2026-08-28", "stance": "warn", "quote": "For the record we looked at Ory early on, but it was not mature enough and didn't offer a full IdP stack at the time.", "excerpt": "We've been using Keycloak for a while, it's definitely not bad, but there are times when it's been frustrating, and getting it both stable and scalable seem to be incompatible goals. It's super powerful and can do whatever you want it to do (at least if you are comfortable writing Java SPI). But there's a lot of knowledge of how to set things up that takes time and is not readily acquired. For the record we looked at", "context": "", "use_case": "identity provider", "switched_from": "", "story": "I used AWS cognito for a startup. I wouldn't do it again"}]}], "who": [], "tags": [], "use_cases": ["identity provider", "auth"], "compared": [{"slug": "keycloak", "name": "Keycloak", "co": 3, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=49478091", "title": "I used AWS cognito for a startup. I wouldn't do it again", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48668033", "title": "Cloudflare launched self-managed OAuth for all", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48491426", "title": "Show HN: Open-source API Key server written in Go by Ory", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {"recommend": 1, "compare": 1}, "2026-07": {}, "2026-08": {"warn": 1}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 791695697, "item_id": 49480981, "url": "https://news.ycombinator.com/item?id=49480981", "by": "sceptic123", "date": "2026-08-28", "stance": "warn", "quote": "For the record we looked at Ory early on, but it was not mature enough and didn't offer a full IdP stack at the time.", "excerpt": "We've been using Keycloak for a while, it's definitely not bad, but there are times when it's been frustrating, and getting it both stable and scalable seem to be incompatible goals. It's super powerful and can do whatever you want it to do (at least if you are comfortable writing Java SPI). But there's a lot of knowledge of how to set things up that takes time and is not readily acquired. For the record we looked at", "context": "", "use_case": "identity provider", "switched_from": "", "story": "I used AWS cognito for a startup. I wouldn't do it again"}, {"id": 778735793, "item_id": 48670987, "url": "https://news.ycombinator.com/item?id=48670987", "by": "v5v3", "date": "2026-06-25", "stance": "compare", "quote": "Ory Enterprise License: Unlock enterprise-grade features like security SLAs for CVEs, SAML, B2B organizations, multi-tenancy, and better scalability.", "excerpt": "\"Ory Enterprise License: Unlock enterprise-grade features like security SLAs for CVEs, SAML, B2B organizations, multi-tenancy, and better scalability.\" [0] Or just stick with KeyCloak that offers a full self hosted product... [1] [0]https://github.com/ory [1]https://www.keycloak.org/", "context": "", "use_case": "auth", "switched_from": "", "story": "Cloudflare launched self-managed OAuth for all"}, {"id": 775873489, "item_id": 48492093, "url": "https://news.ycombinator.com/item?id=48492093", "by": "denysvitali", "date": "2026-06-11", "stance": "recommend", "quote": "I love Ory and I'm always amazed by your new releases!", "excerpt": "So this seems to be M2M tokens - what about the, arguably more common, use case of creating a short lived or simply ephemeral token to allow an AI agent to use a service (e.g: GitHub) without the possibility to have it leak a valid upstream token in a commit message? My solution to this particular problem is gh-proxy - but of course GitHub is only one of the 100s of services that one might want this for. https://gith", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: Open-source API Key server written in Go by Ory"}]}