Aptiq — Production-Ready SaaS API Starter

Every SaaS product repeats the same bootstrap: auth, health checks, a database, and a deploy path. Aptiq packages these decisions into a single template so a new product starts from a tested foundation instead of a blank repo — the auth flow, schema, and deployment topology are all wired before the first feature is written.

A pnpm monorepo with a backend app (Express REST API), a frontend app (React SPA), and shared packages for ESLint config, TypeScript config, and UI components. Docker Compose provisions PostgreSQL; the backend runs Prisma migrations and serves a versioned API under /api/v1.

Prisma schema for users and sessions supporting the JWT auth flow — registration, login, current-user, and refresh token rotation with bcrypt password hashing.

The main challenge was keeping the template general enough to be useful yet concrete enough to be a real starting point — health/readiness endpoints, versioned API paths, and multiple deployment targets without coupling to a specific vendor.

Stateless backend with PostgreSQL allows horizontal scaling from day one. Deployment configs for Render, Railway, and Fly.io each describe API + database topology, and Docker Compose provides a local production-equivalent environment.

Graceful shutdown handling and readiness checks let orchestrators restart or drain the service without dropping traffic.

Health and readiness endpoints for load balancers and orchestrators, plus structured logging wired through the shared config package.

Express over Fastify for ubiquity and familiarity. React + Vite over Next.js for a lighter frontend that stays decoupled from the API. pnpm workspaces over a single package for clean separation.