Billing with a paper trail
Idempotent payment handling, append-only credits, and replay-safe refunds keep financial effects traceable.
Inspect the implementationOpen source. Yours to build on.
Your next SaaS, with a head start.
A Next.js starter that connects accounts, team billing, usage credits, and background work. Start small. Make the product yours.
- Free under MIT
- Your code, your data
- Five languages
Inside the starterSushi SaaS
A clear view of every credit.Actual English application · Sample data
Built on tools you already know
- Next.js
- TypeScript
- Better Auth
- Stripe
- PostgreSQL
- Drizzle
Take a closer look
The product already has a foundation.
Explore the real screens your customers and operators will use. Bring your own brand, workflow, and business model.
Every credit has a story.
Give customers a clear history of grants, usage, and refunds. Keep one traceable ledger behind the balance.
Actual starter screens in English, populated with sample data. This is a read-only preview.
Confidence you can inspect
The details matter after launch.
Follow the source and tests behind the claims. These are the systems that keep working when a request repeats or a job is interrupted.
Work that can recover
Durable jobs, bounded retries, and cancellation checks preserve progress beyond a browser request.
Inspect the implementationClear ownership boundaries
Workspace-scoped authorization and private file access keep customer resources in their own context.
Inspect the implementationA smaller first step
Start with what you need.
Choose your local setup. Add the admin console and publishing tools when your project calls for them.
git clone https://github.com/PansaLegrand/sushi-saas-template.git
cd sushi-saas-template
git switch -c my-saas e63276252e4b64566229cb87225afc72da6991de
export SAAS_STARTER_PROFILE=core
pnpm starter core install
pnpm starter core setup
pnpm starter core doctor
pnpm starter core demoNode 24.22.1+ (24.x), pnpm 10.22.0, and Docker.
Open the full Quick StartCode is free. Hosting and any external services you enable have their own costs.One connected reference
Follow a request all the way through.
Run the local image example to see the pieces work together. The demo provider is a placeholder; the surrounding workflow is real.
Trace the image workflow- 01
Check access
Resolve the customer, workspace, capability, and quota.
- 02
Reserve once
Record the task, credit spend, and durable dispatch together.
- 03
Do the work
Process the job and make the private result available.
- 04
Recover safely
Retry with stable identity or compensate a terminal failure.
Built with Sushi SaaS
From a starter to DojoClip.
DojoClip brings video, image, music, and voice workflows together. See which foundations carry over and where a real product adds its own experience.
Read the case studyCan I use this for a commercial product?
Yes. The starter is open source under the MIT License. You can adapt it for commercial products; keep the required license notice. Hosting and third-party services are separate.
Do I need every application?
No. Core runs the customer app and worker. Operations adds admin, and Publishing adds Content Studio. Profiles choose local tools and build targets; they do not change plan entitlements.
Does it include a working AI provider?
The local image and video examples use mock providers and stay disabled in production. Add your provider, product rules, and validation while keeping the billing, storage, and recovery contracts.
What do I still need before launch?
Your product workflow, identity, pricing, provider accounts, reviewed legal policies, and deployment configuration. The launch and upgrade guides explain the checks and operational responsibilities.
Your next commit starts here
Make it your own.
Start with Core, explore the code, and build the part that makes your product different.
MIT licensed · Free to use and extend