GoKawiilI’m excited to announce that Better Auth is joining Vercel.
From the very beginning, this team has been our biggest inspiration and has always reflected many of the reasons we started working on Better Auth.
Vercel shares our commitment to keeping auth open source, framework and platform agnostic. Joining forces gives us more resources and room to focus on building the framework that much of the community relies on.
Together, we’ll also be able to invest more deeply in where auth is heading: a future where agents act on users’ behalf and need secure, scoped, and revocable access, while bringing these primitives across Vercel’s products.
I’m incredibly grateful to our community, everyone who inspired us in different ways and helped us get here.
Three years ago, I was building an open-source web analytics platform and I needed to add auth. Back then, whenever I started a project with Next.js, I’d reach for NextAuth. Most of the time, all I needed was “sign in with Google” and a simple user object, so it worked great.
But for that project, I needed organizations (multi-tenant): inviting teammates, roles, permissions, proper access control. I looked for something I could pull in and use alongside NextAuth, but nothing really existed. The options were to build it myself or use a third-party auth service.
It took me a couple of weeks to build organizations into the project and refactor everything around it, and I still wasn’t satisfied with the result. Shortly after, I started experimenting with next-org , a wrapper on top of NextAuth that would add organization support and document best practices. I kept hitting walls, the APIs never felt ergonomic, and I eventually gave up midway.
Then I kept running into the same problem everywhere.
I was working on a small Expo app, and adding OAuth with NextAuth felt nearly impossible. And later, I wanted to see if I could move a Next.js project to Svelte, but there was no “NextAuth for Svelte,” so the migration was painful.
... continue reading