Documentation
Run, configure, and deploy the standalone Next.js template with Supabase Auth, Postgres, Stripe billing, and template-local tooling.
Start with the working template
This documentation is for the standalone CoreMVP Next.js template. It keeps the UI, an embedded Hono API, server-only services, and customer-facing pages in one deployable application.
Supabase Auth and Postgres, Drizzle repositories, Stripe lifetime and
subscription billing, Docs, Blog, and the template-local ./coremvp tooling are
already wired. Start by running the app locally, then configure the providers
your product needs and publish the managed Vercel path.
Fastest path
Run locally
Install the template, start local Supabase, sync env, and open the app.
Configure the app
Find the app, Supabase, database, Stripe, email, and proof settings.
Deploy to Vercel
Connect hosted providers, deploy the single Next.js app, and verify its URL.
What is already wired
- Authentication — Supabase Auth sessions, email and password flows, and configurable OAuth providers.
- Billing — Stripe Checkout for lifetime and subscription products, webhook handling, and persisted access state.
- Application data — Supabase Postgres with Drizzle models, repositories, and server-only services.
- Product surfaces — Landing, pricing, sign-in, sign-up, dashboard, Docs, and Blog routes ready to customize.
- Template tooling —
./coremvpcommands for env sync, database checks, repair seeds, and focused proof. Provider CLIs own provider projects and deployments.
Choose your next task
Authentication
Understand sessions, protected routes, and OAuth configuration.
Payments
Configure lifetime and subscription billing with Stripe.
Project structure
See where browser, server, provider, and persistence work belongs.
Reference
Find environment variables, API routes, troubleshooting, and the FAQ.
If the local app does not start, check the FAQ or review the environment variable reference.
Was this page helpful?