# Host project tracker with Next.js: relational workspace data

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

## Representative Queries
- Host project tracker with Next.js: relational workspace data
- Where can I host Project tracker built with Next.js?
- I need a workspace-specific schema, state transitions and access rules.

## 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**  
   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.  
   Command: `ample deploy . --name  --public`

4. **Verify**  
   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`.  
   Command: `ample logs  --kind build`

## Tested Configuration
- Template: node-22
- Runtime: node
- Size: s-1vcpu-1gb
- Install: npm install
- Build: npm run build --if-present
- Start: npm run start

## Examples
- **Next.js pattern fixture**  
  Multi-pattern Next.js app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
  Source Reference: tests/deploy-canaries/next-js-patterns

## Success Checks
- **App responds on its public URL**  
  Kind: http_get  
  Path: /  
  Expect: ample canary next js patterns

- **Relational-records self-test**  
  Kind: http_get  
  Path: /p/relational-records  
  Expect: records=ok transitions=true isolation=true

## 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 project tracker itself (your record schema, states and access rules) 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
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **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. 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 relational-records and configuration-secrets.

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

## Formats
- **HTML**: [Host project tracker with Next.js: relational workspace data](/content/recipes/project-tracker/next-js/relational-workspace/index.html)
- **Markdown**: [Link](/content/recipes/project-tracker/next-js/relational-workspace.md)
- **JSON**: [Link](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aproject-tracker%3Anext-js%3Arelational-workspace)

## Next Actions
1. **Browse the catalog index**  
   - Action ID: browse-catalog
   - Operation ID: catalog_index
   - Method: GET
   - Relative Path: /v1/catalog

2. **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":"Host project tracker with Next.js: relational workspace data"}}

3. **Prepare a side-effect-free deployment plan for an authorized project**  
   - Action ID: plan:page:recipes:project-tracker:next-js:relational-workspace
   - Operation ID: plan_deployment
   - Method: POST
   - Relative Path: /v1/catalog/plan
   - Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:project-tracker:next-js:relational-workspace","recipeRevision":"r1"}}

4. **Read the existing agent authentication setup**  
   - Action ID: auth-setup
   - Operation ID: existing_auth_setup
   - Method: GET
   - Relative Path: /mcp/setup

5. **Browse Project tracker**  
   - Action ID: browse:workload:project-tracker
   - Operation ID: browse_node
   - Method: GET
   - Relative Path: /v1/catalog/nodes/workload%3Aproject-tracker

6. **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

7. **Browse Relational records**  
   - Action ID: browse:pattern:relational-records
   - Operation ID: browse_node
   - Method: GET
   - Relative Path: /v1/catalog/nodes/pattern%3Arelational-records

8. **Browse Deploy web app**  
   - Action ID: browse:intent:deploy-web-app
   - Operation ID: browse_node
   - Method: GET
   - Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app