I built a production-ready Next.js + Firebase SaaS foundation instead of rebuilding the same infrastructure again
I've spent the last few weeks building SaaSStinger Lite, a production-ready SaaS starter focused specifically on developers building with Next.js + Firebase.
The motivation was pretty straightforward: every new SaaS seems to require rebuilding the same foundational pieces before you can work on the actual product.
For SaaSStinger Lite, I wanted those pieces to be structured as a proper application architecture rather than a collection of disconnected starter components.
The architecture
The foundation includes:
Next.js 16 / App Router
React 19
TypeScript
Firebase Authentication
Cloud Firestore
Multi-workspace architecture
Workspace memberships
OWNER / ADMIN / MEMBER RBAC
Invitation system
Audit logs
Usage tracking
Workspace and profile settings
Service-layer architecture
Secure Firestore rules
Production documentation
One of the areas I spent a lot of time on was workspace-scoped authorization.
The goal isn't simply to hide UI elements based on a user's role. Access needs to be enforced throughout the application and reflected in the Firestore security model.
The same applies to invitations and memberships: the application needs to understand the relationship between a user, their membership, their role, and the workspace they're operating in.
Why Firebase?
I specifically wanted SaaSStinger Lite to be useful to developers who prefer Firebase but don't want to rebuild all of this infrastructure themselves.
It's designed to work with the Firebase Spark plan, without relying on Cloud Functions.
That makes the initial infrastructure relatively simple while still giving the application a proper foundation for authentication, persistence, authorization and workspace management.
What I'm trying to solve
The goal isn't to provide another collection of UI components.
It's to get developers past the repetitive infrastructure stage so they can spend their time building the actual SaaS product.
SaaSStinger Lite is now available for $129 as a one-time purchase.
Website: https://saasstinger-website.vercel.app
I'd particularly like feedback from other developers building with Next.js and Firebase:
What's the SaaS infrastructure you find yourself rebuilding every time you start a new project?
The part that stands out is treating workspace authorization as architecture rather than just another starter feature. Auth is easy to copy between projects; getting memberships, roles and Firestore rules to stay consistent is where things usually get messy. Curious which part took the most iteration to make reusable without making the foundation overly opinionated.
Yeah, that was probably the part that took the most iteration. The tricky bit wasn’t the individual RBAC or membership pieces, but making the workspace/membership model, service layer, and Firestore rules line up consistently without forcing too many assumptions on the app built on top of it.
I deliberately kept the foundation opinionated around authorization boundaries, while leaving the actual product/domain logic flexible. That balance took a few iterations to get right.
That balance is probably the hardest part to get right. Have you found any areas where being opinionated in the foundation actually made a later product decision harder?