Documentación

Deploy to Vercel

DeploymentVercel workflowProduction setup

Vercel is the most direct deployment target for this template.

Because Fast Unicorn is built on Next.js with route handlers, locale-aware routing, and integration-driven environment variables, Vercel usually gives the smoothest path from local development to production.

Before you deploy

Complete the setup from Installation and Environment, and make sure your production integrations are ready before starting the deploy flow.

What this deployment guide covers

Infrastructure setup

Production database, environment variables, and provider configuration needed before the first deploy.

Deployment sequence

A practical order for importing the repo, attaching services, migrating the database, and publishing the app.

Post-deploy validation

Critical checks for auth, checkout, webhooks, and localized routing after the app is live.

Prerequisites

Before deploying

Make sure you have:

  • a production PostgreSQL database
  • all required environment variables
  • Stripe products and webhook configuration
  • a verified Resend sender
  • production OAuth credentials

These prerequisites matter because the app depends on several production-only integration values that cannot be safely guessed after deployment.

Deployment flow

Steps

  1. Import the repository into Vercel
  2. Add all environment variables from src/env.js
  3. Connect the production database
  4. Run pnpm db:push or your chosen Prisma deploy flow
  5. Deploy the app

Recommended order

Set environment variables before depending on the first successful production build. It reduces failed deploys caused by incomplete auth, Stripe, or email configuration.

After deployment

  • set NEXT_PUBLIC_APP_URL to the production domain
  • configure the Stripe webhook endpoint to https://your-domain.com/api/stripe/webhook
  • update Google OAuth allowed URLs
  • verify auth, checkout, and localized routes in production

These steps make the deployed app match the real production hostname and external provider expectations.

  • sign in with Google
  • sign up with credentials
  • password recovery email
  • subscription checkout
  • one-time payment checkout
  • dashboard access
Go-live validation

Final advice

Treat the first successful deploy as the beginning of production validation, not the end of it.

Use Production Checklist as the final pass before launch so auth, billing, email, and locale-aware routing are all verified together.