{"slug": "auth0", "name": "Auth0", "category": "security", "category_name": "Security and passwords", "description": "", "recommenders": 1, "commenters": 8, "warners": 3, "score": -0.667, "rising": -0.33, "first": "2025-12-20", "latest": "2026-08-28", "why": "for auth I use auth0, because I am too lazy to run keycloak", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 1, "neutral": 4, "compare": 0, "warn": 3}, "spark": [0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0], "listed": false, "loved": [], "caveat": "", "short_quote": "for auth I use auth0, because I am too lazy to run keycloak", "icon": false, "domain": "auth0.com", "github_repo": null, "official_url": "https://auth0.com", "pricing": "", "aliases": ["Auth0"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 776410416, "item_id": 48525651, "url": "https://news.ycombinator.com/item?id=48525651", "by": "Traubenfuchs", "date": "2026-06-14", "stance": "recommend", "quote": "for auth I use auth0, because I am too lazy to run keycloak", "excerpt": "> specialized hosting What do you mean? My private next.js fullstack slop runs dockerized on my kubernetes cluster and for auth I use auth0, because I am too lazy to run keycloak or whatever dockerized auth slop is currently en vogue.", "context": "", "use_case": "authentication", "switched_from": "", "story": "Phoenix LiveView 1.2 Released"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 768734930, "item_id": 48045933, "url": "https://news.ycombinator.com/item?id=48045933", "by": "jillesvangurp", "date": "2026-05-06", "stance": "warn", "quote": "But don't deviate from the happy path!", "excerpt": "This sounds like moving the problem, not solving it. I've been doing server based systems since forever and sso is this big complicated topic where people seem to bias to using either really complicated and convoluted enterprise solutions or some walled garden with lots of limitations. In both cases you are buying into somebody else's solution. That complex framework is complex because the company behind it threw eve", "context": "", "use_case": "auth", "switched_from": "", "story": "From Supabase to Clerk to Better Auth"}, {"id": 768719282, "item_id": 48044955, "url": "https://news.ycombinator.com/item?id=48044955", "by": "jakubriedl", "date": "2026-05-06", "stance": "warn", "quote": "I really don't see a single reason why I would pick Clerk, Auth0, Kinde, ...", "excerpt": "I've recently switched from Clerk to BetterAuth as well and it's really good and definitely would recommend to anyone. It supports more things I need, it's more reliable, and much cheaper. The reason why it work for me is that it's finally a open-source solution that is on par or better with commercial. When I've selected Clerk originally the reason was that there wasn't open-source alternative, and I won't roll my o", "context": "", "use_case": "authentication", "switched_from": "", "story": "From Supabase to Clerk to Better Auth"}, {"id": 757100867, "item_id": 47318804, "url": "https://news.ycombinator.com/item?id=47318804", "by": "brian200", "date": "2026-03-09", "stance": "warn", "quote": "I didn't want to set up Auth0 for a server only I use.", "excerpt": "I built a mem0-based personal memory server \u2014 a knowledge vault Claude can read/write to. Getting it working in Claude Code was easy. Claude.ai web, mobile, and Desktop? Much harder, because of auth. Claude.ai custom connectors require full OAuth 2.1. FastMCP gives you an in-memory test provider (useless in prod) or a proxy that requires Google/GitHub/Auth0 as an identity provider. I didn't want to set up Auth0 for a", "context": "", "use_case": "", "switched_from": "", "story": "Personal MCP server on every Claude platform without Auth0"}]}], "who": [{"by": "edent", "context": "maintains OpenBenches", "url": "https://news.ycombinator.com/item?id=46341344", "date": "2025-12-20"}], "tags": [], "use_cases": ["authentication", "sso across subdomains", "auth", "dynamic client registration"], "compared": [{"slug": "aws-cognito", "name": "AWS Cognito", "co": 1, "switched_from": 0, "switched_to": 1}, {"slug": "keycloak", "name": "Keycloak", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=48038827", "title": "From Supabase to Clerk to Better Auth", "mentions": 2}, {"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=48821747", "title": "Ask HN: How do I setup SSO and SLO on my two WP websites with separate databases", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48524293", "title": "Phoenix LiveView 1.2 Released", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47318803", "title": "Personal MCP server on every Claude platform without Auth0", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46846055", "title": "Ask HN: How do you handle auth when AI dev agents spin up short-lived apps?", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {"neutral": 1}, "2026-01": {}, "2026-02": {"neutral": 1}, "2026-03": {"warn": 1}, "2026-04": {}, "2026-05": {"warn": 2}, "2026-06": {"recommend": 1}, "2026-07": {"neutral": 1}, "2026-08": {"neutral": 1}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 791659297, "item_id": 49478706, "url": "https://news.ycombinator.com/item?id=49478706", "by": "patwolf", "date": "2026-08-28", "stance": "neutral", "quote": "I mostly used Auth0 in the past", "excerpt": "My experience with Cognito matches the author's experience exactly. I mostly used Auth0 in the past, but we switched to Cognito for a new project because it would be cheaper. Don't like that email addresses are case sensitive, and now you want to change that? Sorry, you gotta create a new user pool from scratch--no way to migrate.", "context": "", "use_case": "authentication", "switched_from": "", "story": "I used AWS cognito for a startup. I wouldn't do it again"}, {"id": 781447392, "item_id": 48840462, "url": "https://news.ycombinator.com/item?id=48840462", "by": "PaiDxng", "date": "2026-07-08", "stance": "neutral", "quote": "Auth0 can share login across subdomains", "excerpt": "It sounds like you\u2019re mixing SSO with user provisioning; Auth0 can share login across subdomains, but each app still needs a plan for creating or syncing user records.", "context": "", "use_case": "SSO across subdomains", "switched_from": "", "story": "Ask HN: How do I setup SSO and SLO on my two WP websites with separate databases"}, {"id": 776410416, "item_id": 48525651, "url": "https://news.ycombinator.com/item?id=48525651", "by": "Traubenfuchs", "date": "2026-06-14", "stance": "recommend", "quote": "for auth I use auth0, because I am too lazy to run keycloak", "excerpt": "> specialized hosting What do you mean? My private next.js fullstack slop runs dockerized on my kubernetes cluster and for auth I use auth0, because I am too lazy to run keycloak or whatever dockerized auth slop is currently en vogue.", "context": "", "use_case": "authentication", "switched_from": "", "story": "Phoenix LiveView 1.2 Released"}, {"id": 768734930, "item_id": 48045933, "url": "https://news.ycombinator.com/item?id=48045933", "by": "jillesvangurp", "date": "2026-05-06", "stance": "warn", "quote": "But don't deviate from the happy path!", "excerpt": "This sounds like moving the problem, not solving it. I've been doing server based systems since forever and sso is this big complicated topic where people seem to bias to using either really complicated and convoluted enterprise solutions or some walled garden with lots of limitations. In both cases you are buying into somebody else's solution. That complex framework is complex because the company behind it threw eve", "context": "", "use_case": "auth", "switched_from": "", "story": "From Supabase to Clerk to Better Auth"}, {"id": 768719282, "item_id": 48044955, "url": "https://news.ycombinator.com/item?id=48044955", "by": "jakubriedl", "date": "2026-05-06", "stance": "warn", "quote": "I really don't see a single reason why I would pick Clerk, Auth0, Kinde, ...", "excerpt": "I've recently switched from Clerk to BetterAuth as well and it's really good and definitely would recommend to anyone. It supports more things I need, it's more reliable, and much cheaper. The reason why it work for me is that it's finally a open-source solution that is on par or better with commercial. When I've selected Clerk originally the reason was that there wasn't open-source alternative, and I won't roll my o", "context": "", "use_case": "authentication", "switched_from": "", "story": "From Supabase to Clerk to Better Auth"}, {"id": 757100867, "item_id": 47318804, "url": "https://news.ycombinator.com/item?id=47318804", "by": "brian200", "date": "2026-03-09", "stance": "warn", "quote": "I didn't want to set up Auth0 for a server only I use.", "excerpt": "I built a mem0-based personal memory server \u2014 a knowledge vault Claude can read/write to. Getting it working in Claude Code was easy. Claude.ai web, mobile, and Desktop? Much harder, because of auth. Claude.ai custom connectors require full OAuth 2.1. FastMCP gives you an in-memory test provider (useless in prod) or a proxy that requires Google/GitHub/Auth0 as an identity provider. I didn't want to set up Auth0 for a", "context": "", "use_case": "", "switched_from": "", "story": "Personal MCP server on every Claude platform without Auth0"}, {"id": 750146704, "item_id": 46884169, "url": "https://news.ycombinator.com/item?id=46884169", "by": "jcmartinezdev", "date": "2026-02-04", "stance": "neutral", "quote": "Some auth providers like Auth0 have support for it", "excerpt": "For what it looks, this is something where DCR (https://openid.net/specs/openid-connect-registration-1_0.html) could be helpful. Some auth providers like Auth0 have support for it: https://auth0.com/docs/get-started/applications/dynamic-client-registration. There are some caveats and security concerns when using DCR, so you should research more into that. Another option may be CIMD (https://www.ietf.org/archive/id/dr", "context": "", "use_case": "dynamic client registration", "switched_from": "", "story": "Ask HN: How do you handle auth when AI dev agents spin up short-lived apps?"}, {"id": 741461504, "item_id": 46341344, "url": "https://news.ycombinator.com/item?id=46341344", "by": "edent", "date": "2025-12-20", "stance": "neutral", "quote": "We use Auth0 for authentication - people editing have to use a social network to log in.", "excerpt": "You are welcome to fork our code for OpenBenches https://github.com/openbenches/openbenches.org/ It is fairly standard PHP + MySQL. We use Auth0 for authentication - people editing have to use a social network to log in. That significantly reduces (but doesn't eliminate) the need for moderation. As for maintenance - once in a while dependabot will say a PHP library is out of date and I'll run the update. Please do la", "context": "maintains OpenBenches", "use_case": "authentication", "switched_from": "", "story": "Why do people leave comments on OpenBenches?"}]}