Auth is not hard to roll yourself. Crypto: don't do it. Auth? Easy peasy.
Better Auth is joining Vercel
11–20 of 95 posts
Re: Better Auth is joining Vercel
#12can Vercel give any assurance that they won’t add a reliance on their closed-source cloud offering for the package? especially given their ownership of next-auth too i really loved better-auth’s DX but the nature of their database adapters means it’s relatively easy to switch over to another provider/library
From what I remember, next-auth is kind of dead and Better Auth developers have been maintaining security of next-auth for some time now. (or was it Vercel that did the maintaining?)
Better Auth is the go-to solution for many people using Nextjs, so it makes sense that Vercel puts some effort in maintaining it.
I have never had issues running Nextjs in regular containers, it is just a good open source solution, I don't see why it would be any different with Better Auth.
Re: Better Auth is joining Vercel
#13Uggggg I just implemented Better Auth for our new product - time to start looking for backup plans. I used to be a huge Vercel fanboy but everything they have done in the last few years turns into a complicated mess.
Re: Better Auth is joining Vercel
#14This is amazing although I would really like for them to explore filling the backend gaps. An acquisition of Trigger.dev or Inngest would be the obvious move and nobody would be surprised. Thoughts?
Re: Better Auth is joining Vercel
#15I used Better Auth for my mobile app backend. It works okayish. My biggest complaints are the OpenAPI specification gets little care, as it mainly caters for JS frontend, and breaking changes in patch version are more common than most packages.
Re: Better Auth is joining Vercel
#16Reminder - KeyCloak was donated to CNCF so a safe choice https://www.keycloak.org https://www.cncf.io/blog/2023/04/11/keycloak-joins-cncf-as-a...
how is this related to better auth ? In my understanding, keycloak and better auth are fundamentally different. I would compare keycloak more with Ory for example.
Re: Better Auth is joining Vercel
#17Uggggg I just implemented Better Auth for our new product - time to start looking for backup plans. I used to be a huge Vercel fanboy but everything they have done in the last few years turns into a complicated mess.
Silent execution of tremor was a pain in the ass trying to upgrade to nextjs 15 / react 19: https://github.com/tremorlabs/tremor/issues/148
Re: Better Auth is joining Vercel
#18Auth is not hard to roll yourself. Crypto: don't do it. Auth? Easy peasy.
Rolling auth by yourself is very messy. Storing tokens correctly, rotating and using correct tokens, with correct parameters and so on. Endless footguns.
Re: Better Auth is joining Vercel
#19Auth is not hard to roll yourself. Crypto: don't do it. Auth? Easy peasy.
Oh man, it really depends(tm). If you are building a small internal app, sure, but you'd often still be better off leveraging a social provider or employee directory.
I work in the auth space (for FusionAuth) and we run into plenty of folks that started out rolling auth themselves. Just username and password right? A bit of hashing, salting and leveraging a built-in crypto library.
But then you need to add account recovery. And then MFA. And then registration. And then progressive registration. And then webhook integration. And then passkeys. And then SAML integration. And the delegated SAML setup. And then and then and then.
You're distracted from your core application by feature requests for your login system.
You have lots of options nowadays. Use a library provided by your framework (Rails, Spring, and Django have them), use a tool like Better Auth, use a third party system like FusionAuth or Auth0. But don't build undifferentiated functionality that impacts your user experience.
PS Of course, where I stand depends on where I sit, but I firmly believe that you should not build an auth system the same way you should not build a database.
Re: Better Auth is joining Vercel
#20Ah, here we go again.
Glad I decided to roll my own auth rather then using some library. I had a feeling that eventually they will join Vercel.