The guest data layer.
One Master Profile under your PMS, POS, booking, and OTA systems, not locked inside a suite you also buy campaigns from.
The guest identity layer under the stack a hotel already runs.
Every guest,remembered.
One Master Profile under the stack you already run. Desk, CRM, and agents read the same guest. Not another AI tool.
The systems you already run
- Book4Time
The layer everything runs on.
Casa Layer is the guest identity layer under the stack you already run: one Master Profile, open to every tool and agent that needs it.
Any agent runs on it.
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.
Separate from every tool.
Replace your CRM or your PMS and the resolved record is untouched. Your team, your CRM, and any agent read the same Master Profile.
Built for rigour, not just resolution.
- Identity Resolution
- Open API
- Mechanical Attribution
Not another CDP
Attachment is not identity.
A CDP bolted into another product is that product's filing system, not your guest spine. Activation is real work. Identity is different work. If the richest view of the guest only deepens inside one suite, you bought attachment, not a record that travels. Casa Layer is the guest identity layer under the stack: one Master Profile tools and agents can act on, so hotels get the guest relationship back.
Connects to the systems you already run.
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, Square (Bookings).
One infrastructure. Every department has a reason.
IT / CTO
An open API across your existing stack, so agents and desk tools read the same Master Profile, with a consent ledger and audit-ready lineage from day one.
Operations Director
Casa Layer does the connection work, so you go live without standing up a data team.
General Manager
A complete profile at check-in, without asking questions the guest has answered before.
Commercial Director
Performance tracked against real folio charges, not a vendor’s black box.
The questions we hear first.
How long does it take to go live?
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.
Do we have to replace any of our systems?
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.
Who holds the Master Profile?
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 under your stack rather than inside one vendor's suite, 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.
What happens if we cancel?
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.
How do agents connect to the layer?
Agents and desk tools read the same Master Profile over an open 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.
How is guest consent handled?
Every Master Profile carries a full GDPR and CCPA consent ledger: lawful basis, capture date, marketing opt-in and retention period, recorded per guest.
Is Casa Layer only for hotel groups?
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.
How is it priced?
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.
If your guests come back, we’d like to talk.
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.