# Host Inventory Manager with Next.js: Relational Workspace Data

Deploy an inventory manager 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 inventory manager-specific behavior as your application code.

## Representative Queries
- Host inventory manager with Next.js: relational workspace data
- Where can I host Inventory manager 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

## Framework
- **Framework**: Next.js
- **Workload**: Inventory manager

## 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 <name> --public`
4. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/relational-records) and then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`. Command: `ample logs  --kind build`

## Success Checks
- **App responds on its public URL**: Expect path `/` to return `ample canary next js patterns`
- **Relational-records self-test**: Expect path `/p/relational-records` to return `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 inventory manager 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.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **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
- **Browse the catalog index**: `GET /v1/catalog`
- **Search published recipes**: `POST /v1/catalog/search`
- **Plan deployment**: `POST /v1/catalog/plan`
- **Read existing authentication setup**: `GET /mcp/setup`
- **Browse Inventory Manager**: `GET /v1/catalog/nodes/workload%3Ainventory-manager`
- **Browse Next.js**: `GET /v1/catalog/nodes/stack%3Aframework-next-js`
- **Browse Relational Records**: `GET /v1/catalog/nodes/pattern%3Arelational-records`
- **Browse Deploy Web App**: `GET /v1/catalog/nodes/intent%3Adeploy-web-app`