# Travel operators: reporting dashboard using Next.js

## Summary

A reporting dashboard blueprint for travel operators built with Next.js on Ample. Domain schema: listings (reference, destination, departure_dates, price_from, publishing_status, agency_id): trips as listings with publishing status; agencies (name, license_number, region): operators or branches; suppliers (name, type, agency_id, status): hotels and transport suppliers; reports (agency_id, period, object_key, generated_at): branch sales reports; exports (id, definition, object_key, row_count, generated_at, authorized_role): generated artifacts and who may download them. Public information: published trips and departure dates, destination guides, booking conditions. Kept out of scope until handling is reviewed: traveler passports and identity, payment details, supplier contracts. Passport and payment data are regulated; only published trips and branch reporting are modeled. 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).

## Infrastructure requirements

- **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:** 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:** 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 travel operators 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 travel operators domain.** Create the tables listings, agencies, suppliers, reports, exports. Trips as listings with publishing status lives in listings; keep the sensitive classes (traveler passports and identity, payment details, supplier contracts) 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 travel operators workflow.
   
   ```
   ample logs <deployment_id> --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)

## Limitations

- The technical basis (generated downloads on Next.js) was verified with the pattern fixture; the travel operators 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. Passport and payment data are regulated; only published trips and branch reporting are modeled.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.
- Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
- PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

## Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).
- 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-dirty (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 Travel operators 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