Installation

• Node.js 18 or newer
• npm
• PostgreSQL database
• Supabase project
• Optional integrations like Stripe, Paddle, Lemon Squeezy, Resend, Upstash Redis, PostHog, and Sentry

The parent project build script already runs prisma generate, and postinstall also runs Prisma generate automatically.

npm install

Use .env.example as the base, then add the extra variables documented by the project for payments, Redis, analytics, monitoring, and AI.

Start with the minimum set: app URL, database, and Supabase.

NEXT_PUBLIC_APP_ENV=development
NODE_ENV=development
NEXT_PUBLIC_APP_URL=http://localhost:3000
DATABASE_URL=
DIRECT_URL=
NEXT_PUBLIC_SUPABASE_URL=
NEXT_PUBLIC_SUPABASE_ANON_KEY=
SUPABASE_SERVICE_ROLE_KEY=

This creates the tables for profiles, organizations, memberships, blog posts, projects, emails, chats, subscriptions, and organization subscriptions.

npx prisma generate
npx prisma migrate dev

1. Create a Supabase project.
2. Add your local and production redirect URLs.
3. Copy NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, and SUPABASE_SERVICE_ROLE_KEY.
4. Make sure the authenticated app can resolve the same user IDs used by Prisma profiles.

npm run dev

• Open http://localhost:3000 and confirm it redirects to /landing.
• Visit /auth/login/simple and /auth/signup/simple.

1. Open /landing.
2. Create an account.
3. Log in.
4. Create an organization.
5. Open /pricing.
6. Visit /members.
7. Confirm protected routes redirect correctly when logged out.

This order matches the safest rollout path because it keeps failures isolated and easy to debug.

1. Resend
2. Redis
3. One payment provider
4. PostHog
5. Sentry
6. AI providers