Two surfaces, one record
Stampede has two product surfaces. Operations is what the team uses to run the venue. Experience is what guests see. They draw from the same Guest Profile underneath. Read /docs/operations and /docs/experience next.
The Guest Profile is the spine
One identity-resolved record per guest, per organisation. Phone, email and Wi-Fi MAC fold into one Customer node — deterministically, with named edges, not a probability score. Visit /docs/guest-profile to read how it resolves.
Bookings, Wi-Fi, Orders, Reviews, Loyalty
The five product modules that capture signal. Each is documented as a sub-page under Operations. Each writes to the Guest Profile.
Marketing CRM closes the loop
Segments built over the profile drive campaigns; campaign responses (open, click, bounce) write back to the profile as edges. The loop closes on the same node it started from.
AI reads the graph
The assistant reads the live profile and proposes writes — segments, campaigns, replies. Every AI write is human-approved. Visit /docs/ai to see the surfaces.
Done. From here, the natural reading order is the four pillar overviews above, then the schema explorer at /docs/reference/schema.