# Home services: inventory manager using Next.js

An inventory manager blueprint for home services built with Next.js on Ample. Domain schema:

- **services** (sku, name, category, price_from, duration_estimate): service catalog as SKUs;
- **parts_stock** (sku, delta, reason, moved_at): parts and consumables movements;
- **jobs** (job_no, service_area, status, scheduled_for): jobs as orders with status transitions;
- **job_lines** (job_no, sku, qty): services and parts on a job;
- **events** (seq, record_type, record_id, kind, at): application-owned history written in the same transaction.

Public information: service catalog and pricing from, service areas and hours, licensing and insurance summary. Kept out of scope until handling is reviewed: customer addresses and access notes, payment details. Customer addresses and access instructions are personal data; keep them out until handling is reviewed. Technical basis 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).

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

- [S3-compatible object storageverified](/content/discover/primitive/s3-compatible-object-storage/index.html)  
  Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You need

- **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 home services data classes may be handled at all; this blueprint models public information only

## Exact tested configuration

- **build**  
  `npm run build --if-present`
- **install**  
  `npm install`
- **runtime**  
  `node`
- **sizes**  
  `1vcpu-1gb`
- **start**  
  `npm run start`
- **template**  
  `node-22`

## Steps

1.  **Model the home services domain.** Create the tables services, parts_stock, jobs, job_lines, events. Service catalog as skus lives in services; keep the sensitive classes (customer addresses and access notes, payment details) out of this schema.  
2.  **Workflow step 1.** Model SKUs and stock movements; derive stock from movements  
3.  **Workflow step 2.** Apply movements transactionally with an optimistic version check on the SKU  
4.  **Workflow step 3.** Record an event per movement for history  
5.  **Workflow step 4.** Deploy and verify history and rejected stale updates  
6.  **Deploy.** Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
```
$ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
```
7.  **Verify.** Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the home services workflow.
```
$ ample logs <deployment_id> --kind build
```

## How it was checked

✓ app responds on its public URL· http get/ → “ample canary next js patterns”  
✓ transactional-workflows self-test from the example· http get/p/transactional-workflows → “see the pattern fixture checks”

## Evidence

1. November 5, 2026 · 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); the transactional workflows checks passed: 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). The blueprint's Home services schema and workflow below build on that verified basis.

## Tested examples

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

## What it doesn’t cover

- The technical basis (transactional workflows on Next.js) was verified with the pattern fixture; the home services schema and workflow are an original design for this blueprint, built on that basis.
- Customer addresses and access instructions are personal data; keep them out until handling is reviewed.
- Verified on the node-22 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
