Migrate Render web service: Next.js

Move Next.js compute from Render web service 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

Copy environment variables and secret files from the Render dashboard into an env file kept out of the repository. Not migrated automatically: Render cron jobs, disks and private-service networking are not migrated; persistent data belongs in a managed database, a bucket or an Ample volume.

Cutover

Add the custom domain with ample domain add, update DNS from the Render target, keep the Render service until verified, then suspend it.

Rollback

Keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

Representative Queries

• Migrate Render web service: Next.js
• Where can I host Next.js built with Next.js?
• I need a component-scoped export/import or reconfiguration procedure for Next.js, with compatibility checks, verification and rollback.

Prerequisites

• Authorized access to the Render web service 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

Workflow Steps

1. Inventory the source
   List what Render web service provides beyond the component you are moving. Out of scope here: Render cron jobs, disks and private-service networking are not migrated; persistent data belongs in a managed database, a bucket or an Ample volume.

2. Source step 1
   Copy environment variables and secret files from the Render dashboard into an env file kept out of the repository.

3. Source step 2
   Translate the Render build and start commands (or render.yaml) into the repository's manifest or --build-command/--start.

4. Source step 3
   Note Render-only features in use: background workers, cron jobs, disks, private services.

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.

   Command: 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 Render target, keep the Render service until verified, then suspend it.

8. Rollback
   Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

Success Checks

• Destination app responds on its public URL.
  • Kind: http_get
  • Path: /
  • Expect: ample canary next js patterns
• Configuration-secrets check from the destination example.
  • Kind: http_get
  • Path: /p/configuration-secrets
  • Expect: see the pattern fixture checks.
• Relational-records check from the destination example.
  • Kind: http_get
  • Path: /p/relational-records
  • Expect: see the pattern fixture checks.
• Data or object counts and checksums match the source.
  • Kind: manual
  • Expect: operator comparison before cutover.

Limitations

• Documentation only: nothing is executed automatically and no execution binding is offered.
• The source-side procedure is documented from Render web service's standard tooling and was not executed in this catalog's evidence; the destination side was verified with the pattern fixture.
• No full source-product parity is claimed: Render cron jobs, disks and private-service networking are not migrated; persistent data belongs in a managed database, a bucket or an Ample volume.
• Verified on the node-22 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures on the managed side are not verified beyond the pattern checks.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Authoritative: true
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

Components

1. App server
   • Size: s-1vcpu-1gb
   • Quantity: 1.0
   • Monthly Amount: 5.0
2. Managed PostgreSQL database
   • Size: s-1vcpu-1gb
   • Quantity: 1.0
   • Monthly Amount: 5.0

Note: Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.

Evidence Summary

• Kind: canary_run
• Summary: 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 Render web service is documented from the vendor's standard tooling and was not executed by this catalog's evidence.
• Observed At: 2026-09-21T02:34:39Z
• Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)
• Expires At: 2027-03-20T02:34:39Z
• Scope:
  • Checks: [/p/configuration-secrets, /p/relational-records]
  • Destination Only: true
  • Template: node-22

Next Actions

• Browse the catalog index
  • Action ID: browse-catalog
  • Operation ID: catalog_index
  • Method: GET
  • Relative Path: /v1/catalog
• Search published recipes by intent, stack and constraints
  • Action ID: search-recipes
  • Operation ID: search_recipes
  • Method: POST
  • Relative Path: /v1/catalog/search
  • Parameters:
    • Body: {"limit":5,"query":"Migrate Render web service: Next.js"}
• Prepare a side-effect-free deployment plan for an authorized project
  • Action ID: plan:page:migrate:render-web-service:next-js
  • Operation ID: plan_deployment
  • Method: POST
  • Relative Path: /v1/catalog/plan
  • Parameters:
    • Body: {"inputs":{},"projectId":"","recipeId":"page:migrate:render-web-service:next-js","recipeRevision":"r1"}
• Read the existing agent authentication setup
  • Action ID: auth-setup
  • Operation ID: existing_auth_setup
  • Method: GET
  • Relative Path: /mcp/setup
• Browse Render web service
  • Action ID: browse:migration:render-web-service
  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/migration%3Arender-web-service
  • Parameters: {"nodeId":"migration:render-web-service"}
• Browse Next.js
  • Action ID: browse:stack:framework-next-js
  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/stack%3Aframework-next-js
  • Parameters: {"nodeId":"stack:framework-next-js"}
• Browse Migrate compute
  • Action ID: browse:intent:migrate-compute
  • Operation ID: browse_node
  • Method: GET
  • Relative Path: /v1/catalog/nodes/intent%3Amigrate-compute
  • Parameters: {"nodeId":"intent:migrate-compute"}