How it fits
Every platform in this category claims one view of the guest. This is the arrangement that actually produces one, and the reason it is hard to retrofit.
A bus, not a stack.
The platform is a set of services around an event bus rather than one application with modules bolted to it. A booking is taken by one service, a Wi-Fi session is authenticated by another, a payment is recorded by a third, and none of them call each other directly.
Each one publishes what happened. A booking created, a session started, an order paid, a review received. Everything that cares subscribes. That is the whole trick, and it is the reason the guest profile is current rather than a nightly reconciliation of six systems that disagree.
Who does what.
The names are internal, but the split is worth seeing, because it explains why adding a module does not require rewriting the others.
A captive portal and RADIUS handle authentication and per-session limits, with the SNAPguard appliance giving each venue a managed tunnel. Every login publishes a guest.
Availability, deposits, pre-orders and the live day-planner. Publishes the booking lifecycle and consumes guest history to show staff who is arriving.
Two-way sync with the till, so spend and line items attach to a guest rather than sitting in a separate report.
Each subscribes to the events that should trigger it: enrol on sign-on, request a review after a visit, re-engage after a lapse.
The record everything resolves to, matched on a real identity key rather than a guess, and stored as a graph so related signals sit one hop apart.
Claims you can check.
Every competitor in the category says “one view of your guest”. The difference between saying it and having it is architectural, and it shows up in questions that are awkward for a point solution: does a Wi-Fi login update the booking record without an export? Does yesterday’s payment change who is in this morning’s segment? Can you leave with your data?
A bus in the middle makes those boring questions rather than roadmap items. It is also why the AI work is foundation-first: a graph where a guest, their visits, their spend and their consent are already connected is the hard part, and it is not something you can add later by putting a language model in front of five disconnected databases.
The homepage draws this live: every section from the hero fan-in to the stage cells is the same event flow, running.