Clerk

• CategoryModern hosted SaaS
• LanguageTypeScript
• PricingFreemium
• LicenseProprietary
• Created2019
• GitHub stars1.7k
• HIPAA-eligibleYes (BAA)
• SSO / SAMLOut of box

Clerk is the auth product Next.js teams pick by default in 2026. Pre-built React components for sign-in / sign-up / user profile, organisation primitives, multi-factor, social logins, and the polish that lets you ship a real auth flow in an afternoon. Pricing kicks in at the 10k MAU threshold; below that it is free.

• Next.js / React teams shipping a B2C or B2B product
• Founders who want to delete auth from the engineering backlog
• Multi-tenant products needing organisation + member primitives
• Apps that need polished UI components without designing them

Skip Clerk if your team is committed to owning the user database, Supabase Auth or Better Auth fit that better. Skip if your scale (or pricing model) makes the per-MAU bill unattractive past 100k users.

Clerk is the default for Next.js auth in 2026. The DX is genuinely the best in the category and the time saved is real. The pricing is the trade-off, at scale, the bill matters; below that, the time saved buys it back.

Clerk hands you the parts nobody enjoys building: sign-in and sign-up screens, a user profile surface, session handling wired into middleware, and organisation and member primitives for multi-tenant products. The components are themeable rather than generic, so the result does not look like a template, and the React and Next.js SDKs are clearly where the team invests most. Multi-factor, social providers and session revocation are configuration rather than code. The practical effect is that a two-person team ships a real auth flow, including the account-management screens that usually get postponed for a year, in a single sitting. What you give up is control of the rendering path. The components are Clerk's, and deep customisation eventually means dropping to the headless hooks and rebuilding the pieces you originally skipped, which is worth knowing before you promise anyone a bespoke sign-in experience.

Clerk is freemium and the bill scales with the number of humans who sign in, not with your infrastructure. That model is friendly to early products and unfriendly to consumer apps with large, lightly engaged user bases, which is the single most common reason teams leave. Model it before you build, not after your first surprising invoice. The other cost is migration. User records and session state live with Clerk, so moving to Better Auth or Supabase Auth later is a real project: exporting the directory, getting credentials across without forcing every user to reset a password, and a period where both systems accept logins. None of that is a reason to avoid Clerk. It is a reason to be honest at the start about whether your growth curve makes per-active-user pricing sustainable, because that answer decides this more than any feature comparison will.

• Official homepage →
• GitHub repo →

The 30-min call is where your auth choice becomes a real architecture, a migration plan if you are switching, and a price range you can take to your stakeholders. Describe your stack, your scale, your compliance constraints. I tell you whether Clerk is genuinely your fit.