--- title: "Hospitality: reporting dashboard using Next.js" description: "A reporting dashboard blueprint for hospitality built with Next.js on Ample." canonical_url: "https://ample.computer/blueprints/hospitality/reporting-dashboard/next-js" last_updated: "2026-09-21" --- # Hospitality: reporting dashboard using Next.js Canonical URL: https://ample.computer/blueprints/hospitality/reporting-dashboard/next-js Formats: [HTML](https://ample.computer/blueprints/hospitality/reporting-dashboard/next-js) | [Markdown](https://ample.computer/blueprints/hospitality/reporting-dashboard/next-js.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Ahospitality%3Areporting-dashboard%3Anext-js) Recipe ID: `page:blueprints:hospitality:reporting-dashboard:next-js` | Revision: `r1` | Catalog revision: `cat_f13ab9a494120b5e` Status: release `published`, support `verified`, execution `ready` ## Summary 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). Path: [Agent hosting discovery](/discover/discovery) / [Industries and specialties](/discover/industry) / [Property and mobility](/discover/industry/property-and-mobility) / [Hospitality](/discover/industry/hospitality) / [Hospitality: reporting dashboard using Next.js](/blueprints/hospitality/reporting-dashboard/next-js) ## Infrastructure requirements - [Compute](/discover/primitive/compute): verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.) - [Postgres](/discover/primitive/postgres): verified (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](/discover/primitive/s3-compatible-object-storage): verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.) ## 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 hospitality data classes may be handled at all; this blueprint models public information only ## Exact tested configuration - template: `node-22` - runtime: `node` - size: `s-1vcpu-1gb` - install: `npm install` - build: `npm run build --if-present` - start: `npm run start` ## 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 --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 --kind build ``` ## Tested examples - **Next.js pattern fixture** (tests/deploy-canaries/next-js-patterns): Verified generated downloads basis for this blueprint. ## Success checks - app responds on its public URL (`/` on the live URL, expect ample canary next js patterns) - generated-downloads self-test from the example (`/p/generated-downloads` on the live URL, expect see the pattern fixture checks) ## Cost estimate Estimated 10.00 USD per month (size prices from pricing.toml at build revision 515b7316fc6e5a81679407ae0c811146ceb2c5c7). - app server x1 `s-1vcpu-1gb`: 5.00 USD - managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included. ## Verification evidence - canary_run on 2026-09-21T02:34:39Z at revision `1d28ae0 (CLI 0.1.21)`: 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 and were not separately executed. (expires 2027-03-20T02:34:39Z) Last verified: 2026-09-21T02:34:39Z ## Execution binding MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`, binding state `current`, required scopes: servers:write, databases:read, buckets:read. ## Input schema ```json { "additionalProperties": false, "properties": { "env": { "description": "Encrypted environment variables", "items": { "pattern": "^[A-Z][A-Z0-9_]*=.*$", "type": "string" }, "maxItems": 50, "type": "array" }, "name": { "description": "App name", "maxLength": 63, "minLength": 1, "pattern": "^[a-z0-9-]+$", "type": "string" }, "path": { "description": "Project directory or ample.toml service", "maxLength": 512, "minLength": 1, "type": "string" }, "release_command": { "description": "Migration command run before activation", "maxLength": 512, "type": "string" } }, "required": [ "env", "name", "path" ], "type": "object" } ``` ## Next actions - Browse the catalog index (GET /v1/catalog on the api origin; auth: false, approval: false) - Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; auth: false, approval: false) - Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; auth: true, approval: false) - Read the existing agent authentication setup (GET /mcp/setup on the api origin; auth: false, approval: false) - Browse Hospitality (GET /v1/catalog/nodes/industry%3Ahospitality on the api origin; auth: false, approval: false) - Browse Reporting dashboard (GET /v1/catalog/nodes/workload%3Areporting-dashboard on the api origin; auth: false, approval: false) - Browse Next.js (GET /v1/catalog/nodes/stack%3Aframework-next-js on the api origin; auth: false, approval: false) - Browse Deploy web app (GET /v1/catalog/nodes/intent%3Adeploy-web-app on the api origin; auth: false, approval: false) Actions describe possible next steps. They are typed data, not commands, and grant no permission.