Soft.xyz is an independent, data-driven platform that compares 232+ developer tools across 69 categories by real metrics — GitHub activity, npm downloads, actual pricing, DX scores, and community sentiment. Unlike pay-to-play review sites, every ranking on Soft.xyz is based on publicly verifiable data pulled from GitHub, npm, and official pricing pages.

How does Soft.xyz collect data?

Soft.xyz pulls data from public APIs including GitHub (stars, forks, commits, open issues, last commit date), npm (weekly download counts), and official pricing pages. Community sentiment data comes from Reddit and Hacker News mention tracking. All metrics are refreshed weekly and timestamped so you can see exactly when data was last updated.

Is Soft.xyz free to use?

Yes, Soft.xyz is completely free to use. All tool pages, comparisons, benchmarks, DX scores, pricing analysis, and category rankings are available at no cost. For teams that need a deeper analysis, we offer a paid Stack Audit report ($199) that evaluates your entire tech stack with personalized recommendations. An API is also available for programmatic access to our dataset.

How many tools does Soft.xyz track?

Soft.xyz tracks 232 developer tools across 69 categories including databases, hosting, authentication, payments, analytics, CI/CD, monitoring, search, CMS, and more. Each tool page includes real-time GitHub metrics, npm download counts, pricing breakdowns, and side-by-side comparisons with alternatives in the same category.

Home / Migrations / NextAuth.js v4 → Auth.js v5 (next-auth v5)

NextAuth.js v4 → Auth.js v5 (next-auth v5)

medium

Auth.js v5 is a ground-up rewrite of NextAuth v4. Framework-agnostic, App Router native, Edge-compatible. The API surface changed significantly but migration guides are thorough.

Estimated: 3-8h · 5 steps

Progress0%

Step 1: Update package

npm install next-auth@beta

Step 2: Create auth.ts

Move [...nextauth] route config to a top-level auth.ts file. Export { handlers, auth, signIn, signOut }.

import NextAuth from 'next-auth'
export const { handlers, auth, signIn, signOut } = NextAuth({ providers: [...] })

Step 3: Update route handler

Replace pages/api/auth/[...nextauth].ts with app/api/auth/[...nextauth]/route.ts using the handlers export.

import { handlers } from '@/auth'
export const { GET, POST } = handlers

Step 4: Update session access

getServerSession(authOptions) → auth() from your auth.ts. useSession hook still works in Client Components.

Step 5: Migrate callbacks

session/jwt callback signatures updated. User object shape changed — check adapter docs.

✓ Sign in, sign out, session access all work in both Client and Server Components

What this migration involves

Moving from NextAuth.js v4 to Auth.js v5 (next-auth v5) is rated medium and takes about 3-8h on a typical project. The guide breaks it into 5 steps, 3 of which ship with runnable commands and 1 with a verification check.

Related migrations

Auth0 → Clerk — easy, 2-4h Auth0 → Better Auth — medium, 4-8h Clerk → Better Auth — medium, 4-8h NextAuth.js v4 → Auth.js v5 — medium, 2-4h Firebase Auth → Supabase Auth — medium, 4-8h NextAuth.js / Auth.js → Better Auth — medium, 3-6h

FAQ

How long does migrating from NextAuth.js v4 to Auth.js v5 (next-auth v5) take?

Around 3-8h for a typical project — 5 steps, difficulty rated medium, 3 of them with copy-paste commands.

Is moving from NextAuth.js v4 to Auth.js v5 (next-auth v5) reversible?

No reverse guide is tracked yet, so treat this as a one-way move and keep a full export of your NextAuth.js v4 data before you start.

What does Auth.js v5 (next-auth v5) cost compared to NextAuth.js v4?

Pricing for both tools is contact-based or not tracked yet.