Host approval workflow with Next.js: relational workspace data

Deploy an approval workflow built with Next.js on Ample using the relational records 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: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the approval workflow-specific behavior as your application code.

Representative Queries

• Host approval workflow with Next.js: relational workspace data
• Where can I host Approval workflow built with Next.js?
• I need a workspace-specific schema, state transitions and access rules.

Resource Requirements

• primitive:compute
• primitive:postgres

Infrastructure Requirements

1. 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.
2. Postgres (verified): 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: 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 relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). 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/relational-records) from the example; 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 approval workflow itself (your record schema, states and access rules) is application code and was not separately tested.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.00
• Components:
  • App server: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
  • Managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Next Actions

1. Browse the catalog index: GET /v1/catalog
2. Search published recipes: POST /v1/catalog/search with body { "limit": 5, "query": "Host approval workflow with Next.js: relational workspace data" }
3. Prepare a deployment plan: POST /v1/catalog/plan with body { "inputs": {}, "projectId": "", "recipeId": "page:recipes:approval-workflow:next-js:relational-workspace", "recipeRevision": "r1" }
4. Read the existing agent authentication setup: GET /mcp/setup
5. Browse Approval workflow: GET /v1/catalog/nodes/workload%3Aapproval-workflow
6. Browse Next.js: GET /v1/catalog/nodes/stack%3Aframework-next-js
7. Browse Relational records: GET /v1/catalog/nodes/pattern%3Arelational-records
8. Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app