Business Problem & Solution

A hospitality business is not one app — it is a guest-facing booking site, a back-office for partners and operators, and a dozen specialised AI and operations tools that only create value when they share one guest, one booking, and one source of truth. The hard part is not any single feature; it is making forty-four apps feel like one product without each team forking the data model, the design, or the access rules.

Hotel Marketplace is the host #01: the front door guests book through, and the shell every other ecosystem app plugs into. It owns the core entities the whole ecosystem reads — properties, rooms, rate plans, inventory, bookings, guests, reviews — and the shared chrome (navigation, the app launcher, the operator console, the honesty inspector, the sign-in gate). Everything else is a tenant on this host.

It proves the coupling spine works: a single synthetic dataset, one typed adapter, and a live event bus make the connections real — a booking made on the consumer site shows up in the operator console, drives loyalty and recommendations, and feeds analytics, with no app holding its own private copy of the truth.

It simplifies the irreversible, external bits and labels them: payments are a simulated capture (no real PSP), confirmation emails land in an in-app "sent" viewer (no real SMTP), the map is illustrated, and channel-manager sync is mocked. The flow is real end-to-end; only the parts that would move real money or send real messages are faked, and they say so.

Synthetic catalog only — ~1,000+ invented properties across ~12 countries, with generated facilities, photos (placeholder gradients, never real imagery), POIs, reviews, guests and bookings. No real brands, customers, or PII. Figures shown anywhere in this demo are representative and labelled.