Walk into the back office of almost any hotel and you’ll find the same thing: a PMS that thinks it owns the guest, a POS that thinks it owns the check, an RMS that thinks it owns the rate, and a row of spreadsheets quietly reconciling the gaps between them. Each system has a model of the business. None of them agree.
Integrations are supposed to fix this. In practice they move data without moving meaning. A reservation copied from one system to another is still two different reservations, governed by two different sets of rules, drifting apart the moment either side changes.
The model is the product
Aerandil’s bet is that the meaning should be the thing you build, not a byproduct of the apps. Declare the operation once — as typed objects, the links between them, the actions that can change them, and the events those changes emit — and every surface reads from the same source of truth.
- A reservation is one typed object, connected to a person, a room type, a rate plan, a stay, and a folio.
- The rules for how it can change live with the object, not scattered across screens and scripts.
- Every change is recorded as an immutable event, so the history of the operation is a fact you can query and replay.
Configurable, not prescriptive
Modelling once doesn’t mean forcing every property into one shape. The ontology is a superset: a boutique inn uses a small slice of it; a multi-brand group uses the same core contract at portfolio scale. Available, not mandatory.
That’s the foundation everything else — apps, automation, intelligence — finally gets to stand on.