Independent in everything — except the tech stack.
A hotel runs on systems it chose but can't direct. A new guest flow, a quick experiment, a report that doesn't exist yet — each one lands as a vendor project, on their roadmap, their timeline, their price. Most never clear the queue.
So the effort flows backward. Instead of building what's next, the hotel spends itself closing the gaps its systems leave— and every workaround hardens into process. Over years, the operating model isn't the one the hotel designed; it's the one the integrations allowed.
The cost isn't a line item. It's control. What a hotel can do is set by what its systems permit — and every gap is a call made by a vendor, not the hotelier.
Standards have been tried.
Influences, not dependencies — each moved the industry; none shipped a running backbone.
Message standards for travel distribution — broad and early, but from an older era of the web and taken up unevenly, so a hotel could never assume two of its systems spoke the same one.
Working specifications for hotel-technology connections — practical, but each vendor built the parts it chose, one connection at a time, so integration stayed a per-project cost for the hotel.
A unified hospitality data model — a strong shared vocabulary, but one that lived on paper: no running backbone to carry it between a hotel’s systems.
The industry should shape the stack — not the other way around.
Everything here exists to flip one arrangement: today the hotel adapts to its vendors; Serai makes the vendors adapt to the hotel. Hotels keep what works, replace what doesn't, and build what's missing — on a common layer no vendor can take away.
Nothing to get locked into.
What a hotel keeps, no matter what happens to any vendor — including this one.
Every connector is replaceable and the model is documented — a hotel can adopt one connection, extend it, or walk away. Leaving is a configuration change, not a migration project.
The core is being built to become an open standard — released under Apache-2.0 at the published maturity gate, with governance handed to the industry rather than kept by any one company.
Schemas, mappings, and routing rules are inspectable, documented, and versioned. Nothing proprietary sits between a hotel and its own events.
The layer translates and routes — it is never a system of record. Data keeps living in the systems the hotel already owns, reachable through one feed.
See how the commons gets handed over.
The whole point is a layer the industry keeps. Read how governance transfers at a published gate — or walk the architecture with the team.