Stampede
Login

General architecture

Every event.Every service.Live.

Seraph, our event bus, carries every booking, login and payment to every service that needs it.

See it live
Wi-Fi
Booking
Payment
Review
Points
Seraph event bus
  • reviews.review.createdreply drafted
  • loyalty_v2.points.createdbalance updated
  • ordering.order.paymentspend on the profile
  • bookings.booking.createdprofile, points, email
  • wifi.session.createdguest captured
On AWS EventBridge
published once, on one bus

Powering 2,500+ UK venues

Art HospitalityNº 90OIR GroupFolkPlonk'dPetiscoSankey'sWild InnsThe StablesCoast & CountrySiam NiyomVietnamese Street KitchenHowiesCaldera
La-YamRadioBuoy & OysterThe Northern CollectiveVittoria GroupAmarettoNo.12 Hotel & BistroThe Truffled HogKneadThe George at BurnhamFifteenOmomoThe Welsh HouseFuego
Valiant Pub CompanyParadise PalmsFat HippoThe BoundaryArtisan InnkeepersFauna BrewingSmoke BBQMount EdgcumbeRocca GroupPotyoOrnithologyRico Libre
The problem

Reconciled, nightly.

Separate systems all day, an export at 2am, and a guest view that is stale by breakfast.

The nightly-sync world
The day trades
Six systems log it
Nightly export
One viewAlready stale
the day trades, the export runs, and the view is a day behind the guest.
How it works

Published once.

One booking reaches four services at the same moment.

New booking
Covers4
Time19:30
Publishesbookings.booking.created
SeraphAWS EventBridge
Guest profileMorpheusProfile updated
Loyaltyloyalty-v2Points accrued
MarketingserviceGuest emailed
ReportingreportsVisit counted
Your next moduleJust subscribes
one booking, published once, four services updated, no export
The services

Who does what.

Each module publishes what happened. The rest listen.

Trinity

Guest Wi-Fi

wifi.session.created
Zion

Bookings

bookings.booking.created
Neo

Payments

ordering.order.payment
loyalty-v2

Loyalty

loyalty_v2.points.created
Tank

Reviews

reviews.review.created
inbox

Inbox

inbox.thread.created
Morpheus

Guest profile

merges every event
service

Marketing

triggers on events
SeraphThe bus between them
Why it matters

Claims you can check.

The bus turns them into boring questions.

No exports

Live, not nightly.

A Wi-Fi login reaches the guest profile the moment it happens. No 2am sync.

Real time

Spend moves segments.

A payment lands on the profile, so it counts in the next segment.

Your data

Yours to take.

One record per guest, held by you, not a booking network.

What’s next

Foundation first.

AI needs connected data before it needs a model. The bus is how ours got connected.

See what we shipped