Authentication
Supabase email/password and OAuth flows remove the session plumbing from your first build.
The hard parts of your product, already wired.
Supabase Auth, Stripe billing, persisted access, documentation, and deployment proof tooling in one application.
Included product surfaces
Authentication
A real account flow.
Sign up, sign in, OAuth, callbacks, and session-aware navigation are connected to Supabase Auth.
Welcome back
Sign in to your account
you@example.com
••••••••
Sign in
Billing
Checkout to durable access.
Stripe Checkout and verified webhooks turn a payment event into persisted product access.
One-timeSubscription
Checkout→Webhook→Access
Dashboard
Product building blocks, ready.
Preview practical dashboard pages composed entirely from shadcn components.
Overview
Cards and chart
Activity
Search and actions
Onboarding
Questionnaire
States
Feedback patterns
Content
Docs and Blog included.
Explain the product, document setup, and publish articles from the same application and content source.
Documentation
Getting started
Authentication
Payments
Deployment
From the Blog
Technical content with real routes and metadata.
Write once, then publish through the source-backed Blog index and article pages.
What you get
A product foundation you can inspect.
Billing
Stripe Checkout, webhooks, and billing state cover both one-time and subscription products.
Database and access
Drizzle migrations persist purchase and subscription truth instead of trusting a redirect or client flag.
Product dashboard
Account, billing status, cards, and tables give the signed-in product a working starting point.
Docs and Blog
Customer documentation and a source-backed Blog are already part of the application shell.
Deployment proof
The included CLI checks local setup, app database readiness, core flows, and hosted application liveness.
Technical proof
Built to prove itself.
The template includes customer-facing commands for setup, local product flows, database checks, and production verification.
project readiness
Setup readiness
./coremvp env syncAuthentication flow
./coremvp e2e authBilling flow
./coremvp e2e billing:lifetimeProduction application
./coremvp prod e2e smoke https://<your-production-domain>Billing demo
Test both ways to sell.
The example plans use Stripe test mode to demonstrate template behavior. They are not CoreMVP product prices.
From the template
Latest from the Blog
FAQ
Before you explore.
What is included in this template?+
A standalone Next.js application with Supabase Auth and Postgres, Drizzle, Stripe billing flows, a dashboard, Docs, Blog, and a project CLI.
Are the prices in the demo CoreMVP prices?+
No. The local pricing pages contain example plans for exercising Stripe test-mode checkout and access behavior.
Does billing support one-time purchases and subscriptions?+
Yes. The template includes separate examples for lifetime access and recurring subscriptions, including verified webhook handling and persisted state.
How do authentication and the database work?+
Supabase owns authentication and Postgres, while Drizzle migrations and application routes keep account and access state connected to the product UI.
Can I customize the product and design?+
Yes. The application is intended to be edited: routes, components, styles, copy, plans, and product logic remain in your codebase.
Is this a hosted service or a code template?+
It is a Next.js code template that you run, customize, and deploy in your own provider accounts.
Can I use my own Supabase project?+
Yes. Connect the template to your Supabase project with its public URL and anon key, then apply the included database setup.
Can I connect my own Stripe account?+
Yes. Add your Stripe keys and approved price IDs to use the included one-time and subscription checkout examples.
Are Google, GitHub, and Apple sign-in supported?+
Yes. The auth screens include all three provider options. Enable the providers in Supabase and configure their callback URLs to use them.
How do I deploy the template?+
Follow the managed Vercel path in the docs, configure the required provider variables, and run the included verification commands before launch.