Travel operators: public directory using Next.js · Ample Computer
Travel operators: public directory using Next.js
A public directory 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; state_transitions (record_type, from_state, to_state): the allowed state machine. 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: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).
What it runs on
Computeverified Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
Postgresverified 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.
CDNverified A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.
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 createpassed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*) - A review of which travel operators 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
Model the travel operators domain. Create the tables listings, agencies, suppliers, reports, state_transitions. 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.
Workflow step 1. Model listings with a publishing_status state machine scoped to the agency.
Workflow step 2. Serve only published listings, with media from the CDN bucket.
Workflow step 3. Enforce the agency scope on every query.
Workflow step 4. Deploy and verify a published listing and that unpublished listings are absent.
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=... --env CDN_PUBLIC_URL=...
- Verify. Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the travel operators workflow.
$ ample logs <deployment_id> --kind build
How it was checked
✓ app responds on its public URL http get/ → “ample canary next js patterns”
✓ relational-records self-test from the example http get/p/relational-records → “see the pattern fixture checks”
Evidence
- 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 relational records checks passed: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). The blueprint's Travel operators schema and workflow below build on that verified basis.
Tested examples
- Next.js pattern fixture. Verified relational records basis for this blueprint.
What it doesn’t cover
- The technical basis (relational records on Next.js) was verified with the pattern fixture; the travel operators schema and workflow are an original design for this blueprint, built on that basis.
- Passport and payment data are regulated; only published trips and branch 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-urlreturns presigned upload URLs.