Skip the repetitive plumbing that consumes weeks of a SaaS MVP launch. This starter kit gives you a ready‑to‑run Next.js codebase with authentication, billing, UI components, and a basic dashboard already wired together, so you can start adding your product’s unique features immediately.
What You Get
- auth/ – NextAuth configured with email and OAuth providers, no additional setup required.
- billing/ – Integrated Stripe support handling subscriptions, invoice generation, and a customer portal.
- components/ui/ – Over 100 local shadcn/ui components, organized to avoid scaffolding conflicts and ready for customization.
- dashboard/ – Basic user dashboard that connects authentication state with billing information and navigation.
- pages/marketing/ – Pre‑built landing, pricing, and sign‑up pages that follow a typical SaaS layout.
- config/ – Environment files and production‑ready Next.js configuration tuned for deployment.
How to Use
- Clone the repository and run
npm install (or yarn) to install dependencies.
- Copy the example
.env.example to .env.local and fill in your NextAuth and Stripe credentials.
- Run
npm run dev to launch the development server; the auth routes, billing endpoints, and dashboard will be operational out of the box.
- Replace the placeholder content in
pages/marketing with your own copy and branding.
- Extend or replace UI components from
components/ui as needed; the library is fully local, so you can edit without triggering CLI conflicts.
- When ready, build with
npm run build and deploy to your preferred host; the provided config files include sensible defaults for production.
Who This Is For
- Developers who need a functional SaaS foundation quickly and prefer to avoid manual setup of authentication and payment processing.
- Teams building MVPs that want a consistent UI layer based on shadcn/ui without recreating components for each project.
- Engineers looking for a clear, production‑ready example of NextAuth and Stripe integration within a Next.js application.
- Anyone who wants to focus on core product features rather than spending time resolving CLI or configuration conflicts.