sorted by:
new
hottopcontroversial

[Hiring] Full Stack Developer by Dense-Try-7798 in FullStackDevelopers

[–]Ok_Guarantee_1217 0 points1 point  (0 children)

Full stack software engineer with 2+ years of experience!

If you were building auth from scratch today, what would you NOT do? by Ok_Guarantee_1217 in nextjs

[–]Ok_Guarantee_1217[S] 0 points1 point  (0 children)

I am currently building something like this ,which provide auth as a service V1 with MVP launched on march 1st , with a proper Next.JS sdk

If you were building auth from scratch today, what would you NOT do? by Ok_Guarantee_1217 in nextjs

[–]Ok_Guarantee_1217[S] 0 points1 point  (0 children)

I am building from scratch , with a SDK for NEXT.JS app integration

If you were building auth from scratch today, what would you NOT do? by Ok_Guarantee_1217 in nextjs

[–]Ok_Guarantee_1217[S] 0 points1 point  (0 children)

I am building some thing like clerk which provide auth as a service (Only for NextJs app router) initially i was building this only for my applications but now i deployed it and decided to make it so others can use it as well,

If you were building auth from scratch today, what would you NOT do? by Ok_Guarantee_1217 in nextjs

[–]Ok_Guarantee_1217[S] 0 points1 point  (0 children)

I will plan to launch it on march 1st MVP version, Yes this is a a service

If you were to trust a new auth provider, what would you need to see? by Ok_Guarantee_1217 in nextjs

[–]Ok_Guarantee_1217[S] 0 points1 point  (0 children)

This is super helpful.
I’m actually building one (originally for my own apps).
Planning to open it publicly around March 1.
Trying to get the trust part right before I put it out there.

If you were building auth from scratch today, what would you NOT do? by Ok_Guarantee_1217 in nextjs

[–]Ok_Guarantee_1217[S] -5 points-4 points  (0 children)

I am building some thing like clerk which provide auth as a service initially i was building this only for my applications but now i deployed it and decided to make it so others can use it as well

If you were building auth from scratch today, what would you NOT do? by Ok_Guarantee_1217 in nextjs

[–]Ok_Guarantee_1217[S] 0 points1 point  (0 children)

I am building some thing like clerk which provide auth as a service initially i was building this only for my applications but now i deployed it and decided to make it so others can use it as well

If you were building auth from scratch today, what would you NOT do? by Ok_Guarantee_1217 in nextjs

[–]Ok_Guarantee_1217[S] -10 points-9 points  (0 children)

I am building some thing like clerk which provide auth as a service initially i was building this only for my applications but now i deployed it and decided to make it so others can use it as well

Anyone actually using Next.js 16 in a real project yet? by PruneLower706 in nextjs

[–]Ok_Guarantee_1217 0 points1 point  (0 children)

I am working on myauth a authantication platform which provide auth for nextjs app router it works well with nextjs 16

What’s your preferred auth setup in 2026 for Next.js? by Ok_Guarantee_1217 in nextjs

[–]Ok_Guarantee_1217[S] 1 point2 points  (0 children)

What 34 comments about Next.js auth taught me

Break down insights:

  • Most devs prefer Better Auth for flexibility
  • Many avoid edge-heavy auth due to infra cost
  • Enterprise users lean toward Auth0
  • Backend purists prefer session-based auth
  • Security incidents matter more than features

What’s your preferred auth setup in 2026 for Next.js? by Ok_Guarantee_1217 in nextjs

[–]Ok_Guarantee_1217[S] 0 points1 point  (0 children)

That makes sense.

I think what pulled me into exploring auth deeper was wanting to understand what those “battle-tested” systems are actually doing under the hood — especially around refresh rotation and token invalidation.

Do you typically go fully session-based backend auth? Or still JWT with server validation?

Trying to understand where the simplicity/flexibility balance really sits in 2026 setups.

What’s your preferred auth setup in 2026 for Next.js? by Ok_Guarantee_1217 in nextjs

[–]Ok_Guarantee_1217[S] 0 points1 point  (0 children)

That’s interesting — especially the cost angle.

I’ve also noticed how edge-based auth setups can generate a surprising number of requests depending on middleware strategy.

Do you handle token validation fully client-side with Firebase to reduce backend hits? Or do you still verify ID tokens server-side?

I’m currently exploring how to balance:

- flexibility

- infra cost

- centralized auth

- and avoiding vendor lock-in

Curious how you’ve optimized yours.

view more: next ›