Skip to content
Login

General architecture

Every event. Every service. Live.

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

See it live
Wi-Fi
Booking
Payment
Review
Points
Event bus
  • Review postedreply drafted
  • Points earnedbalance updated
  • Order paidspend on the profile
  • Booking madeprofile, points, email
  • Guest connectedguest captured
Real time, every service
published once, on one bus

Powering 2,500+ UK venues

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

Reconciled, nightly.

Six systems all day, one export at 2am, a view stale by breakfast.

Saturday night, one guest

Before

Synced · 02:00
Nightly export02:00
6 systems into one sheet
Guest viewAlready stale
Sarah MitchellLast in: Thursday
Tonight’s table: not yet
Wi-Fi login · 19:02Lands tomorrow
  • Separate systems log the day on their own
  • An export at 2am to join them up
  • A guest view a day behind the guest

After

Live · 22:15
One profileVIP
Sarah MitchellEvery venue
Visits15
Spend£1,382
Last inTonight
Tonight, as it happenedWi-Fi login19:02Booking seated · table 1219:30Square bill paid22:15
Nut allergyMargarita on arrivalTable 12
  • Each module publishes what happens, once
  • Every module that needs it listens, as it happens
  • Her record current to the last thing she did
Same guest, same night. The difference is whether her record waits for 2am.
How it works

Published once.

One booking reaches four services at the same moment.

New booking
Covers4
Time19:30
PublishesBooking made
Event busReal time
Guest profileListensProfile updated
LoyaltyListensPoints accrued
MarketingListensGuest emailed
ReportingListensVisit 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.

Publishes

Guest Wi-Fi

Guest connected
Publishes

Bookings

Booking made
Publishes

Payments

Order paid
Publishes

Loyalty

Points earned
Publishes

Reviews

Review posted
Publishes

Inbox

Message received
Listens

Guest profile

merges every event
Listens

Marketing

triggers on events
Event busThe 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