Recipes

The cookbooks swap pieces out. These recipes do the opposite: they build on what already ships. Each one is a complete walkthrough of a feature real SaaS products need, written the same way the rest of the codebase is, so what you add reads like what was already there.

Start with the vertical slice

If this is your first addition, read Add a feature first. It lays out the house pattern, a Zod model, a four-part API route and a test, that every other recipe assumes.

Billing beyond one seat

Single-subscriber checkout ships by default. Team and seat billing covers per-seat quantities, so an account can pay for a whole team.

User content

File uploads uses Supabase Storage for avatars and attachments, including the access rules that keep one tenant out of another's files.

Hardening the account

Two-factor auth adds TOTP on top of NextAuth, the authenticator-app flow users expect from a product that holds their data. See the security model for what is already enforced without you doing anything.

Async work

Webhooks and background jobs covers receiving your own signed webhooks and moving slow work off the request path with a queue or a cron.

All recipes

Add a featureBuild a vertical slice the house way.Team / seat billingPer-seat subscriptions.File uploadsUploads with Supabase Storage.Two-factor auth (2FA)TOTP on top of NextAuth.Webhooks & background jobsYour own webhooks and async work.

Want to replace a provider instead of building on it? The cookbooks cover every swap.