Hospitality: Public Directory using Next.js

Summary

A public directory 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; state_transitions (record_type, from_state, to_state): the allowed state machine. 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: 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

• Hospitality: public directory using Next.js
• Where can I host Hospitality: Public directory built with Next.js?
• I need a genuinely specialized public directory workflow covering property listings, service vendors and occupancy-related reporting.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:cdn

Infrastructure Requirements

1. Compute: 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: 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: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

Framework

Next.js

Workload

Public directory

Industry

Hospitality

Execution Status

Ready

Validations

Success Checks

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

Limitations

• The technical basis (relational records on Next.js) was verified with the pattern fixture; the hospitality 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. Guest identity documents are sensitive; only availability and booking status are modeled here.