Supabase + Stripe + Next.js starter: what you still have to wire
A Next.js Supabase Stripe boilerplate (also searched as “Supabase Stripe starter”) is a repo where auth, Postgres, and subscriptions are already connected, not a blank create-next-app plus two vendor quickstarts. You still write the product. The kit is supposed to stop you from re-explaining OAuth, webhooks, and RLS every new idea.
NextBento is that shape: Next.js 16, Supabase, Stripe, Resend, $59 one-time. Integration overviews: Supabase and Stripe. Step-by-step: Supabase setup and Stripe setup.
What is already wired
After you clone and fill env vars (quick start):
- Supabase Auth: Google and GitHub OAuth, magic link, email/password, session cookies, middleware on dashboard routes, post-signup onboarding gated on
profiles.onboarding_completed. - Postgres + RLS: profiles, subscriptions, teams, API keys. Privileged writes go through API routes and server clients, not the browser.
- Stripe: Checkout for subscriptions, Customer Portal, webhook updating subscription state. Price math stays on the server.
- Teams: owner / admin / member. The owner is the Stripe customer (
subscriptions.user_id). Admins invite. Members use the app. - Resend: transactional email once DNS is verified.
That is the triangle NextBento locked on purpose. You cannot swap Clerk or Lemon Squeezy without rewriting the kit. If those vendors are a hard requirement on day one, this is not that kit.
What you still have to wire (always)
No honest starter ships your product:
- Your domain model, unique tables, and RLS policies for your resources
- Pricing copy, plan names, and Stripe products in the Dashboard (the kit does not invent your SKU)
- Onboarding copy that is not generic
- Marketing pages for your offer (this marketing site is a separate repo; do not copy live compare pages into the cloned kit)
- Anything that is not Supabase / Stripe / Resend (storage product features, i18n, seat billing (not included))
A “Supabase Stripe starter” that claims you will not write backend code is selling a demo.
Typical leftover work (and where docs live)
| Leftover | You do | Docs |
|---|---|---|
| Create the Supabase project and OAuth apps | Dashboard + env | Supabase setup |
| Create Stripe products, webhook, Customer Portal | Dashboard + env | Stripe setup, billing |
| Verify the sending domain | Resend DNS | Resend setup |
| Invite a collaborator | In-app teams | Teams |
| Deploy | Vercel + env | Deploying to Vercel |
Free tiers: Vercel, Supabase, and Resend can host a first app at $0 infra. Stripe fees apply when you charge customers. Confirm current vendor limits on their pricing pages.
When this starter is the wrong kit
If you need organizations / seat billing / i18n / super-admin on day one, NextBento does not ship that. If you need MongoDB or Lemon Squeezy on day one, NextBento does not ship that. If the license must be $0, this is not that kit.
If the stack already matches, get NextBento ($59) or read pricing. The 2026 kit table is on compare.
Related
- Next.js 16 SaaS boilerplate
- Cursor / Claude skills vs a blank repo
- Prompting auth and Stripe from a blank repo
