## Equipment rental: product catalog using Next.js

### Summary
A product catalog blueprint for equipment rental built with Next.js on Ample. Domain schema: equipment (sku, name, category, day_rate, serial_tracked): rental catalog; stock_movements (sku, unit_serial, delta, reason, moved_at): check-outs, returns, and maintenance; rentals (rental_no, period_start, period_end, status): rentals with status transitions; rental_lines (rental_no, sku, unit_serial, rate): rental contents; events (seq, record_type, record_id, kind, at): application-owned history written in the same transaction. Public information: equipment catalog and rates, availability calendar, deposit and insurance terms. Kept out of scope until handling is reviewed: renter identity documents, payment, and deposit details. Identity verification and deposits are outside these flows; only availability and rental status are modeled.

### Representative Queries
- Equipment rental: product catalog using Next.js
- Where can I host Equipment rental: Product catalog built with Next.js?
- I need a genuinely specialized product catalog workflow covering asset serial numbers, availability windows, and return status.

### Resource Requirements
- **Compute**
- **Postgres**
- **S3-compatible object storage**

### Infrastructure Requirements
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### Framework
Next.js

### Workload
Product catalog

### Industry
Equipment rental

### Release Status
Published

### Support Status
Verified

### Execution Status
Ready

### Documentation Prerequisites
- A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
- A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables
- A review of which equipment rental data classes may be handled at all; this blueprint models public information only

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

### Workflow Steps
1. **Model the equipment rental domain**: Create the tables equipment, stock_movements, rentals, rental_lines, events. Rental catalog lives in equipment; keep the sensitive classes (renter identity documents, payment and deposit details) out of this schema.
2. **Workflow step 1**: Model the SKU catalog with versioned updates.
3. **Workflow step 2**: Record every catalog change as an event in the same transaction.
4. **Workflow step 3**: Reject stale concurrent updates.
5. **Workflow step 4**: Deploy and verify history and conflict handling.
6. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
7. **Verify**: Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the equipment rental workflow.

### Examples
- **Next.js pattern fixture**: Verified transactional workflows basis for this blueprint.

### Success Checks
- App responds on its public URL.
- Transactional-workflows self-test from the example.

### Limitations
- The technical basis (transactional workflows on Next.js) was verified with the pattern fixture; the equipment rental schema and workflow are an original design for this blueprint and were not executed as a separate application.
- No health, financial, privacy or other compliance claim is made. Identity verification and deposits are outside these flows; only availability and rental status are modeled.

### 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: s-1vcpu-1gb, 1.0, 5.0
  - Managed PostgreSQL database: s-1vcpu-1gb, 1.0, 5.0

### Evidence Summary
- **Canary run**: Next.js pattern fixture deployed on Ample. The transactional workflows checks passed: an optimistic version check and an event row written in the same transaction.

### Next Actions
- Browse the catalog index
- Search published recipes by intent, stack, and constraints
- Prepare a side-effect-free deployment plan for an authorized project
- Read the existing agent authentication setup
- Browse Equipment rental
- Browse Product catalog
- Browse Next.js
- Browse Deploy web app
