Most starter kits are sold on a README promise. A list of green checkmarks, a slick landing page, and the quiet assumption that you'll never actually audit the code before your card gets charged.
I didn't trust my own kit enough to do that. So before I put a price on it, I sat down and reviewed NuxtForge the way a skeptical buyer would: fresh clone, README only, no mercy, no memory of having written any of it.
It did not all pass. This is what broke, what I fixed, and what's actually tested now — because a kit that hides its history will hide its bugs.
What it is, in one paragraph
NuxtForge is a decoupled Nuxt 4 + NestJS 11 SaaS foundation in TypeScript. Not a monolith — a real API (NestJS, Prisma 6, PostgreSQL 17, Redis, BullMQ, S3/MinIO, Stripe, Resend) and a separate SSR frontend (Nuxt 4) behind Nginx, all wired together with Docker Compose. The idea is boring on purpose: give you the undifferentiated plumbing every SaaS rebuilds from scratch — auth, tenant isolation, config, billing hooks, an admin shell — already built and tested, so you start on your product instead of on npm init.
