Getting Started

LaunchKit Pro is a production-oriented AI-ready full-stack SaaS starter kit with mock mode and provider-ready OpenAI/Gemini adapters by LaunchKit Labs. It gives buyers a full-stack foundation — not just UI mockups — so you can ship auth, workspaces, billing, AI, storage, admin, and developer tooling faster.

Who it is for

• Founders launching a B2B or B2C SaaS product
• Agencies building client portals with workspaces and billing
• Developers who want NestJS + Next.js architecture with clear module boundaries
• Marketplace buyers evaluating a deployable starter before customizing

Editions overview

Edition	Focus	Typical use
LaunchKit Lite	UI foundation	Landing pages, auth UI, dashboard shell, themes
LaunchKit Pro	Full-stack SaaS	Auth, workspaces, RBAC, billing, AI, audit, storage, deployment
LaunchKit Enterprise	Scale & white-label	Advanced AI, API keys, feature flags, starter packs, security center

Backend plan codes align with lite, pro, and enterprise.

What is included

Backend

• NestJS API with PostgreSQL (Prisma) and optional Redis queues
• Auth (JWT), protected from redirect, suspended user/workspace enforcement
• Multi-workspace RBAC, invites, branding, feature limits
• Mock billing (Stripe/Lemon adapters), dynamic plan catalog from DB
• Mock AI (OpenAI/Gemini adapters), generation/history/usage
• LOCAL storage (S3/R2/Cloudinary adapters), avatars
• Admin CRUD — users, workspaces, plans, billing settings, overview KPIs
• API keys, outbound webhooks, license system, updates catalog
• Demo-safe mode, search, security (rate limit, CAPTCHA), audit logs, queues foundation

Frontend

• Next.js App Router — dashboard Command Center, workspace insights, admin console
• Dark/light theme with stable accent persistence; toast dismiss buttons
• Profile avatar crop/resize; workspace switcher with suspended/disabled states
• i18n foundation: English and French

Documentation

• This buyer docs site ships in your package — use offline or run locally. Public docs deployment is optional.

Tech stack overview

Layer	Technology
API	NestJS, TypeScript, Prisma
Database	PostgreSQL
Cache / queues (optional)	Redis when QUEUES_ENABLED=true
Frontend	Next.js App Router, TypeScript, shadcn/ui (Radix)
Docs	VitePress (static, packaged)
API docs	Swagger / OpenAPI

---

Quickstart — fastest safe setup (~15 min)

Assumes PostgreSQL is installed and running.

1. Database

CREATE USER launchkit_user WITH PASSWORD 'replace_with_secure_password';
CREATE DATABASE launchkit_app OWNER launchkit_user;

2. Backend

cd backend
npm ci
cp .env.example .env

Set at minimum:

DATABASE_URL=postgresql://launchkit_user:replace_with_secure_password@127.0.0.1:5432/launchkit_app
JWT_ACCESS_SECRET=replace_me_access_secret
JWT_REFRESH_SECRET=replace_me_refresh_secret
APP_URL=http://localhost:4000
FRONTEND_URL=http://localhost:3000
EMAIL_PROVIDER=MOCK
STORAGE_PROVIDER=LOCAL
QUEUES_ENABLED=false
API_DOCS_ENABLED=true

npx prisma generate
npx prisma migrate deploy
npm run start:dev

Use migrate deploy, not migrate dev, for this quickstart.

3. Frontend

cd frontend
npm ci
cp .env.example .env.local

NEXT_PUBLIC_API_URL=http://localhost:4000

npm run dev

4. Verify

• http://localhost:4000/health → OK
• http://localhost:3000 → register → dashboard

Set API_DOCS_ENABLED=false if you do not need Swagger during setup.

---

Buyer-friendly notes

• Mock providers are intentional — connect real Stripe, OpenAI, SMTP, and S3 later using prepared adapters.
• Redis is optional — keep QUEUES_ENABLED=false for the simplest install.
• Docs deployment is optional — read this site from the package or run npm run dev locally.
• Never commit secrets — use placeholders in examples only.

---

Next steps

1. Installation — full install flow and production build order
2. Environment Variables — required backend and frontend vars
3. Database Setup — PostgreSQL, Prisma, pgAdmin, migrations
4. Internationalization — English/French foundation and locale preference
5. Redis & Queues — optional background jobs
6. File Storage & Avatars — uploads, avatars, public URLs
7. Deployment Gotchas — common fresh-install fixes

No secrets in documentation

Use placeholder values in .env examples. Never commit real database passwords, JWT secrets, payment keys, or AI provider keys.