Next SaaS Template

Start here

New developers should follow the onboarding path in order. It takes the application from a clean checkout to a verified product change and optional Stripe sandbox subscription.

1. Understand the template
2. Run it locally
3. Tour the project
4. Customize the product
5. Add a metered feature
6. Connect Stripe sandbox
7. Verify and ship

Reference documentation

The remaining documentation is organized by task and can be read independently:

• Concepts — architecture, organizations and tenancy, plans and entitlements, usage and quotas, and background processing.
• Features — billing and subscriptions, plans, pricing, and trials, coupons, organizations and members, API keys, file storage, usage analytics, notifications, audit logs, data lifecycle, and the Operations Center and support workflows.
• Development — recipe index, ServiceStack APIs, feature gates, meters and quotas, background jobs, database migrations, frontend pages, typed DTO generation, testing, and AI-assisted development.
• Operations — runbook index, configuration, secrets, deployment, database and storage, observability and health, background jobs and recovery, external services, retention and lifecycle, backup and restore, and troubleshooting.
• Security — security index, authentication and accounts, authorization and roles, tenant isolation, API credentials and abuse controls, Stripe webhook security, support access, data protection and privacy, web and input security, and the production security review.

The planned onboarding, concept, feature, development, operations, and security documentation sets are now present. Existing root-level documents remain available as compatibility entry points where material has moved into this structure.

Documentation conventions

• Paths are relative to the repository root unless stated otherwise.
• Workspace is the internal code and database term; the product UI calls it an Organization.
• C# request and response types in MyApp.ServiceModel are authoritative. MyApp.Client/lib/dtos.ts is generated.
• Configuration keys use JSON notation in prose, such as Saas.EnableTrials, and double underscores in environment variables, such as Saas__EnableTrials.
• Commands assume a Bash-compatible shell on Linux or macOS. Equivalent PowerShell commands can be used on Windows.

Quick command index

# Run locally
cd MyApp
dotnet watch

# Diagnose local configuration
./scripts/doctor.sh

# Recreate development state
ASPNETCORE_ENVIRONMENT=Development ./scripts/reset-dev.sh --yes

# Run every validation gate
./scripts/verify.sh

# Check production configuration and run verification
./scripts/preflight.sh

Useful application surfaces: