12-hour beta launch console

Single-product SaaS for ideas, job specs, handoff, and POD-ready case workflows.

One Next.js app. One Postgres database. Membership tiers with credits. User-owned Printify connections. Server-side billing, provider calls, and AI usage only.

Create beta accountOpen dashboard
Fastest route to livePrivacy-consciousPrintify-first

Launch defaults

App stack
Next.js 16 + Prisma + Postgres
Billing
PayPal subscriptions + credit packs
POD provider
Printify via user PAT + shop ID
Usage model
Credits included in every membership
Deployment
Docker + Caddy + VPS

Launch MVP

Auth, membership billing, credits, user Printify connection, curated item allowlist, job specs, and prep/export.

Key constraint

Launch with user-supplied Printify token and shop ID. Postpone full OAuth until after beta.

Safe AI path

Ship AI inside the product and charge simple fixed credits per generation. Postpone granular token billing.

Execution order

  1. 1. Configure Postgres, auth secret, PayPal, Printify sync token, and domain env vars.
  2. 2. Push schema, seed plans and packs, run catalog sync, and confirm `/api/health` is green.
  3. 3. Validate signup, login, and admin bootstrap.
  4. 4. Wire membership checkout, webhook reconciliation, and monthly credit posting.
  5. 5. Save and validate user Printify token plus `shop_id`.
  6. 6. Upload artwork and prepare exports for the curated allowlist items.
  7. 7. Use credits for AI idea and job spec generation.
  8. 8. Deploy to the VPS, point DNS, enable TLS, test webhooks, then open beta.

Repo map

  • prisma/ data model, plans, device seed data
  • src/auth.ts Auth.js credentials setup
  • src/lib/ billing, provider, entitlements, env helpers
  • src/app/api/ health, billing, webhooks, provider endpoints
  • scripts/ admin bootstrap and daily Printify sync
  • docs/launch-blueprint.md launch decisions and 12-hour runbook
  • Dockerfile and docker-compose.yml VPS deployment baseline