# Property management: vendor portal using Next.js

A vendor portal blueprint for property management built with Next.js on Ample. Domain schema:

- **listings** (reference, address, unit, rent, publishing_status, agency_id): rental listings with publishing status;
- **agencies** (name, license_number, portfolio_size): management offices;
- **maintenance_vendors** (name, trade, agency_id, status): vendors per office;
- **reports** (agency_id, period, object_key, generated_at): portfolio reports per office;
- **document_access** (document_id, principal_reference, role, granted_at): who may read which document.

Public information: available rentals, office contacts, application process. Kept out of scope until handling is reviewed: tenant identity and payment history, inspection reports with personal data. Tenant data is personal and often regulated; only published listings and office-scoped reporting are modeled. Technical basis verified on Next.js: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

**Verified** November 5, 2026

## 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 property management 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 property management domain.** Create the tables listings, agencies, maintenance_vendors, reports, document_access. Rental listings with publishing status lives in listings; keep the sensitive classes (tenant identity and payment history, inspection reports with personal data) out of this schema.

2. **Workflow step 1.** Model vendors scoped to the agency with roles.

3. **Workflow step 2.** Authorize document access by vendor and role (401, 403 negative tests).

4. **Workflow step 3.** Store vendor documents in the private bucket.

5. **Workflow step 4.** Deploy and verify the negative tests and an authorized download.

6. **Deploy.** Run the synchronous deploy once and read the result. Re-running with no change is a no-op.

```sh
$ 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/private-document-library) and your own acceptance checks for the property management workflow.

```sh
$ ample logs <deployment_id> --kind build
```

## How it was checked

✓ app responds on its public URL · http get/ → “ample canary next js patterns”  
✓ private-document-library self-test from the example · http get/p/private-document-library → “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 private document library checks passed: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). The blueprint's Property management schema and workflow below build on that verified basis.

## Tested examples

- **Next.js pattern fixture.** Verified private document library basis for this blueprint.

## What it doesn’t cover

- The technical basis (private document library on Next.js) was verified with the pattern fixture; the property management schema and workflow are an original design for this blueprint, built on that basis.
- Tenant data is personal and often regulated; only published listings and office-scoped reporting are modeled.
- 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.
