Introduction
Learn what the SaaS Boilerplate includes and how to turn it into your product.
SaaS Boilerplate is a source-owned TypeScript foundation for building and operating a production-ready SaaS. It gives you a real application architecture—not a collection of disconnected snippets—so you can focus on your product domain.
Start here
Tech stack
See what powers the browser, API, data, and operations.
Set up locally
Run the complete stack with no third-party keys.
Configure safely
Assign environment and provider settings to the right owner.
Build your first feature
Follow the contract-to-UI path for a new domain.
Go to production
Prepare deployment, providers, and verification.
How the parts connect
What you get
- A React web app, Bun + Hono API, PostgreSQL, and shared Zod contracts.
- Better Auth with password, magic-link, and optional Google sign-in.
- Billing adapters for Polar, Stripe, and Dodo Payments.
- Transactional email, R2/S3/GCS uploads, notifications, error monitoring, and PWA support.
- Source-owned migrations, test coverage, operational runbooks, and optional agent skills.
The boilerplate starts usable with only Postgres. External providers are optional in local development and become available when configured completely.
See Included product surfaces for every shipped browser route and Notifications and marketing endpoints for the communication paths.
A product foundation, not a complete business
The generated product includes the authenticated application and its operational boundaries. You supply the product domain, marketing and legal surfaces, commercial policy, analytics choice, and any organization or background-work model. See Product scope.
Designed for a clean first run
Password authentication, verification, password reset, and magic-link sign-in work locally without third-party API keys. Provider-backed capabilities become available when their complete configuration is present.
How to use these docs
Read the setup guide first, then the tech stack, project structure, and included product surfaces. The feature and web UI guides explain what is already built; optional golden paths and agent skills provide maintained ways to extend it. The architecture and verification requirements apply regardless of the workflow you choose.
Common questions
Yes. Polar, Stripe, and Dodo Payments are supported behind one normalized billing contract. Select exactly one provider per deployment and configure it completely.
No. The product is a React 19 SPA built with Vite+. Next.js powers only this separate documentation site.
Create a dedicated domain with contracts, routes, service policy, repository, UI module, and tests. The first-feature guide walks through that shape.
Use Go live to order product, provider, deployment, backup, and browser proof. Deployment remains the detailed infrastructure guide.