# Hospitality: reporting dashboard using Next.js

A reporting dashboard blueprint for hospitality built with Next.js on Ample. Domain schema: room\_types (sku, name, capacity, base\_rate, amenities): room and package catalog; inventory\_movements (sku, date, delta, reason): availability per date as stock movements; bookings (booking\_no, check\_in, check\_out, status): bookings with status transitions; booking\_lines (booking\_no, sku, nights, rate): booking contents; exports (id, definition, object\_key, row\_count, generated\_at, authorized\_role): generated artifacts and who may download them. Public information: room types, amenities and rates from, property location and policies, events and dining. Kept out of scope until handling is reviewed: guest identity documents, payment details, stay history. Guest identity documents are sensitive; only availability and booking status are modeled here. Technical basis verified on Next.js: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).

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

## Exact tested configuration

buildnpm run build --if-present

installnpm install

runtimenode

sizes-1vcpu-1gb

startnpm run start

templatenode-22

## Steps

1. **Model the hospitality domain.** Create the tables room\_types, inventory\_movements, bookings, booking\_lines, exports. Room and package catalog lives in room\_types; keep the sensitive classes (guest identity documents, payment details, stay history) out of this schema.

2. **Workflow step 1.** Model report definitions scoped to the agency

3. **Workflow step 2.** Generate report artifacts from queries and store them with metadata

4. **Workflow step 3.** Authorize downloads (401 without identity)

5. **Workflow step 4.** Deploy and verify an authorized export and the rejected anonymous request

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/generated-downloads) and your own acceptance checks for the hospitality workflow.

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

## How it was checked

✓app responds on its public URL· http get/ → “ample canary next js patterns”  
✓generated-downloads self-test from the example· http get/p/generated-downloads → “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 generated downloads checks passed: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). The blueprint's Hospitality schema and workflow below build on that verified basis.

## Tested examples

- **Next.js pattern fixture.** Verified generated downloads basis for this blueprint.

## What it doesn’t cover

- The technical basis (generated downloads on Next.js) was verified with the pattern fixture; the hospitality schema and workflow are an original design for this blueprint, built on that basis.
- Guest identity documents are sensitive; only availability and booking status are modeled here.
- 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.
