Live data from Hacker News

From Supabase to Clerk to Better Auth

blog.val.town

61–70 of 259 posts

Re: From Supabase to Clerk to Better Auth

#61
post #48

Earlier quoted context omitted.

Why pay someone to build a house? I’m sure you could do it yourself…but that doesn’t mean that is the best use of your time in all cases. The analogy is basic but apt; not everyone needs or wants to run (or create) every mechanism. I don’t do all of my own hosting either and it’s not because I couldn’t, it’s that it isn’t worthwhile in my cases. To expand a bit more: if a business is faced with a choice to save some…

This comment is more ridiculous than ever in 2026.

Yes the analogy doesn't work here because that is much more cost prohibitive and labor intensive.

Re: From Supabase to Clerk to Better Auth

#62

Earlier quoted context omitted.

I remember Laravel with Socialite [0]. Laravel is what I usually reach for Web SaaS MVP. You only need a VPS and a managed database for testing out the market and can scale a lot without increasing expenses that much.. [0]: https://laravel.com/docs/13.x/socialite

Take this post down immediately ! /jk

Lol, I developed for entrepreneurs who mostly wanted a working proof of concept of their ideas. I guess now you can vibecode them with SaaS for core technical needs.

Re: From Supabase to Clerk to Better Auth

#63

Has anyone used Keycloak for actual production? I have often thought about it but I stick to Auth0 just because I don't know if Keycloak has a good track record?

For what it's worth Authentik has been listing Cloudflare as a customer for a while. Worth a look. There might be something in their blog.

Re: From Supabase to Clerk to Better Auth

#64
post #37

Can someone more intelligent then me tell me why should I offload my postgres users table to some 3rd party provider? Like what is so hard about keeping that table in my VM on hetzner that I have to give it off to someone else? It's not payments, it's just a few fields of data

Start any greenfield project, hand-coded auth takes up 50% of the development time of the entire MVP

[dead]

Re: From Supabase to Clerk to Better Auth

#65

Can someone more intelligent then me tell me why should I offload my postgres users table to some 3rd party provider? Like what is so hard about keeping that table in my VM on hetzner that I have to give it off to someone else? It's not payments, it's just a few fields of data

It’s just a few fields until it’s not. SSO, SAML, SCIM, OIDC, OAuth, 2FA, passwordless auth, verification tokens, etc etc, And, variations of each for wildly popular systems you’ll be expected to integrate with but don’t support the exact spec. For a while at my company, half our support engineers time went to handling random SSO issues that came up in our home built auth system.

"home built auth system" is bound to have "random SSO issues". You fix them, that's how things mature.

Re: From Supabase to Clerk to Better Auth

#66
post #48

Earlier quoted context omitted.

Why pay someone to build a house? I’m sure you could do it yourself…but that doesn’t mean that is the best use of your time in all cases. The analogy is basic but apt; not everyone needs or wants to run (or create) every mechanism. I don’t do all of my own hosting either and it’s not because I couldn’t, it’s that it isn’t worthwhile in my cases. To expand a bit more: if a business is faced with a choice to save some…

This comment is more ridiculous than ever in 2026.

Because of AI or because hackers are hyper targeting infra clusters?

Re: From Supabase to Clerk to Better Auth

#67
post #37

Can someone more intelligent then me tell me why should I offload my postgres users table to some 3rd party provider? Like what is so hard about keeping that table in my VM on hetzner that I have to give it off to someone else? It's not payments, it's just a few fields of data

Start any greenfield project, hand-coded auth takes up 50% of the development time of the entire MVP

…use Django, install auth modules

Re: From Supabase to Clerk to Better Auth

#68

Earlier quoted context omitted.

It takes like an hour. So that's a quick mvp then

Social logins, email logins, password resets, multi-tenant, organizations, many to many users to organizations, etc etc. Not necessary for MVP, but can definitely be painful hacking in later if the MVP hits.

All I am seeing here is Django modules

Re: From Supabase to Clerk to Better Auth

#69
post #65

Earlier quoted context omitted.

It’s just a few fields until it’s not. SSO, SAML, SCIM, OIDC, OAuth, 2FA, passwordless auth, verification tokens, etc etc, And, variations of each for wildly popular systems you’ll be expected to integrate with but don’t support the exact spec. For a while at my company, half our support engineers time went to handling random SSO issues that came up in our home built auth system.

"home built auth system" is bound to have "random SSO issues". You fix them, that's how things mature.

I'm guessing they simply didnt want to spend the time and money doing that

Re: From Supabase to Clerk to Better Auth

#70

Can someone more intelligent then me tell me why should I offload my postgres users table to some 3rd party provider? Like what is so hard about keeping that table in my VM on hetzner that I have to give it off to someone else? It's not payments, it's just a few fields of data

I must as intelligent as you because I also never understood why things like supabase even exist. I believe this shows how much front-end dev world is detached from how things can simple and secure by default.
Post reply on HN