Project structure

The repository is a pnpm + Turborepo monorepo.

Apps

apps/web

Public marketing site built with Astro:

• Landing page, pricing, and blog
• Starlight documentation under /docs/*
• Tailwind CSS v4 via the Vite plugin
• Deployed to Vercel as a static site; rewrites /app/* to the Next.js project

apps/app

Authenticated product dashboard built with Next.js:

• Mounted at /app using basePath
• Better Auth for sign-in, sign-up, and social providers
• Stripe billing, Supabase Storage uploads, and protected routes
• Deployed to Vercel as a separate project

Packages

Shared logic lives in packages/:

Package	Purpose
@repo/config	Typed environment variables
@repo/db	Drizzle schema and queries (Postgres)
@repo/auth	Better Auth server + client
@repo/email	Resend email helpers
@repo/stripe	Checkout and webhooks
@repo/storage	Supabase Storage signed uploads
@repo/jobs	Vercel Cron handlers + optional BullMQ queues

Infrastructure

• Supabase Postgres — required; stores users, subscriptions, and upload metadata
• Supabase Storage — required for uploads; create an uploads bucket in your project
• Redis.io — optional; enables BullMQ queue workers when REDIS_URL is set
• Cron jobs — run via Vercel Cron in production; use pnpm jobs:worker locally