## The short version

Configure build and start for a Next.js app on Ample. A server-rendered app runs next build then next start on the node-22 template with the detected package manager; a static export is published as a static site. The app must bind 0.0.0.0 on PORT.

## What it needs
- [Compute](/content/discover/primitive/compute/index.html): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.)

## Before you start
- A package.json with build and start scripts (next build, next start -H 0.0.0.0 -p ${PORT:-3000})
- Node 22 compatible dependencies
- An Ample account token with servers:write

## How to do it
1.  
   ### Make next start listen correctly  
   Use next start -H 0.0.0.0 -p ${PORT:-3000} so the health check reaches the server.
2.  
   ### Deploy  
   Run the existing synchronous deploy once from the project directory and read the result. Exit 0 is live, 1 is failed, 2 is blocked on a required preflight action. Re-running with no change is a content-addressed no-op.
   
   ```
   ample deploy . --name <app-name> --public --format json
   ```
3.  
   ### Static exports  
   With output: 'export' the build is published as a static site with correct 404 handling; no server process runs.
4.  
   ### Verify  
   Fetch the live URL and run the success checks below. On failure read the build log, then the runtime log, fix the cause and deploy again; do not blind-retry.
   
   ```
   ample logs <deployment_id> --kind build
   ```

## Tested examples
- **Next.js SSR canary** (`tests/deploy-canaries/next-basic-ssr`): next build and next start with a page and an API route.
- **pnpm Next.js canary** (`tests/deploy-canaries/pnpm-next-basic`): Package manager detection with pnpm.
- **Static export canary** (`tests/deploy-canaries/next-static-export`): output: 'export' published as a static site.

## How to know it worked
- page renders (`/` on the live URL, expect ample canary next basic ssr)
- API route stays a Next route (`/api/canary` on the live URL, expect next api stays next)

## Cost estimate
Estimated 5.00 USD per month (size prices from pricing.toml at build revision ca0b484a7a9957c573a88d3a32dc603c3c10135a).
- app server x1 `s-1vcpu-1gb`: 5.00 USD

Upper-bound monthly price of the tested sizes. Plan quotas and budgets apply.

## Verification evidence
- canary_run on 2026-09-19T23:55:33Z at revision `1764076-tls-account-903d345`: Next.js 15 SSR app (next build, next start) deployed on node-22; the page and an API route served correctly. (expires 2027-03-18T23:55:33Z)
- canary_run on 2026-09-19T23:55:33Z at revision `1764076-tls-account-903d345`: Next.js app using pnpm deployed with the detected package manager. (expires 2027-03-18T23:55:33Z)
- canary_run on 2026-09-19T23:55:33Z at revision `1764076-tls-account-903d345`: Next.js static export (Vercel-style output) was published and served, including a nested route and a correct 404. (expires 2027-03-18T23:55:33Z)

## Execution binding
MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-20T01:55:48.667900+00:00 at revision `199ff1dfd526`. Binding state at export: schema_changed. Required scopes: servers:write.

## Typed next actions
- Browse the catalog index (`GET /v1/catalog` on the api origin; authentication not required, approval not required)
- Search published recipes by intent, stack and constraints (`POST /v1/catalog/search` on the api origin; authentication not required, approval not required)
- Prepare a side-effect-free deployment plan for an authorized project (`POST /v1/catalog/plan` on the api origin; authentication required, approval not required)
- Read the existing agent authentication setup (`GET /mcp/setup` on the api origin; authentication not required, approval not required)
- Browse Next.js (`GET /v1/catalog/nodes/stack%3Aframework-next-js` on the api origin; authentication not required, approval not required)
- Browse Configure deployment (`GET /v1/catalog/nodes/intent%3Aconfigure-deployment` on the api origin; authentication not required, approval not required)
- Browse Public web service (`GET /v1/catalog/nodes/pattern%3Apublic-web-service` on the api origin; authentication not required, approval not required)

Actions describe possible next steps. They are typed data, not commands, and grant no permission. Public discovery never provisions anything; planning requires your own authenticated token and approval happens in your client.

## Identifiers and status
Recipe `page:guides:next-js:build-and-start`. Revision r1.

release **published** support **verified** execution **blocked (schema_changed: live tool schema differs from the recorded binding)**

Formats: [HTML](/content/guides/next-js/build-and-start/index.html) \| [Markdown](/content/guides/next-js/build-and-start.md) \| [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Aguides%3Anext-js%3Abuild-and-start)