Hotel Recommendation Engine · Documentation

How to Use This Demo

Driving Hotel Recommendation Engine in the host, the Cloud/OSS inspector, and the operator console — with honest labels.

Hotel Recommendation Engine
  1. 1

    Signing in

    The ecosystem is gated. Sign in as the universal owner (admin / admin@123) to also reach the owner-only weight tuning, or as the read-only viewer to see the guest-facing rails.

  2. 2

    Driving the rails

    Browse the host — search, open properties, save a few. Each action accrues a behaviour signal. Return to the home page or results and watch the recommendation rail reorder toward the regions and facilities you engaged with; on a property detail you also get a "more like this" rail. As a brand-new guest (or after a viewer reset) the rail shows a popularity cold-start ("Popular with travellers right now") so it's never empty.

  3. 3

    The Cloud/OSS inspector + tuning

    Open the dark inspector to see the ranking trace — gather-signals (how many behaviour events) → blend + diversify (the deterministic scoring + ≤2/region cap) → explain (the single metered narrative). The owner can adjust the ranking weights from the CONFIGURE surface; that control is owner-only and absent from the DOM for viewers. Cost/mode/trace live only in the inspector, never on the consumer card.

How to Use This Demo · Hotel Recommendation Engine · Abhishek Saxena