page:blueprints:hospitality:vendor portal:next js

Hospitality: Vendor Portal Using Next.js

Summary

A vendor portal 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;
• document_access (document_id, principal_reference, role, granted_at): who may read which document.

Public information includes room types, amenities, rates, property location, policies, events, and dining. Guest identity documents and payment details are kept out of scope until handling is reviewed.

Resource Requirements

• Compute
• Postgres
• S3-compatible object storage

Infrastructure Requirements

1. Compute
   • 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
   • 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. S3-compatible object storage
   • Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Workflow Steps

1. Model the hospitality domain: Create the tables room_types, inventory_movements, bookings, booking_lines, document_access.
2. Model vendors scoped to the agency with roles.
3. Authorize document access by vendor and role (401, 403 negative tests).
4. Store vendor documents in the private bucket.
5. Deploy and verify the negative tests and an authorized download.
6. Run the synchronous deploy once and read the result.
7. Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the hospitality workflow.

Success Checks

• App responds on its public URL.
• Private-document-library self-test from the example.

Limitations

• The hospitality schema and workflow are an original design for this blueprint and were not executed as a separate application.
• Verified on the node-22 template.

Cost Estimate

• Monthly Amount: $10.00
  • Basis: Size prices from pricing.toml at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty.
  • Components:
    • App server: s-1vcpu-1gb - $5.00
    • Managed PostgreSQL database: s-1vcpu-1gb - $5.00

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 Hospitality.
6. Browse Vendor portal.
7. Browse Next.js.
8. Browse Deploy web app.