From purchase to production

A typical path for teams buying AI Starter. Adjust timelines to your team size and compliance needs.

Phase 0 — Evaluate (before purchase)

You do not need your own Supabase project for Phase 0 — the hosted demo uses Oequ’s shared cloud project.

Phase 1 — First run (day 1)

Goal: Clone and run something on a laptop.

git clone <your-licensed-repo>
cd ai-saas-starter
npm install
npx nx serve demo          # fastest: mock backend
# or
npm run db:start && npm run db:reset && npm run start:web

Follow Quick start and Local setup.

Exit criteria: You can sign in, open a board, and trigger a generation (mock or local fal).

Phase 2 — Your Supabase project (week 1)

Goal: Own data in a cloud or staging project.

1. Create a Supabase project (or use local Docker for longer)
2. npm run db:push — apply migrations
3. Deploy Edge Functions and set secrets (RESEND, FAL, STRIPE, …)
4. Point apps/web at your project URL and publishable key

Use npx supabase login → npx supabase link → npm run db:push, then deploy Edge Functions and set secrets in the Supabase dashboard.

Exit criteria: apps/web talks to your project; RLS enforced; one real generation end-to-end.

Phase 3 — Billing & branding (week 2–3)

Goal: Money path matches your market.

Exit criteria: Test checkout upgrades plan; credits allowance updates; webhook idempotency verified.

Phase 4 — Production hardening (week 3–4)

Goal: Safe to expose paying customers.

• Work through Production hardening
• Configure CORS, secrets rotation, cron jobs (credit reset, stale job reaper)
• E2E smoke on staging: npm run e2e:web (from monorepo)

Exit criteria: Staging matches prod config; monitoring on Edge logs and Postgres.

Phase 5 — Your product layer (ongoing)

AI Starter is the platform, not the GTM product.

Keep platform merges from upstream ai-saas-starter separate from your product fork strategy — see Philosophy & layers.

Where to get help

Next

• Quick start — hands-on tutorial
• Commands — full CLI reference