page:recipes:product catalog:next js:download delivery

Host product catalog with Next.js: authorized file delivery

Summary

Deploy a product catalog built with Next.js on Ample using the generated downloads pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on Next.js: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the product catalog-specific behavior as your application code.

Representative Queries

• Host product catalog with Next.js: authorized file delivery
• Where can I host Product catalog built with Next.js?
• I need a file entitlement model and an application-enforced download authorization flow.

Workflow Steps

1. Build and start
   next build then next start -H 0.0.0.0 -p $PORT on the node-22 template. The server must bind 0.0.0.0 on PORT.

2. Implement the pattern on PostgreSQL
   The fixture's module implements generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. Wire object storage
   Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket.

4. Deploy
   Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.
   ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...

5. Verify
   Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
   ample logs --kind build

Examples

• Next.js pattern fixture: Multi-pattern Next.js app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

• app responds on its public URL
  kind: http_get
  path: /
  expect: ample canary next js patterns

• generated-downloads self-test
  kind: http_get
  path: /p/generated-downloads
  expect: export=ok rows=3 (with ?token=...; 401 without)

Limitations

• Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Next.js major versions are not verified.
• The product catalog itself (your export formats, retention policy and entitlement model) is application code and was not separately tested; the pattern checks are what was verified.

Evidence Summary

• Canary Run: Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); checks passed for generated-downloads and configuration-secrets. Pattern proof: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Observed at 2026-09-21T02:34:39Z.

Cost Estimate

• Monthly Amount: $10.0 (USD)
  • App Server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.0
  • Managed PostgreSQL Database: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.0

Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Next Actions

• Browse the catalog index: GET /v1/catalog
• Search published recipes by intent, stack and constraints: POST /v1/catalog/search
• Prepare a side-effect-free deployment plan for an authorized project: POST /v1/catalog/plan
• Read the existing agent authentication setup: GET /mcp/setup
• Browse Product catalog: GET /v1/catalog/nodes/workload%3Aproduct-catalog
• Browse Next.js: GET /v1/catalog/nodes/stack%3Aframework-next-js
• Browse Generated downloads: GET /v1/catalog/nodes/pattern%3Agenerated-downloads
• Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app