Live data from Hacker News

From Supabase to Clerk to Better Auth

blog.val.town

101–110 of 259 posts

Re: From Supabase to Clerk to Better Auth

#101

Tom's articles are always a good read. Anyone remember Auth0 and passportjs? The churn of auth services is never ending, but I suppose so are the standards.

Disclaimer: I work for an Auth0 competitor, FusionAuth.

Heya, Auth0 is still around! They got bought by Okta in 2021 but still have a free tier and we see them in a lot of bake-offs.

Re: From Supabase to Clerk to Better Auth

#102
post #73

Earlier quoted context omitted.

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

Clerk looks _really_ good initially. It's perfect if you want to prototype something and not care about auth. It's only when you start getting into the details that you begin to suffer. For example, there's _still_ no way to do offline auth on mobile. So that your application could be opened if there's no connectivity at the moment. But hey, you can do the Metamask Web3 blockchain thingie! I have never used Twitter/X…

> offline auth on mobile

Does Better Auth offer this? Or any other auth libraries or solutions? I haven't heard of any, but haven't done an intensive look either.

I suppose you could do something with a cached JWT or cached password hash (though sending a password hash to a mobile client spooks me).

I'm in the space and interested in learning more.

Re: From Supabase to Clerk to Better Auth

#103
post #49

in rails I just authentication-zero. no need for 3rd party provider.

Is that the new library that came out in rails 8? Saw someone present on that at RailsConf 2025 and it seemed like a great solution for all rails apps. Hope it leads that ecosystem to get rid of devise (which I always found confusing).

Re: From Supabase to Clerk to Better Auth

#104
post #34

Using Clerk, quite unhappy with it. No proper RBAC (roles are tied to organizations, not stored on user itself, so you cannot have a concept of global admin or something like that, unless you use metadata for storing arbitrary key value paris), and more than once in the past weeks/months it had a downtime causing the whole app to fail. Would think twice before using it in the future.

i'm currently in the process of evaluating switching our b2b app off clerk too. a customer asked for custom roles (diverging from our default set), which is technically possible on clerk now with role sets, but it's a bit of a workaround rather than first class.

thankfully i'm familiar with better auth from a side project, but migrating SSO/SCIM sounds like it might be a bit of a pain

Re: From Supabase to Clerk to Better Auth

#105

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?

You might be interested in some of the presentations at KeyConf[0]. You can also get some real world stories from the Reddit[1].

I was at KubeCon EU this year (representing my employer, FusionAuth) and there were lots of folks who were running Keycloak who came and chatted with us.

It's a different set of tradeoffs than Auth0 or other SaaS services. More control, but more responsibility too.

0: https://events.linuxfoundation.org/kubecon-cloudnativecon-eu...

1: https://www.reddit.com/r/KeyCloak/

Re: From Supabase to Clerk to Better Auth

#106
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

I feel seen. It's compounded if you also need to add HIPAA row-level security compliance that spans to every form of resource.

Re: From Supabase to Clerk to Better Auth

#107
post #65

Earlier quoted context omitted.

"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

Possibly didn’t want to accept the additional risk that comes with rolling your own auth as well.

Re: From Supabase to Clerk to Better Auth

#108
post #30

The homepage of val.town says "Zapier for know-code engineers".. Is KNOW -code engineer a term?

It's just a play on the phrase "no code". Maybe you can help me out: I still have no idea what val.town is. I guess it's an alternative to Cloudflare Workers?

Hey, I work at Val Town, and we definitely struggle to describe what it is because the platform is so broad, but I'll try: a javascript code editor in the browser that auto-deploys that code to our servers whenever you edit a file. You can run code by clicking a button, on a cron, via HTTP. And there's other stuff like SQLite and blob storage

So yes, like Cloudflare Workers in some ways. Or like CodePen but fullstack. Or Replit. The val town "founding poem" was:

> If GitHub Gists could run,

> And AWS Lambda were fun

Re: From Supabase to Clerk to Better Auth

#109
post #30

The homepage of val.town says "Zapier for know-code engineers".. Is KNOW -code engineer a term?

It's just a play on the phrase "no code". Maybe you can help me out: I still have no idea what val.town is. I guess it's an alternative to Cloudflare Workers?

This comment thread was a nudge to push out a quick experimental change to the val.town landing page, so thank you. Very open to feedback on that messaging if anyone has any. Most customers these days ask about using val town with claude code, so you could also think of us as a deployment platform for vibe coded apps

Re: From Supabase to Clerk to Better Auth

#110
post #73

Earlier quoted context omitted.

Clerk looks _really_ good initially. It's perfect if you want to prototype something and not care about auth. It's only when you start getting into the details that you begin to suffer. For example, there's _still_ no way to do offline auth on mobile. So that your application could be opened if there's no connectivity at the moment. But hey, you can do the Metamask Web3 blockchain thingie! I have never used Twitter/X…

> offline auth on mobile Does Better Auth offer this? Or any other auth libraries or solutions? I haven't heard of any, but haven't done an intensive look either. I suppose you could do something with a cached JWT or cached password hash (though sending a password hash to a mobile client spooks me). I'm in the space and interested in learning more.

We ended up caching the credentials and the JWT refresh token from Clerk, and then manually requesting the access token using the Clerk's sparsely documented frontend API. Except that to do this with Clerk, we needed to fake the cache API and then pluck the token out of the undocumented "__clerk_client_jwt" key.

This is supported by Better Auth out-of-the box. It doesn't hide these kinds of stuff from you.

Post reply on HN