One language for the systems that run hotels.
Serai is a shared model built for an industry patched up together one integration at a time. Serai is being built to become an open standard — not another dependency.
The wiring runs the hotel. Not the hotelier.
Hotel systems were never designed to work together. So staff re-type what the systems should be telling each other. And changing any vendor is a project so painful it never happens.
The experiences a hotel wants to build — for guests, for colleagues — die because the stack has no way to carry them.
The cost isn't a line item. It's control.
One wire per system, not a web of point-to-point integrations.
Every system gets one wire to a shared model instead of many wires to each other. Systems in place stay in place; replace one and the others never notice — and for the first time, the stack follows the hotel's design, not the vendor's.
What a shared model every system brings.
Decoupled systems
Replace a system and the others never notice; vendor roadmaps stop deciding what a hotel can do.
Message analysis
Every message across every connection, on record and searchable: the first honest view of what the systems actually say to each other.
Real-time intelligence
An ordered, live event stream; cross-system and cross-property views built on live data, not month-end exports stitched by hand.
Mini apps
Focused apps on the shared model: guest flows, upsells, colleague tools — launched without waiting on a vendor's roadmap.
Custom translations
Amend and enrich data in flight, by rule: order what arrives out of sequence, anonymize a guest's name to the spa system, inject what a legacy POS can't carry. Only where the hotel says so.
Business routing
Route by rule: hold a message set until it's complete, sequence what a source system won't, send each event where it belongs.
The standard, the platform, the connectors.
One universal connector engine plus per-integration configuration; delivery direct connector-to-target, with an event feed, and apps to build on. The model translates and routes — it is never a system of record.
One canonical model, versioned additively.
The Linked Commons Model is the canonical data and event schema of the Serai Project — the shared language every certified connector normalizes to.
{ "specversion": "1.0", "type": "lcm.reservation.created", "source": "//serai/connector/pms01/prop-001", "lcmprovenance": "pms01", "data": { "snapshot": { "status": "confirmed", "arrival": "2026-08-01", "departure": "2026-08-04", "total": { "amount": 742.5, "currency": "EUR" } } } }
Watch, translate, act — at the hotel's pace.
Every step is small, and every step is reversible.
Mirror or pass-through — nothing altered, the layer observes.
Systems speak the shared model — connect anything.
Custom rules amend and route — only where the hotel says so.
Open-sourcing happens at a published gate — not at anyone's discretion.
Apache-2.0 release of the versioned LCM spec, the connector engine, and the connectors — and transfer to the Serai Foundation, an independent, vendor-neutral body, under a charter drafted and public before the gate is reached.
Built in the open, reported honestly.
A bi-weekly project update — progress, connectors, partners, slippage. All plainly stated.
Start with an intro session.
One session with the team: walk the architecture, map how a property, a product, or an integration fits the model, and decide together whether to go further. Operators, vendors, integrators, contributors — all welcome.