Hapi launches Guest Identity and Data Lakehouse
Hapi announced Hapi Guest Identity and Hapi Data Lakehouse on 1 October 2026. The Miami-based connectivity vendor built both products to resolve the same guest across systems that hold different versions of that person, and to give the resolved record a governed home.
The company calls the pair its first major product initiative since it stepped back from the CRM space and moved Hapi Guest CRM to sister company Aquiva, a consulting and engineering firm with Salesforce expertise.
How the identity layer decides a match
Hapi Guest Identity matches deterministically on verified shared identifiers. The examples the release gives are an email address, a phone number, or a loyalty ID paired with a name.
When two records disagree, Hapi decides which value takes precedence and keeps the original source records intact. The company states that it will not create a profile unless it is confident in the match.
The output is a golden guest record built from sourced guest information.
The same guest can appear differently in the PMS, the restaurant system, the spa, the loyalty programme, the survey platform and other tools, so each system holds a partial view of one person.
Guest Pop puts the record beside the front desk
Hapi Guest Pop is a browser extension for staff on property. It surfaces the known guest inside applications an employee already has open, including the PMS.
The release states that recognition starts at check-in and continues through the stay. Staff do not toggle between systems or add another application to the workflow.
The lakehouse underneath
Hapi Data Lakehouse normalizes reservation, guest, stay and folio data from connected systems into one hospitality-specific data model. The release calls it the governed foundation that makes identity resolution possible.
Data sits in open formats. Hapi's own product page names Apache Iceberg and Parquet, held in Hapi's managed environment, partitioned and segmented by customer. Hotels can pull their history through APIs or take a full export to their own cloud storage.
Access is the hotel's decision. The release states that hotels determine which systems and technology partners can read and activate against their data, and that the same foundation can feed a CDP, a CRM, business intelligence or an AI tool.
Hapi's own page adds two operating details. Live supply refreshes on 15-minute micro-batches, and near real-time APIs serve anything that needs to move faster. The page states that the hotel brand owns the first-party data.
Segredo on the cost of getting it wrong
"The hospitality industry has talked about the golden guest profile for years, but the real opportunity is what hotels can do once they have one they can trust," said Luis Segredo, founder and chief strategy officer at Hapi.
"Getting an identity wrong in a marketing email may be a minor mistake. Getting a guest's name, loyalty status, or preferences wrong during the stay can undermine the experience in a much more meaningful way."
The vendor's scale figures
Hapi states that more than 100 systems are connected and in production across 15,000 hotels. Hapi's own Data Lakehouse page breaks the connectivity claim into 27-plus property management platforms and 100-plus systems.
The day-use read
A day-use block sells hours, and it puts a guest in front of a desk without an overnight record behind them. Identity resolution built on an email address, a phone number or a loyalty ID paired with a name works from identifiers a day-use booking already collects.
Guest Pop's check-in surface is the same desk position that hands over a key for a four-hour slot. Folio-level data in the lakehouse is where a block charge would land, and the hotel decides which partner can act on it.