Launching today
StackPatch
Patch authentication into your Next.js app with one command
76 followers
Patch authentication into your Next.js app with one command
76 followers
StackPatch is a CLI that patches production-ready authentication into Next.js projects. Run one command and get Google & GitHub auth, protected routes, and session handling all as real files inside your repo. -No SaaS -No lock-in -Fully open source.
StackPatch
@darshitdev This is such a clean idea — auth isn’t “hard”, it’s just painfully repetitive.
I love that StackPatch ships real, editable files into the repo (no SaaS, no lock-in, no magic runtime), so teams fully own the code from day one. That’s the kind of DX that actually fits production work.
Congrats on the launch — this feels like it’ll become a default starting point for a lot of Next.js projects 👏
StackPatch
@hijacey hey Jacey Thankyou!! yes going through docs and refactoring the necessary code in the codebase is a pain and then adding oauth takes lot of iteration to make it work so trying to solve this repetitive task and i am bringing this one line command supported for all the framework!
Congrats on the launch! Love how StackPatch patches battle-tested auth into existing Next.js apps with one command—great DX, zero lock-in, and perfect for production-focused teams.
StackPatch
@zeiki_yu Thanks more frameworks and feature coming soon in this open source
@zeiki_yu congrats Zeiki. How do you handle updates and maintenance?
This is awesome — I love that it just patches real files into the codebase.
No magic, no hidden stuff, just code you actually own.
Quick question: do you plan to support Role-Based Access Control in the future, or is the focus staying purely on authentication for now?
Can’t wait to try this on my next Next.js project
StackPatch
@mrpop Thanks a lot really appreciate that 🙂
The core focus is staying authentication-first and composable.
I don’t want StackPatch to turn into a heavy auth framework.
RBAC is something I’m thinking about as an optional patch rather than a default something you add only if you need it and fully own the code.
Would love to hear how you usually handle roles in your projects.
Looks interesting, I feel like there are a couple good use cases for this. I'm wondering how flexible this is, do you have generic way of defining "patches". Could it also work for other domains and apps that are not Next.js? Is it / could it be combined with AI to automatically patch projects?
StackPatch
@wilco_kruijer1 yes currently i am handling use cases for the existing app/project without messing your file structure introducing good design principle and you can revert the changes if something is not up to the mark all the files will be replaced as it is as well as the new project for other domains i am working on it will be out soon! I am not combining this with AI as AI needs lot of iteration to make this work and also AI is not updated with the latest doc changes and it can change file randomly or create new files so lets see
Product Hunt
StackPatch
@curiouskitty Great question!! The hardest cases so far have been projects that already have partial auth setups (custom middleware, existing providers or mixed App Router + legacy patterns). Those are tricky because you’re not starting from a clean slate.
My rule is: StackPatch should never guess intent.
If a pattern can be:
-reliably detected
-patched without overwriting custom logic
-and leave the project in a predictable state
then I support it.
If it requires assumptions (for example: custom auth flows, deeply coupled middleware, or heavily modified folder structures), I intentionally fail fast and mark it as “not supported” rather than silently doing something risky.
The philosophy is: safe defaults > broad coverage. I’d rather support fewer patterns well than many patterns unreliably.
Over time, I’m expanding support based on real-world project structures I see and test against.