Migrate Vercel app: Next.js · Ample Computer

Migrate Vercel app: Next.js

Move a Next.js app's compute from Vercel to Ample. Server-rendered apps run with next build and next start; static exports are published as static sites; environment variables move with --env; a PostgreSQL database can be supplied by URL or auto-provisioned. Cutover is a DNS change with ample domain, and Vercel stays untouched until you confirm.

Verified November 6, 2026

What it runs on

You need

Exact tested configuration

Steps

  1. Inventory. List what the app uses on Vercel. Compute and environment variables are in scope; edge middleware, ISR revalidation, image optimization, cron jobs, and Vercel integrations are out of scope and must be reviewed.

  2. Deploy to Ample in parallel. Deploy the same source with its environment variables; Vercel keeps serving production.

   $ ample deploy . --name <app-name> --public --env KEY=value
  1. Validate on the Ample URL. Run the app's smoke tests and the success checks; compare responses with production.

  2. Cut over DNS. Add the custom domain and set the documented DNS records; TLS is issued automatically. Keep Vercel until traffic is verified.

   $ ample domain add <domain> --app <app-name>
  1. Rollback. Point DNS back to Vercel. Nothing on Vercel was changed by this recipe.

How it was checked

✓ page renders on the Ample URL · http get/ → “ample canary next basic ssr”
✓ database route reports a live connection · http get/api/db → “postgres=ok”

Evidence

  1. November 6, 2026 · canary run Next.js static export (Vercel-style output) was published and served, including a nested route and a correct 404.
  2. November 6, 2026 · canary run Next.js 15 SSR app (next build, next start) deployed on node-22; the page and an API route served correctly.
  3. November 6, 2026 · canary run Next.js 15 route handler using pg with no DATABASE_URL supplied: Ample auto-provisioned a managed PostgreSQL database and /api/db reported postgres=ok.

Tested examples

What it doesn’t cover