One Master Profile, resolved across every system, sitting above all of them, and open to every agent that runs on it.
The systems you already run
One Master Profile, separate from every system that feeds it. PMS, POS, booking and OTA bookings resolved into a single profile per guest, with confidence scoring. Agents query it over MCP; everything else over an open REST API. Full GDPR and CCPA consent ledger.
The agents change every year; the layer they run on does not. Claude, a revenue agent, a concierge assistant, or your own: every agent reads the same Master Profile and goes live in three weeks, not six months. Revenue is attributed to the folio charge it produced.
Not held inside an operational system, and not shaped to suit a product we sell, because we sell none. Replace your CRM or your PMS and the resolved record is untouched. Your team, your CRM and any agent read the same Master Profile, and you can delete any guest from it at any time.
Your PMS, point of sale, booking engine, spa and OTA bookings, connected by our engineers under credentials you issue and can revoke. Nothing to rip out, nothing to replace, and no data team to stand up on your side.
See every integrationSystems shown here include Apaleo, Clock PMS, Cloudbeds, Guestline, Mews, Oracle OPERA, Protel, Stayntouch, Lightspeed, Toast.
An open REST API and MCP server across your existing stack, with a consent ledger and audit-ready lineage from day one.
Casa Layer does the connection work, so you go live without standing up a data team.
A complete profile at check-in, without asking questions the guest has answered before.
Performance tracked against real folio charges, not a vendor’s black box.
Three weeks from kickoff, not six months. Our engineers do the connection work, so you do not need a technical person on your side, and there is no data team to stand up.
No. Casa Layer connects to the tools you already run (PMS, POS, booking engine, OTA bookings), and where a system has an API your vendor switches on access for your own account, scoped to what you have approved. Nothing is ripped out and nothing is scraped.
Casa Layer builds it and holds it, so we will not tell you the record is yours the way most of this category does. What is true is that we sell no applications on top of it, so there is nothing here for it to be locked inside and nothing shaping it to suit a product of ours. It sits above your systems rather than inside one of them, so replacing your CRM or your PMS does not cost you the resolved record. Your own systems stay the record throughout, you can delete any guest at any time, and if you cancel, every copy is deleted from our systems 30 days after cancellation.
Access ends and every copy is deleted from our systems 30 days after cancellation. Your own systems stay the record throughout, and revoking the credentials you issued closes everything we can reach, so nothing has to be unwound.
Agents query the Master Profile directly over an MCP server; everything else reads it over an open REST API. Claude, a revenue agent, a concierge assistant, or one you build yourself: every agent works from the same profile. An agent that can only read can only advise, so we are building write access too, granted system by system by you. Every connection live today reads only.
Every Master Profile carries a full GDPR and CCPA consent ledger: lawful basis, capture date, marketing opt-in and retention period, recorded per guest.
No. The question is whether your guest history is scattered across systems, and whether you have agents or a team that need one version of it. An independent hotel with high-value returning guests has that problem as squarely as a group of twenty does. Most of our work today is with mid-market groups, and we are taking on a small number of partners for the first chapter, so we are deliberate about who we work with.
A flat annual platform licence per property, with every system you connect included. What you pay depends on how many properties you run and which tier you need: the data platform on its own, or the data platform plus the controls for running agents on it. We will give you the number on the first call, not after three.
We’re choosing a handful of partners for the first chapter. If your guest data is scattered across systems, or your agents need something solid to run on, book a demo and we will map it to your stack.
