Build your SaaS.Start from the foundation.
A focused Next.js foundation designed around account recovery, private data, recurring subscriptions, and the billing edge cases that are expensive to get wrong.
Next.js · TypeScript · Supabase · Stripe · Vercel
Example resources
Current plan
Pro
ActiveCreate and edit your private Example resources. Your access follows the confirmed paid-through period shown below.
Monthly subscription
Paid through Oct 24, 2026
Account
Demo account
demo@example.com
Pricing
Start free. Upgrade when you need it.
One Free plan and one Pro entitlement, billed monthly or annually.
Free
$0
Account, recovery, settings, and retained-data access — designed together.
- Account & recovery
- App shell
- Read retained own Example resources
- Delete retained own Example resources
- Billing upgrade path
Pro
$12 / month
Unlock create and edit access for the replaceable Example Resource.
- Everything in Free
- Create Example resources
- Edit Example resources
- Monthly or annual subscription
- Customer Portal
- Server-derived Pro access
No trial. A browser return never grants Pro; access follows trusted server-side billing state and the confirmed paid-through period.
FAQ
Know what you’re
starting from.
A focused foundation is easier to understand, adapt, and trust.
01What is Supabase SaaS Starter?
A focused Next.js foundation for individual-account subscription products. The Example Resource is deliberately small and replaceable.
02What does the starter cover?
The supported product surface is intentionally closed: public marketing, Google and email/password Auth, private user-owned data, one Free plan, one Pro entitlement, Billing, Account, Help, and the replaceable Example Resource.
03Which authentication methods are supported?
Google OAuth and email/password with verification, resend, and recovery. Magic-link authentication is intentionally not part of the product.
04Why Supabase?
Supabase is the supported identity and Postgres platform. The private-data contract uses user ownership and Postgres row-level security rather than client-side entitlement checks.
05How is Stripe handled?
The commercial model is Free plus one Pro plan, billed monthly or annually, using Checkout and Customer Portal. The billing contract derives Pro access from trusted financial facts and confirmed paid-through semantics.
06Does access depend on the Checkout success page?
No. The supported billing contract never treats a browser return as authority for Pro access.
07Can I replace the Example Resource with my product?
Yes. It is the replaceable boundary for exercising Auth, ownership, RLS, Pro gating, and CRUD together. Replacing it must not require rebuilding Auth, Billing, Account, configuration, or the app shell.
08Does it support teams or organizations?
No. Supabase SaaS Starter deliberately supports individual customer accounts only.
09Is it friendly to coding agents?
Yes. The structure favors few canonical documents, explicit boundaries, generated types, executable tests, and centralized configuration rather than agent-specific frameworks.
10Where does it deploy?
Vercel is the only supported deployment target, with Supabase and Stripe isolated across local, staging, and production environments.