All articles
Tools2 min read

Better Auth, Auth.js or Clerk: what I pick for a Next.js app

Three ways to handle sign-in in Next.js, and the one I reach for. A short version of the full comparison on my blog, Le Dev Augmenté.

by Vidhal Elame

Every product I launch starts with the same question: who handles the accounts? I published a full comparison on my blog, Le Dev Augmenté. Here is the short version, with what I take from it for my own projects.

The verdict in one sentence

Better Auth for a Next.js project that wants to keep its accounts in its own database, without paying per user. Clerk for a team that wants ready-made screens and managed compliance. Auth.js for an app that already uses it, or for a session with no database.

What makes the difference

  • Where your users live. With Better Auth and Auth.js, accounts are in your database: PostgreSQL, MySQL or SQLite. With Clerk, they are at Clerk. That is comfortable at first, and it is what makes leaving harder later.
  • What it costs when it works. Better Auth is a free framework under the MIT licence. Clerk is free up to 50,000 users per application, then $25 a month for the Pro plan. B2B team features are an add-on.
  • The screens. Clerk ships the sign-in pages ready-made. With the other two, you build the interface yourself.
  • The future of Auth.js. The project came under Better Auth's care in September 2025, and its documentation recommends Better Auth for new projects.

These prices were noted on 6 November 2026 from the official pages. They move often: check before committing for a year.

What I pick, and why

My latest products run on Better Auth. The reason fits in one line: I want the users table in my database, next to everything else. One backup, one source of truth, and no bill that climbs with the number of sign-ups.

The price is real: you build the sign-in and sign-up screens yourself. For someone who already designs their own interfaces, that is not a cost. For a team in a hurry to ship a prototype, Clerk saves days.

Three questions to ask

  1. Do I want to be able to export my users tomorrow, without asking anyone?
  2. Do I have time to make my own sign-in screens?
  3. At how many users does the bill become a topic?

If you answer yes, yes and "very soon", take a solution that keeps the accounts with you.

Read the full comparison

The full table, criterion by criterion, with the limits of each offer and the sources, is on Le Dev Augmenté (in French): Better Auth, Auth.js ou Clerk : quelle auth pour Next.js en 2026 ?