Starter stack
Indie SaaS
A lower-operations application stack that favors code ownership, usage-sensitive services, and a Merchant of Record.
Recommendation
A solo developer or very small team shipping a focused paid SaaS product
Assumptions
This stack is useful only while these product and operating assumptions remain true.
- The team can own authentication configuration, schema, upgrades, and incident response.
- A Turso database model fits the workload and deployment topology.
- Lemon Squeezy eligibility and Merchant of Record coverage fit the business.
- Cloudflare is a deliberate deployment and edge-platform choice.
What is in this stack
Each layer has a clear job. Replaceable tools can be swapped when your constraints change.
Next.js
Product UI and application surface · Core choice
Better Auth
Application-operated users, sessions, and authentication flows · Replaceable
Turso
Managed application data platform · Replaceable
Lemon Squeezy
Checkout and covered seller-of-record operations · Replaceable
Resend
Application-triggered email delivery · Replaceable
Cloudflare
Application runtime, delivery, and edge platform · Replaceable
Why these tools fit together
Next.js provides the application; Better Auth keeps identity logic and records closer to the codebase; Turso supplies the database; Lemon Squeezy takes the Merchant of Record route; Resend handles transactional mail; Cloudflare supplies the deployment platform. The combination reduces some fixed operations without pretending the solo developer has no ownership burden.12345679101112131617
When to replace a layer
Change a tool when the underlying constraint changes, not because another logo is more popular.
Authentication
Security operations, account administration, or enterprise identity exceed the team's capacity.
Direction: Move to a reviewed managed identity route.
Database
Relational behavior, write topology, ecosystem requirements, or operations no longer fit Turso.
Direction: Move to a reviewed managed PostgreSQL route.
Commerce
MoR country/product coverage is insufficient or processor ownership becomes preferable.
Direction: Evaluate another MoR or direct processor route.
Hosting
Required Next.js features or long-running workloads do not fit the selected Cloudflare runtime.
Direction: Use a compatible managed host and separate durable work.
Official resources
Use the Stack to decide, then verify implementation and commercial details with each primary source.
Sources
Primary evidence used for the Stack fit and dependency boundaries.
- 1Next.js documentation
Vercel · Accessed Official
- 2Better Auth documentation
Better Auth · Accessed Official
- 3Turso documentation
Turso · Accessed Official
- 4Lemon Squeezy documentation
Lemon Squeezy · Accessed Official
- 5Resend documentation
Resend · Accessed Official
- 6Cloudflare developer documentation
Cloudflare · Accessed Official
- 7Next.js documentation
Vercel · Accessed Official
- 8Next.js license
Vercel · Accessed Official
- 9Better Auth introduction
Better Auth · Accessed Official
- 10Better Auth organization plugin
Better Auth · Accessed Official
- 11Better Auth pricing
Better Auth · Accessed Official
- 12Better Auth repository
Better Auth · Accessed Official
- 13Turso introduction
Turso · Accessed Official
- 14Turso usage and billing
Turso · Accessed Official
- 15Turso plan API
Turso · Accessed Official
- 16Lemon Squeezy payments
Lemon Squeezy · Accessed Official
- 17Lemon Squeezy pricing
Lemon Squeezy · Accessed Official
- 18Resend pricing
Resend · Accessed Official
- 19Workers and platform product pricing
Cloudflare · Accessed Official