Nick Launches rebuilds backend after reaching 21k users
Nick Launches said the product outgrew its rushed May backend at 21k users and moved to a cleaner NextJS setup using dirstarter, better-auth, and oRPC. Week 11 updates listed 85 live launches and new directory filters, making it a concrete post-MVP refactor case rather than a launch demo.

TL;DR
- Nick Launches reached 21k users after a May launch, and the original backend had been vibe-coded without "proper architecture," according to nicklaunches' refactor post.
- The new stack moved to better-auth, DB sessions, declarative RBAC, oRPC, TanStack Query, Zod, Prisma/Postgres, and Redis-backed rate limits, according to the architecture comparison.
- The cleanup followed real volume: the Week 11 update listed 227 submissions, 85 live launches, 919 upvotes, 247 new builders, and a newsletter send to 1,494 builders.
- The build-vs-buy call was explicit: directories were "a solved problem" with listings, submissions, categories, and SEO pages, as one reply put it.
- Dirstarter became reusable infrastructure: the AI Agents Listing progress post showed AWS SES and GA4 added on top of the same boilerplate.
The Dirstarter authentication docs match Nick's new auth column: BetterAuth, Google login, magic links, one-time tokens, RBAC, and session management. oRPC's homepage matches the API column, with type safety, OpenAPI, TanStack Query integrations, and Server Actions. The public Nick Launches directory page exposes the distribution layer behind the product: directory rows with DR, traffic, and backlink fields.
21k-user refactor
Nick Launches started in May with a backend the maker said was mostly vibe-coded. By the refactor post, the site had reached 21k users and needed "proper development," according to nicklaunches' update.
The sequence is the useful part for vibe-coders: the architecture cleanup followed users, launches, and analytics, rather than preceding them.
New NextJS stack
Nick said the rebuild used Dirstarter and called out better-auth and the oRPC router in the refactor post. The public Dirstarter page sells the boilerplate as a complete Next.js directory template with authentication, an admin panel, Stripe payments, blogging, AI-generated content, and SEO-optimized pages.
Stack changes from the attached comparison:
- Auth: better-auth 1.6 replaced NextAuth v5 beta.
- Sessions: Postgres DB sessions with Redis cache replaced JWT.
- Login: Google, magic link, and OTP claim flow replaced password, GitHub/Google/Twitter, and magic link.
- Authorization: declarative RBAC with wildcard grants, enforced per procedure, replaced an env-var admin allowlist and build-time admin exclusion.
- API: an oRPC router with one definition for RPC, public OpenAPI, and RSC replaced REST route handlers and server actions.
- Client data: TanStack Query with typed oRPC bindings replaced raw
fetch()and form actions. - Validation: Zod on every procedure, feeding OpenAPI docs, replaced manual checks plus Mongoose constraints.
- Database: Prisma 7 and Postgres replaced Mongoose plus the native MongoDB driver.
- Rate limiting:
rate-limiter-flexiblewith Redis and per-procedure config replaced a custom Mongo fixed-window limiter plus BotID.
Dirstarter's project structure docs describe server-side oRPC folders for procedure builders, permissions, roles, context, and routers. Its authentication docs describe BetterAuth with magic links, Google OAuth, role-based access control, session management, and a user management interface.
Dirstarter buy-versus-build math
Nick Launches had asked followers to vote on four designs, then skipped all four and bought Dirstarter Basic, as the Dirstarter decision post showed.
The reasoning was practical:
- Rebuilding submission flows and listing pages cost distribution time, as one reply put it.
- Directories were already solved at the level of listings, submissions, categories, and SEO pages, according to another reply.
- Visitors did not grade products on custom design, a design reply argued.
- Nick Launches had already spent hours implementing features that existed elsewhere, according to a follow-up.
That is the whole post-MVP refactor lesson, stated without romance: custom code lost to distribution speed.
Week 11 launch volume
The refactor followed a week with actual marketplace churn. Nick Launches' Week 11 post said the newsletter went to 1,494 builders and listed:
- 227 products submitted.
- 85 products went live.
- 919 upvotes cast.
- 247 new builders joined.
The linked Week 11 recap added that 18 of the 85 live launches were premium, the directory had reached 2,104 total builders, and the product base had crossed 908 live products.
Launch directory filters
Nick Launches also turned launch distribution into a measured dataset. The directory audit post said he ran the numbers on 158 launch directories and filtered for four things:
- Their own pages rank in Google.
- Listings actually get indexed.
- Links are dofollow.
- A real audience browses the site.
The linked free directory list promised DR, traffic, and dofollow status for each directory. The current public Nick Launches launch-directory page presents 156 directories and includes DR/traffic and backlink columns.
AI Agents Listing
The Dirstarter move also shows up outside the core product. In the AI Agents Listing progress post, Nick said he added AWS SES and GA4 on top of Dirstarter, kept the infrastructure on AWS, and paused the side build while new Nick Launches features came first.
The screenshot already has slots for AI agents, MCP servers, agent skills, ads, search, dark mode, and submissions, with Claude Code, Cursor, Devin, and Lindy as early cards.