Skip to content
Discussion options

You must be logged in to vote

I think an official starter could be valuable, but I would probably frame it as a reference implementation rather than a single “official SaaS stack.”

Next.js already gives the core building blocks, but a maintained full-stack example would help developers understand how the framework authors expect common production concerns to fit together:

  • authentication and protected routes
  • database access patterns
  • server actions / route handlers
  • RBAC and organizations/teams
  • Stripe subscriptions
  • email flows
  • file uploads
  • background jobs
  • admin or internal dashboard patterns
  • deployment and environment variable setup

The tricky part is avoiding too much provider lock-in. For example, auth, payments, sto…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by Lewis-D13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Help
Labels
None yet
2 participants