Travel operators: public directory using Next.js

Family: Industry blueprint
Summary: A public directory blueprint for travel operators built with Next.js on Ample. Domain schema:

• Listings: Trips as listings with publishing status; includes fields for reference, destination, departure dates, price from, and publishing status.
• Agencies: Operators or branches with fields for name, license number, and region.
• Suppliers: Hotels and transport suppliers with fields for name, type, agency ID, and status.
• Reports: Branch sales reports with fields for agency ID, period, object key, and generated at.
• State Transitions: The allowed state machine with fields for record type, from state, and to state.

Public information includes published trips and departure dates, destination guides, and booking conditions. Sensitive data such as traveler passports and identities, payment details, and supplier contracts are out of scope until further review.

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).

Representative Queries

1. Travel operators: public directory using Next.js
2. Where can I host Travel operators: Public directory built with Next.js?
3. I need a genuinely specialized public directory workflow covering tour listings, supplier access and itinerary reporting.

Resource Requirements

• Compute
• Postgres
• CDN

Infrastructure Requirements

1. Compute

   • Status: Verified
   • Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

2. Postgres

   • Status: Verified
   • Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

3. CDN

   • Status: Verified
   • Summary: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

Workflow Steps

1. Model the travel operators domain: Create the tables listings, agencies, suppliers, reports, state_transitions.
2. Model listings with a publishing_status state machine scoped to the agency.
3. Serve only published listings, with media from the CDN bucket.
4. Enforce the agency scope on every query.
5. Deploy and verify a published listing and that unpublished listings are absent.
6. Run the synchronous deploy once and read the result.
7. Run the pattern self-test(s) from the example and your own acceptance checks for the travel operators workflow.

Examples

Next.js pattern fixture: Verified relational records basis for this blueprint.

Success Checks

1. App responds on its public URL.
2. Relational-records self-test from the example.

Limitations

• The technical basis (relational records on Next.js) was verified with the pattern fixture.
• No health, financial, privacy or other compliance claim is made.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Components:
  • App server (s-1vcpu-1gb): $5.00
  • Managed PostgreSQL database (s-1vcpu-1gb): $5.00

Evidence Summary

• Next.js pattern fixture deployed on Ample; the relational records checks passed: a verified basis and were not separately executed.

Last Verified At

September 21, 2026.

Next Actions

1. Browse the catalog index
2. Search published recipes by intent, stack and constraints
3. Prepare a side-effect-free deployment plan for an authorized project
4. Read the existing agent authentication setup
5. Browse Travel operators
6. Browse Public directory
7. Browse Next.js
8. Browse Deploy web app