--- title: "Migrate Heroku app: Next.js" description: "Move Next.js compute from Heroku app to Ample, one component at a time." canonical_url: "https://ample.computer/migrate/heroku-app/next-js" last_updated: "2026-09-21" --- # Migrate Heroku app: Next.js Canonical URL: https://ample.computer/migrate/heroku-app/next-js Formats: [HTML](https://ample.computer/migrate/heroku-app/next-js) | [Markdown](https://ample.computer/migrate/heroku-app/next-js.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Amigrate%3Aheroku-app%3Anext-js) Recipe ID: `page:migrate:heroku-app:next-js` | Revision: `r1` | Catalog revision: `cat_f13ab9a494120b5e` Status: release `published`, support `verified`, execution `unbound` ## Summary Move Next.js compute from Heroku app to Ample, one component at a time. Destination verified on Ample: the app built, started and answered on its public HTTPS URL with encrypted configuration delivered. Source procedure: Export config vars with `heroku config -s -a ` into an env file kept out of the repository. Not migrated automatically: Heroku add-ons other than Postgres, release-phase scheduling, dyno autoscaling and Heroku Scheduler are not migrated; use `--release-command` for release tasks. Cutover: Add the custom domain with `ample domain add`, update DNS from the Heroku DNS target, keep the Heroku app until verified, then scale it down. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide. Path: [Agent hosting discovery](/discover/discovery) / [Migration sources by component](/discover/migration) / [Compute sources](/discover/migration/compute-sources) / [Heroku app](/discover/migration/heroku-app) / [Migrate Heroku app: Next.js](/migrate/heroku-app/next-js) ## Infrastructure requirements - [Compute](/discover/primitive/compute): verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.) - [Postgres](/discover/primitive/postgres): verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.) ## Prerequisites - Authorized access to the Heroku app source and its export tooling - An inventory of every component in scope and out of scope - A validated backup or copy before any cutover - An Ample account token with servers:write, databases:read ## Exact tested configuration - template: `node-22` - runtime: `node` - size: `s-1vcpu-1gb` - install: `npm install` - build: `npm run build --if-present` - start: `npm run start` ## Steps 1. **Inventory the source.** List what Heroku app provides beyond the component you are moving. Out of scope here: Heroku add-ons other than Postgres, release-phase scheduling, dyno autoscaling and Heroku Scheduler are not migrated; use `--release-command` for release tasks. 2. **Source step 1.** Export config vars with `heroku config -s -a ` into an env file kept out of the repository 3. **Source step 2.** Translate the `Procfile` web process into the start command (`--start` or the package manifest's start script); worker processes need a separate `--kind worker` service 4. **Source step 3.** Note buildpacks and add-ons in use; managed databases replace Heroku Postgres, other add-ons need their own plan 5. **Deploy on Ample in parallel.** next build then next start -H 0.0.0.0 -p $PORT on the node-22 template. Pass the exported variables with --env; keep the source running. ``` ample deploy . --name --public --env-file .env.production ``` 6. **Validate before cutover.** Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/configuration-secrets, /p/relational-records). 7. **Cut over.** Add the custom domain with `ample domain add`, update DNS from the Heroku DNS target, keep the Heroku app until verified, then scale it down. 8. **Rollback.** Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation. ## Tested examples - **Next.js pattern fixture (destination)** (tests/deploy-canaries/next-js-patterns): Verified destination basis: Next.js compute. ## Success checks - destination app responds on its public URL (`/` on the live URL, expect ample canary next js patterns) - configuration-secrets check from the destination example (`/p/configuration-secrets` on the live URL, expect see the pattern fixture checks) - relational-records check from the destination example (`/p/relational-records` on the live URL, expect see the pattern fixture checks) - data or object counts and checksums match the source ## Cost estimate Estimated 10.00 USD per month (size prices from pricing.toml at build revision 515b7316fc6e5a81679407ae0c811146ceb2c5c7). - app server x1 `s-1vcpu-1gb`: 5.00 USD - managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample. ## Verification evidence - canary_run on 2026-09-21T02:34:39Z at revision `1d28ae0 (CLI 0.1.21)`: Destination side verified: the Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template) and its checks passed (the app built, started and answered on its public HTTPS URL with encrypted configuration delivered). The source-side export from Heroku app is documented from the vendor's standard tooling and was not executed by this catalog's evidence. (expires 2027-03-20T02:34:39Z) Last verified: 2026-09-21T02:34:39Z ## Execution binding No execution binding. This recipe is documentation only; nothing is executed automatically. ## Next actions - Browse the catalog index (GET /v1/catalog on the api origin; auth: false, approval: false) - Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; auth: false, approval: false) - Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; auth: true, approval: false) - Read the existing agent authentication setup (GET /mcp/setup on the api origin; auth: false, approval: false) - Browse Heroku app (GET /v1/catalog/nodes/migration%3Aheroku-app on the api origin; auth: false, approval: false) - Browse Next.js (GET /v1/catalog/nodes/stack%3Aframework-next-js on the api origin; auth: false, approval: false) - Browse Migrate compute (GET /v1/catalog/nodes/intent%3Amigrate-compute on the api origin; auth: false, approval: false) Actions describe possible next steps. They are typed data, not commands, and grant no permission.