INFRASTRUCTURE

What it needs

• 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.)

PREREQUISITES

Before you start

• A deployment id from a failed ample deploy
• An Ample account token with servers:read

TESTED CONFIGURATION

Exactly what was tested

• build: npm run build --if-present
• install: npm install
• runtime: node
• size: s-1vcpu-1gb
• start: npm run start
• template: node-22

STEP BY STEP

How to do it

1. Read the failure code

Exit 1 with build_failed means next build failed in the isolated builder; exit 2 means a required preflight action is blocking.

2. Read the build log

Type errors, missing modules and memory failures show at the end of the build log.

ample logs <deployment_id> --kind build

3. Read the runtime log

A live app that does not answer usually failed to bind 0.0.0.0 on PORT; the runtime log shows it.

ample logs <deployment_id> --kind runtime

4. Fix and redeploy once

Change the source, then run ample deploy again. Do not loop deploys to poll status.

EXAMPLES

Tested examples

• Intentional build failure canary (tests/deploy-canaries/node-package-no-lock (build-and-list-failure)): A failing build command is rejected synchronously and its stderr line appears in the build log.

SUCCESS CHECKS

How to know it worked

• build log contains the failing command output

LIMITATIONS

Know the limits

• Verified on the node-22 template at s-1vcpu-1gb; other templates and sizes are not verified by this recipe.
• Region, compliance attestations and request-duration limits are unknown and not claimed.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
• Documentation only; no tool is executed automatically by the catalog.
• The failing-build evidence uses a generic Node fixture; Next.js-specific build failures were not separately reproduced.

COST

Cost estimate

Unknown. No price is claimed for this recipe.

EVIDENCE

Verification evidence

• canary_run on 2026-09-19T23:55:33Z at revision 1764076-tls-account-903d345: An intentionally failing build was rejected synchronously with build_failed and the failure line was readable in the build log. (expires 2027-03-18T23:55:33Z)
• 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)

EXECUTION

Execution binding

No execution binding. This recipe is documentation only; nothing is executed automatically.

NEXT ACTIONS

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 Troubleshoot deployment (GET /v1/catalog/nodes/intent%3Atroubleshoot-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.