Deployment
Deploy Starter Pro with production-ready infrastructure, secure environment management, Stripe billing, authentication, and scalable SaaS delivery practices.
Production-ready deploymentLink to section
Starter Pro is designed to move from local development to production without rebuilding the infrastructure layer.
The deployment model focuses on:
- predictable infrastructure
- secure environment management
- scalable SaaS delivery
- Stripe billing reliability
- protected authentication flows
- production-safe defaults
Core principle
Deployment should accelerate launch confidence, not become another engineering project.
Recommended stackLink to section
Frontend deployment
Database
Authentication
Billing
Deployment architectureLink to section
User
↓
Vercel deployment
↓
Next.js App Router
↓
Auth + Billing + Server actions
↓
PostgreSQL + Stripe + Email providerHosting layer
The hosting layer serves the application, handles edge delivery, and manages production deployments.
Recommended deployment flowLink to section
Configure infrastructureLink to section
Provision PostgreSQL, configure production domains, and prepare environment variables.
Configure authenticationLink to section
Set production auth secrets, OAuth providers, and trusted host configuration.
Configure StripeLink to section
Create products, prices, webhooks, and production billing configuration.
Deploy the applicationLink to section
Push the application to production and validate environment configuration.
Validate production flowsLink to section
Test authentication, billing sync, route protection, checkout, and subscription access.
Environment variablesLink to section
Starter Pro separates infrastructure concerns clearly.
Core application variables
- DATABASE_URL
- NEXT_PUBLIC_APP_URL
- APP_BASE_URL
- production domains
Security variables
- AUTH_SECRET
- OAuth secrets
- Stripe secret keys
- Webhook signing secrets
Production rule
Never expose server-side secrets to the client. Public environment variables should only contain values safe for browsers.
Stripe production checklistLink to section
Before accepting real payments:
- configure live Stripe keys
- create production products and prices
- configure production webhooks
- validate webhook delivery
- test Checkout flow
- test Billing Portal flow
- validate subscription synchronization
- confirm billing-aware access rules
stripe listen --forward-to localhost:3000/api/webhooks/stripeDatabase deploymentLink to section
Starter Pro uses Prisma with PostgreSQL.
Typical production setup:
pnpm db:migrate
pnpm db:generateRecommended practices:
- managed PostgreSQL hosting
- automated backups
- connection pooling
- separate staging and production databases
- production-safe migration workflow
Deployment philosophyLink to section
Starter Pro intentionally separates:
- infrastructure
- product logic
- billing logic
- auth boundaries
- UI surfaces
This allows you to:
- deploy faster
- scale features safely
- keep billing reliable
- reduce production mistakes
- maintain long-term product velocity
Why this matters
Most SaaS launches slow down because infrastructure and product logic become tightly coupled. Starter Pro keeps those concerns separated from the beginning.
What you should customizeLink to section
You usually customize:
- branding
- product copy
- pricing strategy
- product workflows
- dashboard surfaces
- domain entities
You usually keep:
- deployment structure
- auth foundations
- billing infrastructure
- protected routing
- Stripe synchronization
- environment model
- server boundaries
Production readiness checklistLink to section
Infrastructure ready
Billing ready
Launch ready
Mental modelLink to section
Deployment is not the final step.
It is the system that allows your SaaS to scale safely after launch.