How saas-starter-kit/saas-starter-kit-pro works
Project type and purpose
• This is a full-stack SaaS template comprising:
• A React/Next.js client (“client” folder)
• A Node.js/Express API server (“server” folder)
• AWS infrastructure defined via CDK for CI/CD, an ECS Fargate service, and serverless Lambdas (“infrastructure” folder)
• Machine-learning experiments kept separately (“machine learning” folder)
• The client delivers marketing, auth, purchase and application UIs. The server exposes REST endpoints, handles business logic, data persistence (Mongo and SQL), email notifications, Stripe operations, permissions, and integrates Firebase/Sentry.
File structure
• Top-level separation: client | server | infrastructure | machine learning
• Frontend follows Next.js conventions: pages, components, screens, services, store (Redux), hooks, styles
• Backend is Express-based: routing under src/API, business logic in src/Services, data models in src/Model (mongo and sql), middleware, and configuration modules (stripe, email, firebase, permissions)
• Infrastructure uses AWS CDK to define three distinct stacks:
• AWS CICD Pipeline (build and deploy)
• AWS Fargate API Server (ECS, RDS, VPC, IAM roles, secrets)
• AWS Lambda serverless CRUD functions
• Configuration files present for Docker, Babel, environment variables, Prettier, Jest, CDK, etc.
README
• The readme simply points to a new maintained SaaS template. However, folder names and configs reveal the intended architecture: a scalable, containerized API behind CI/CD, plus an optional serverless layer and ML experiments.
Essential details
• Runtime dependencies (databases, caches if any, external APIs)
• Environment/secret management (AWS Secrets Manager or Parameter Store)
• Don’t forget monitoring/tracing: Sentry and any CloudWatch metrics
• Machine-learning folder separately as an offline or research component not in the production data flow