AI is everywhere in hospitality right now. Every demo promises hyper-personalization. Every pitch deck includes “agentic AI”. Every roadmap includes predictive something.

But here’s the uncomfortable truth:
AI doesn’t fail because it isn’t intelligent enough. It fails because the data layer underneath it is chaotic, fragmented, and poorly governed.

Before you talk about magic, you need plumbing. And plumbing isn’t glamorous... but it’s what keeps the building standing.

Our platform handles the plumbing. We do three big, unglamorous, absolutely essential things:

1. Streams (The One-Way Trip In): We take the reservations, the guest profiles, the stay history, and the ridiculous rate codes from a stack of different PMSs (plus the odd spa or table system) and make it all normal. Then we fire it out, fault-tolerant and portfolio-wide. You get to know what’s actually happening across your properties, and when, instead of playing guessing games.

2. Actions (The Other Way Out): This is the heavy lifting. One clean API to post charges, handle payments, check people in/out, and run all 60-odd critical endpoints across Oracle, Shiji, HotelKey, and their friends. You call us; we route it. It just works. That’s the entire job.

3. Data Platform (The Landing Zone): It’s not some fluffy "data lake," and it’s certainly not a mystical CDP. It’s just a pragmatic, dependable space where all that streaming data lands, syndicates, and gets sliced for analysis without requiring weekly archaeological digs.

Put those pieces together, and yes, we are a phenomenal enabler of AI. Discovery, hyper-personalization, service recovery, revenue ops—the whole toy box is right there, teed up and ready to go.

But as Uncle Ben said to Spider-Man, with great power comes great responsibility.

The Entanglement Problem

An AI that can identify a hotel from a fuzzy caption? Great. One that finds a guest’s own reservation from a name and a vague date? Helpful. An API that fetches post-stay information based on a valid confirmation number? Incredibly useful.

Chain those utilities carelessly—and trust me, someone will—and suddenly, some kid in a basement is using your clever AI to rebuild a guest's entire folio, complete with home address, payment details, and a neat diary of what they did on property.

That’s not innovation. That’s regulatory malpractice.

Chaining is where things go sideways. One API call is almost never the problem; it’s the second one that follows, or the next.  Maybe it's the logic that says, “hey, while you’re here, you might as well…” That’s how small conveniences turn into catastrophic violations.

Smart systems need limits that separate adjacent capability from reckless entanglement.

Booking is consent to buy; post-stay is consent to expose. Full stop. These functions require different authentication, different scopes, and different security layers for a reason. Crossing those wires isn't a clever technical shortcut; it's how you swap a minor API convenience for a major, headline-grabbing helmet fire—explaining to an angry regulator why your AI exposed a thousand guest profiles along with their home addresses.

House Rules for Building with Adults

If you’re building with us (or frankly, with anyone in this industry), you need to internalize a few house rules:

• Capability Isn’t Consent. Because your AI can fetch a full guest profile doesn’t mean it may. If the guest didn't explicitly authorize that scope, you've overstepped.

• Separate Intents. The purpose of the user's interaction must match the data you touch. “Find a vibey hotel for the weekend” should end in a booking, not a data pull on every profile that appears in the search results.

• Least Privilege, Real Auth. Forget your mood board. Use tokens and scopes that exactly match the journey being taken. Anything more is a gaping security hole.

• Audit Everything. If you can’t replay the sequence of events and the data fields touched, you didn’t control it.

APIs don’t grant responsibility; they assume it.

Use the power well, and you’ll ship magic. Use it sloppily, and you’ll ship a breach.

‍