Deployment
Publish the standalone Next.js template with Vercel, Supabase, and Stripe, or choose an advanced self-hosted path.
Deploy the standalone app
The managed path is one Next.js application on Vercel with Supabase Auth and Postgres plus Stripe Checkout and webhooks. Start here after the template runs locally. Docker and VPS deployment remain available when you want to own more infrastructure.
Vercel
Recommended: connect hosted providers, deploy the app, and verify the exact URL.
Docker
Build and run the application as a container.
VPS
Operate the application, proxy, TLS, and updates on your own server.
Before you deploy
- Finish Getting Started and confirm the app runs locally.
- Review Configuration so browser-safe and server-only values stay separate.
- Prepare hosted Supabase, Vercel, and Stripe access for the provider steps you intend to enable.
- Keep Stripe in test mode until checkout, webhook delivery, persisted access, and the hosted URL work together.
Managed deployment path
- Create or link the hosted Supabase project and apply the included migrations.
- Save the deployed Site URL and Redirect URLs in Supabase Auth configuration.
- Link the Vercel project and add the reviewed Production environment values with Vercel CLI or Dashboard.
- Configure the Stripe test catalog and webhook endpoint used by the deployed app.
- Deploy the app and verify the exact production URL before switching provider state to live mode.
Follow the complete Vercel deployment guide for the commands, provider checkpoints, and hosted verification path.
Runtime ownership
| Surface | Default owner |
|---|---|
| Next.js pages, embedded Hono API, and server services | Vercel project |
| Authentication and Postgres | Supabase project |
| Checkout, customer portal, and billing events | Stripe account |
| Provider projects, environment values, and deployment | Provider CLI or Dashboard |
| App database checks and hosted proof | Template-local ./coremvp CLI |
Advanced self-hosting
Choose Docker or VPS when you want direct control over the application runtime. Those paths require you to own container operation, networking, TLS, updates, monitoring, and recovery.
Was this page helpful?