Host digital downloads with Next.js: relational catalog data

Deploy a digital downloads built with Next.js on Ample using the transactional workflows 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. Verified on Next.js: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Not separately tested: your domain records, validation rules and concurrency policy; treat the digital downloads-specific behavior as your application code.

Representative Queries

• Host digital downloads with Next.js: relational catalog data
• Where can I host Digital downloads built with Next.js?
• I need catalog tables, transactional update logic and application-level access boundaries.

Resource Requirements

• primitive:compute
• primitive:postgres

Infrastructure Requirements

• Compute

  • Status: verified
  • Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

• Postgres

  • Status: verified
  • Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

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 transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. Deploy
   ample deploy . --name --public. 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.

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

Success Checks

• App responds on its public URL
  Kind: http_get
  Path: /
  Expect: ample canary next js patterns

• Transactional-workflows self-test
  Kind: http_get
  Path: /p/transactional-workflows
  Expect: tx=ok history=2 conflict=rejected

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 digital downloads itself (your domain records, validation rules and concurrency policy) is application code and was not separately tested; the pattern checks are what was verified.
• 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.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

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 transactional-workflows and configuration-secrets.
  • Observed At: 2026-09-21T02:34:39Z
  • Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)
  • Expires At: 2027-03-20T02:34:39Z

Formats

• HTML
• Markdown
• JSON