Documentation

Vercel Deployment

StartupKit is optimized for Vercel, but the Next.js output runs on any Node host. These steps assume you cloned the zip into your own private Git repo.

Pre-flight Checklist

  • Database provisioned (MongoDB Atlas) and reachable from Vercel.
  • Stripe products, keys, and webhook URL ready.
  • Resend domain verified (or fallback sender prepared).
  • Environment variables copied from .env.

Deploy to Vercel

  1. Push your private repository (created from the zip) to GitHub, GitLab, or Bitbucket.
  2. Import the project in Vercel.
  3. Paste all env vars under Project Settings → Environment Variables (repeat for Preview vs Production as needed).
  4. Optionally add a postbuild script to run prisma migrate deploy beforenext build (or run it manually).
  5. Click Deploy.

Verification

  • Visit the live URL and create a test account.
  • Run through checkout with Stripe test mode and confirm the webhook logs in Vercel.
  • Ensure emails send from your production domain (or at least Arrive in Resend logs).
  • Check the dashboard pages still respect onboarding + subscription gating.

Production Tips

  • Rotate NEXTAUTH_SECRET and Stripe keys before handing a copy to a customer.
  • Disable /dev-tools in production by checking process.env.NODE_ENV (already handled).
  • Use Vercel Analytics or your preferred telemetry to monitor usage.
  • Schedule backups for MongoDB Atlas and Stripe webhooks.

Self-Hosting

Prefer another provider (Render, Railway, Fly.io, bare metal)? Run npm run build thennpm run start. Make sure the runtime exposes PORT and setNEXTAUTH_URL to the public domain.