Host reporting dashboard with Next.js: relational workflow state

Deploy a reporting dashboard 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 reporting dashboard-specific behavior as your application code.

Representative Queries

• Host reporting dashboard with Next.js: relational workflow state
• Where can I host Reporting dashboard built with Next.js?
• I need a domain record schema, validation rules and concurrency behavior.

Resource Requirements

• Primitive: Compute
• Primitive: Postgres

Infrastructure Requirements

1. 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.
2. 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.

Prerequisites

• A Next.js project that builds and starts with the documented commands (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
• A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
• An Ample account token with servers:write, databases:read

Workflow Steps

1. Build and start
   • Command: 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
   • Body: 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
   • Command: ample deploy . --name --public
   • Body: 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
   • Command: ample logs --kind build
   • Body: Fetch the live URL and the pattern self-test route(s) (/p/transactional-workflows); then run your own checks. On failure read ample logs --kind build then --kind runtime.

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 reporting dashboard 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
• 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

Next Actions

• Browse the catalog index
  • Action ID: browse-catalog
  • Method: GET
• Search published recipes by intent, stack and constraints
  • Action ID: search-recipes
  • Method: POST
• Prepare a side-effect-free deployment plan for an authorized project
  • Action ID: plan:page:recipes:reporting-dashboard:next-js:relational-workflow
  • Method: POST
• Read the existing agent authentication setup
  • Action ID: auth-setup
  • Method: GET