Live data from Hacker News

From Supabase to Clerk to Better Auth

blog.val.town

81–90 of 259 posts

Re: From Supabase to Clerk to Better Auth

#81

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.

Majority of apps are B2C apps, they don't need any of this.

All you need is Apple and Google Oauth.

Re: From Supabase to Clerk to Better Auth

#82

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.

Django, Rails etc handles this.

Re: From Supabase to Clerk to Better Auth

#83

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

People are very scared of messing up authentication and getting hacked. They would rather offload that responsibility to a third party and not think about it.

Re: From Supabase to Clerk to Better Auth

#84
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.

If you’re implying that people should __always__ roll their own services and never vendor out non-core parts, the security industry would love to learn where you work.

Re: From Supabase to Clerk to Better Auth

#85
post #4

> Some important context is that Clerk is a major success. They just raised 50 million dollars and they have lots of satisfied users. And even more users who are looking to escape. Clerk is just a mess. They are trying to cram EVERYTHING into their libraries: Web3 crap, Stripe, etc. Clerk's JS blob is now triggering the browser inspectors for being slow to load. Every time when we upgraded React, Clerk libraries were…

> And even more users who are looking to escape. Uhm, companies like Replit and several other large startups are actually adopting Clerk. I guess if your world mainly revolves around X (formerly Twitter), it can seem like everyone is moving away from Clerk. Also, Better Auth’s X presence is pretty much centered around criticizing every auth provider out there, so the discourse there tends to skew heavily negative.

> Also, Better Auth’s X presence is pretty much centered around criticizing every auth provider out there, so the discourse there tends to skew heavily negative.

This from an account created 2 hours ago, with a username that’s a negation of the BetterAuth founder…

If you’re Clerk stakeholder why not just come out as yourself and engage openly!

Re: From Supabase to Clerk to Better Auth

#86

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 am just as confused as you. My 2c: For a broad range of requirements, running your DB directly and managing auth with Django or similar is easier. Perhaps at enterprise scale, this changes.

[dead]
Post reply on HN