SOURCE 01PMS + booking
THE JOURNEY ECOSYSTEM
Connect the stars. Keep their meaning.
Journey works across the systems already around the guest—more than one PMS included—so history, intent, spend, membership, and service can become one useful, governed relationship.
Source-aware values Scoped access Activation by readiness
SOURCE 02OTA + direct
SOURCE 03POS + commerce
SOURCE 04Web + marketing
ConstellationSINGLE UNDERSTANDING
USEFUL OUTCOMEOne profile
USEFUL OUTCOMEPast stays
USEFUL OUTCOMEAssociated people
USEFUL OUTCOMEUseful intent
Illustrative product behavior. Source availability and permitted actions depend on configured integrations, data rights, consent, and access.
Built to connect the systems already around a remarkable stay.
Oracle Hospitality
Mews
Cloudbeds
Hostaway
Guesty
Provider marks identify systems in the hospitality ecosystem. Connection method and availability vary by provider, contract, configuration, data rights, and permissions. Display does not imply universal certification, endorsement, or live activation.
THE SYSTEMS AROUND THE STAY
Connect the stars. Keep their meaning.
Journey creates a relationship layer across the systems a brand already trusts. Each signal keeps its source, scope, freshness, and permission context.
PMS · PROPERTY · STAY
Bring reservation, stay, property, profile, and operational context together across the systems your portfolio already runs.
OHOracle Hospitality
MMews
GGuesty
CCloudbeds
HHostaway
IInfor
TThinkReservations
SPStreamline PMS
HHospitable
COMMERCE · POS · EXPERIENCE
Connect on-property and direct behavior so a guest relationship includes what happened beyond the room.
SShopify
TToast
BEBooking engines
EPExperience providers
JPJourney Pay
CRM · MARKETING · ENGAGEMENT
Carry governed audiences and guest context into the tools teams use to bring the relationship back.
RRevinate
AAscend360
CCustomer.io
EEmail
SSMS
WSWeb signals
Provider names identify systems in the hospitality ecosystem. Connection method and availability vary by provider, contract, configuration, data rights, and permissions. Display does not imply universal certification, endorsement, or live activation.
THE CONNECTION MODEL
Move context through governed doors—not around them.
Use canonical provider paths.
Journey integrates through supported APIs, events, exports, and approved adapters. Browsers do not call secret provider APIs directly.
Resolve without flattening.
Signals retain source, organization, brand, venue, confidence, verification, aliases, and review history.
Permission follows the signal.
Only authorized actors and configured capabilities can use context, and important actions remain visible and reviewable.
MULTIPLE PMS SYSTEMS, ONE GUEST
Portfolio complexity should not make a loyal guest start over.
A hotel group or residence operator may run different systems by property, flag, acquisition, or market. Constellation connects permitted clues into a shared understanding while keeping every source and access boundary visible.
Olivia Chen. O. Chen. An OTA relay address. One relationship.
A verified member email, booking context, prior PMS IDs, and consented first-party behavior can align the records. A masked email remains a clue—not automatic proof.
TRUST IS A PRODUCT FEATURE
Useful context, with boundaries.
Sources stay visible
Useful values retain lineage, freshness, aliases, confidence, and scope.
Access remains scoped
Organizations, brands, venues, permissions, and consent govern what can be seen and used.
Important decisions stay reviewable
AI can synthesize and recommend without hiding rules, evidence, or human control.
CONNECT YOUR HOSPITALITY STACK
Show Journey where the relationship lives today.
We’ll map the relevant systems, source ownership, permissions, and activation sequence before representing any provider as connected or ready.
Applications are curated. Connected features, providers, commercial terms, and activation timing depend on the executed agreement and completed readiness checks.