Serai
Why

Independent in everything — except the tech stack.

A hotel doesn't get to do what it wants with its own stack. New flows, new guest experiences, quick experiments — each one is a vendor project on their roadmap, their timeline, their price. So it doesn't happen.

The effort flows the opposite way: staff manually fixing what the systems fail to share — re-typed reservations, mismatched folios, reports stitched by hand. Patching instead of building, at every property, every day.

The cost isn't a line item. It's control: what a hotel can do today is decided by what its systems allow.

so it doesn't happen
patching instead of building
Prior art

Standards have been tried. Credit where due.

Influences, not dependencies — each moved the industry; none closed the loop.

OpenTravel

Message standards for travel distribution — broad and early, but request/response-era and adopted unevenly across hotel systems.

HTNG / AHLA

Workgroup specifications for hotel technology seams — practical, but implemented à la carte by vendors, seam by seam.

UHDM

A unified hospitality data model — a strong shared vocabulary, without a running backbone to carry it between systems.

What's different

Nothing to get locked into.

What a hotel keeps, no matter what happens to any vendor — including this one.

No lock-in

Every connector is replaceable and the model is documented — a hotel can adopt one seam, extend it, or walk away. Leaving is a configuration change, not a migration project.

A path to open source

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.

No black box

Schemas, mappings, and routing rules are inspectable, documented, and versioned. Nothing proprietary sits between a hotel and its own events.

The hotel’s data stays the hotel’s

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.

The point

The industry should shape the stack — not the other way around.

Everything here exists to invert the arrangement: hotels keep what works, replace what doesn't, and build what's missing — on a common layer no vendor can take away.