# 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

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

## You need

- The Next.js source and its environment variable names and values
- next start bound to 0.0.0.0 on PORT (Vercel does not require this; Ample does)
- A component inventory: edge middleware, ISR, image optimization, cron jobs (they become `ample job` schedules) and Vercel-specific integrations
- An Ample account token with servers:write, databases:read and domains:write for cutover

## Exact tested configuration

- `build` npm run build --if-present
- `install` npm install
- `runtime` node
- `sizes` 1vcpu-1gb
- `start` npm run start
- `template` node-22

## 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.

```sh
   $ ample deploy . --name <app-name> --public --env KEY=value
   ```

3. **Validate on the Ample URL.** Run the app's smoke tests and the success checks; compare responses with production.

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

```sh
   $ ample domain add <domain> --app <app-name>
   ```

5. **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

- **Static export canary.** Vercel-style static export served with correct 404 handling.
- **SSR canary.** next build and next start.
- **Next.js + pg canary.** Database connection from a route handler with an auto-provisioned managed database.

## What it doesn’t cover

- Verified on the node-22 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Apps and their managed databases are placed together, in the same region.
- Each stage is an ordinary `ample deploy` or `ample domain` command you run.
- Edge middleware, ISR, and image optimization run in the app or framework; cron jobs become `ample job` schedules; reconnect Vercel integrations to the app directly.
- Vercel-side changes and deletion are the user's separate actions.
