This boilerplate provides a comprehensive, opinionated stack for building Software-as-a-Service (SaaS) products, targeting developers who want to accelerate their SaaS development lifecycle. It offers pre-built features for user authentication, team management, payments, and more, allowing focus on unique product differentiation.

How It Works

The architecture separates concerns into a user-facing Next.js/Express frontend (app) and a server-only Express API backend (api). It leverages React with Material-UI for the UI, MobX for state management, and Mongoose with MongoDB for data persistence. Key features include server-side rendering, WebSocket communication via Socket.IO, and integrations with AWS SES/S3 for email and file storage, and Stripe for subscriptions.

Quick Start & Requirements

• API: Navigate to api/, run yarn install, then yarn dev. Requires a .env file with MongoDB URL, AWS credentials, Google OAuth keys, Mailchimp API key, and Stripe keys.
• App: Navigate to app/, run yarn install, then yarn dev. Requires a .env file for Stripe publishable keys and AWS S3 buckets.
• Dependencies: Node.js, Yarn, MongoDB, AWS account (SES, S3), Google Cloud Platform account, Mailchimp account, Stripe account.
• Setup: Estimated setup time depends on configuring external services.
• Docs: https://builderbook.org/book

Highlighted Details

• Full-stack TypeScript development.
• User authentication via Google OAuth and passwordless options.
• Team creation, invitations, and management features.
• Stripe integration for subscription billing and webhook handling.
• File uploads to AWS S3 with pre-signed URLs.
• Transactional emails via AWS SES.

Maintenance & Community

• Developed by Async Labs.
• Contact: team@async-labs.com
• Projects built with this boilerplate are showcased in the README.

Licensing & Compatibility

• MIT License. Permissive for commercial use and integration into closed-source projects.

Limitations & Caveats

The project relies heavily on external services (AWS, Google, Mailchimp, Stripe), requiring significant configuration and potential costs. The opinionated architecture may require adaptation for different technology preferences.