select auth framework

[jxtngx]

select an auth provider based on:

• ease of integration with shadcn/ui if no prebuilt components
• state of open source repo
• repo owner and perceived business health
• security considerations (find out what great looks like for authsec)

[jxtngx]

not selected

• authjs + neon had too much overhead and took away from focus on underlying tasks that have to do with torchtune
• workos also had too much overhead
• stack auth is too new of a company to depend on regardless of integration with neon, there was more of a learning curve than authjs and workos, and docx was low
• supabase-auth has an existing example with shadcn however, it seems best to opt for auth0 or clerk
• clerk is very easy to implement however, i think it is good to force use of a lower level library for experience sake

Note

any mention of "too much overhead" has to do with lack of familiarity with auth concepts and typescript, and not actual difficulty for someone who is maybe more familiar with auth and js/ts

remaining candidates

auth0 is comparable to clerk more than it is comparable to supabase-auth.

evaluating auth0 has more to do with selecting either neon or supabase more than it does selecting auth0. going with auth0 seems to be a safe default when it comes to auth providers.

selected

• auth0 + neon
• autho0 + supabase

the desired bar

ideally, the level of experience or skill to reach seems to be some combination of of authjs + an auth provider (auth0) + a user db provider (supabase or neon)