Frequently Asked Questions

This FAQ answers common questions about SaaSStinger Lite.

Questions are grouped into:

• Product questions
• Development questions
• Firebase questions
• Architecture questions

Product Questions

What is SaaSStinger Lite?

SaaSStinger Lite is a production-ready Next.js and Firebase SaaS starter kit.

It provides the foundation required to build SaaS applications, including:

• Authentication
• Multi-workspace architecture
• Team management
• RBAC permissions
• Audit logging
• Usage tracking

Who is SaaSStinger Lite for?

SaaSStinger Lite is designed for:

• SaaS developers
• Startup founders
• Product teams
• Agencies building SaaS applications

What technology stack does SaaSStinger Lite use?

The main stack includes:

• Next.js
• React
• TypeScript
• Firebase Authentication
• Cloud Firestore
• Tailwind CSS
• shadcn/ui

Does SaaSStinger Lite include a complete SaaS product?

No.

SaaSStinger Lite provides the foundation and architecture.

Developers add their own:

• Business logic
• Product-specific features
• Integrations
• UI customization

Is billing included?

The Lite version does not include a complete billing system.

Billing features can be added by developers or included in future product versions.

Does SaaSStinger Lite include Firebase Storage?

No.

Firebase Storage is not included in the Lite architecture.

Development Questions

Can I customize SaaSStinger Lite?

Yes.

The codebase is designed for extension.

Common customization areas:

src/components/

src/services/

src/actions/

src/server/

src/types/

Can I add new features?

Yes.

Recommended workflow:

Feature Idea

    ↓

Type Definition

    ↓

Server Action

    ↓

Service Logic

    ↓

Repository

    ↓

UI Components

Does SaaSStinger Lite use Server Actions?

Yes.

Server Actions are used as the communication layer between client components and server-side logic.

Does SaaSStinger Lite use a repository pattern?

Yes.

Database operations are separated into repository files.

Example:

src/server/repositories/

This keeps Firestore access isolated from business logic.

Does SaaSStinger Lite use TypeScript?

Yes.

The project is TypeScript-first.

Types are maintained in:

src/types/

src/shared/

Firebase Questions

Does SaaSStinger Lite require Firebase?

Yes.

Firebase provides:

• Authentication
• Firestore database
• Server-side administration

Does it work with the Firebase Spark Plan?

The Lite architecture is designed to remain compatible with Firebase Spark-plan constraints.

It intentionally avoids features that require paid infrastructure, such as background server processes.

Does SaaSStinger Lite use Firebase Cloud Functions?

No.

The Lite architecture avoids Cloud Functions to maintain Spark-plan compatibility.

Does it support Firebase Emulator?

Yes.

The Firebase Emulator is supported for local development and testing.

Authentication Questions

Which authentication providers are supported?

SaaSStinger Lite uses Firebase Authentication.

The enabled providers depend on the Firebase project configuration.

Are users required to create a workspace?

Yes.

The onboarding flow requires users to create a workspace before using the application dashboard.

Workspace Questions

Can users belong to multiple workspaces?

Yes.

The architecture supports multiple workspace memberships.

A user can have different roles in different workspaces.

What workspace roles exist?

Current roles:

OWNER

ADMIN

MEMBER

Can permissions be customized?

The current system uses role-based permissions.

Developers can extend the RBAC system.

Security Questions

Are Firestore rules included?

Yes.

The project includes Firestore security rules.

Are permissions enforced only on the frontend?

No.

Authorization is checked server-side and through Firestore rules.

Are audit logs permanent?

Yes.

Audit logs are designed to be retained and are not user-deletable.

License Questions

Can I use SaaSStinger Lite for commercial projects?

Refer to the license included with your purchase.

Can I redistribute SaaSStinger Lite?

No.

Redistribution rights depend on the license agreement.

Support Questions

Where should I report issues?

When reporting issues include:

• Version
• Operating system
• Node.js version
• Browser
• Error messages
• Steps to reproduce

How should I request help?

Provide enough technical context to reproduce the issue.

Good reports include:

Problem:

Expected result:

Actual result:

Steps to reproduce:

Environment:

Related Documentation

• Installation Guide
• Firebase Setup
• Configuration Reference
• Firestore Schema
• Troubleshooting Guide