Hospitality data infrastructure for independent and regional hotel groups. A canonical model, an encoded semantic layer, and adapters for the systems that actually feed the operation.
Meridian sits one layer below the applications a group already runs — the PMS, the channel manager, the CRM, the revenue management system, the booking engine, the loyalty platform — and provides what those applications cannot: a canonical model for hospitality data, an encoded semantic layer for every metric the group reports against, and adapters for the systems that actually feed the operation.
It is not a BI tool. It is the substrate underneath one. When a group builds a dashboard on top of Meridian, the metrics are consistent because the semantic layer enforces them. When the PMS vendor changes an API, one adapter gets updated and every consumer downstream continues working.
It is not a lakehouse. The lakehouse is primitives sold to organisations with internal data engineering teams. Meridian is finished hospitality intelligence, sold to groups whose competitive advantage does not come from operating data infrastructure.
Independent and regional hotel groups at the ten-to-a-hundred property scale. Mixed branded and unbranded portfolios. Enough operational complexity to justify integrated intelligence, not enough scale to justify an in-house data engineering team.
If a group already operates a thirty-person data engineering function, Meridian is not the right fit. They are better served by horizontal infrastructure they can shape to their idiosyncrasies. Meridian is for everyone else.
Three architectural decisions shape every product choice. They are not features. They are the structural commitments that determine whether the platform survives year two.
Meridian is being built in 2026. The canonical layer is in place. The semantic layer and the first source-system adapters are next.
We are currently working with a small number of design partners — hotel groups whose operational reality shapes how the product takes its first commercial form. The partnership is structured: their data, their workflows, and their constraints are what Meridian is being built against, in exchange for early access and a meaningful say in what the first version becomes.
The design partner cohort is small by intention. The groups in it are not beta testers. They are co-authors of a product that will serve groups like them.
For more on the infrastructure argument behind Meridian, read Why Hotel Groups Don’t Need a Data Lakehouse and What Kills Hotel Group BI Projects.
We are selecting a small number of reference partners for Meridian. Independent hotels and boutique groups only. You provide data access. We build, deploy, and document. No budget required — just genuine interest in what this can actually do for a property like yours.