Understand and adapt Sushi SaaS
See what the starter chooses, why it chooses it, which alternatives fit, and what to keep, change, or remove for your product.
What Sushi SaaS Is
What the starter includes, which product decisions it makes, and how to decide whether to adopt all or part of it.
When Sushi SaaS Is a Good Fit
Evaluate the starter by the decisions you can keep, the systems you are willing to operate, and the work your product still requires.
How Sushi SaaS Is Structured
Understand the starter's enforced layers, the choices behind them, and how to add a feature without creating a second architecture.
Why One Five-Credit Task Tests the Whole SaaS
See why Sushi SaaS uses a deliberately simple image provider to prove the difficult connections between identity, credits, jobs, storage, operations, and recovery.
How Sushi SaaS Authentication Works
Follow the shipped sign-in journey, then decide which providers, verification, MFA, tenancy, and abuse controls your product should keep.
How Sushi SaaS Routes Requests
See what the middleware does for users and operators, why organization selection stays visible in the URL, and which routing choices you can change.
Should You Add a Referral Program?
Decide whether you need referral attribution, cash commissions, or credits before enabling the starter's first-touch tracking.