Deploy a Next.js SaaS to Vercel

Deploy the Next.js editions of ShipAny (Next, Two, One) to Vercel — private GitHub repo, import, environment variables, custom domain and webhook URLs.

Last updated: Oct 8, 2026

Vercel is the natural home for ShipAny's Next.js editions — ShipAny Next, Two and One. Connect a Git repository, set a few environment variables, and every push deploys. (ShipAny TanStack and Vinext are built for Cloudflare Workers, Node or Docker — see the Cloudflare guide.)

Steps

  1. Create a private GitHub repository for your project. ShipAny's license doesn't allow publishing the source publicly.
  2. Push your project:
git remote set-url origin git@github.com:your-org/your-repo.git
git push origin main
  1. Import the repository in Vercel.
  2. Add environment variables: your app URL and name, DATABASE_PROVIDER / DATABASE_URL, and AUTH_SECRET (generate it with openssl rand -base64 32). Provider keys — payments, OAuth, email, storage — go in the admin panel after deploy, not in Vercel.
  3. Deploy, then add your custom domain in the project settings.
  4. Point third-party callbacks at the new domain: OAuth redirect URIs and payment webhooks.

Tips

  • Use a serverless-friendly database — Neon, Supabase (pooled connection) or Turso — since each function invocation opens its own connection.
  • Set the app URL to the final domain before the production build, or auth origin checks and payment callbacks will point at the wrong host.
  • Keep AUTH_SECRET stable — changing it signs every user out.

Related reading

More in Integrations

Ship your AI SaaS with ShipAny

Auth, payments, credits, i18n and admin are pre-wired — start from a production-ready template and focus on your product.