Hotels run on screens. The screens run the day: arrivals at the desk, the room board after checkout, the group block eighteen months out, the audit that closes the business date. Ithaca is Aerandil’s PMS — the property management system, built on the same governed ontology as everything else we ship.
Ithaca is Odysseus’s island: the place at the end of the journey. A hotel is where a traveller arrives and rests, and the front desk is the door they arrive through.
Task-shaped, not schema-shaped
Explorer, our operator console, is deliberately generic: it renders whatever the ontology says, every object and action, and it will always ship first. Ithaca is the opposite instrument. It is purpose-built for the flows a front desk, reservations office, or night auditor actually runs — fewer screens, each shaped to a job, none of them asking an operator to think in schemas.
The two share one spine. Every Ithaca screen writes through the same typed, permissioned, validated actions as Explorer, the API, and every agent. There is no privileged path for our own application — if Ithaca needs something the ontology lacks, the ontology grows, and every integrator gets it too. The audit trail stays total.
The front office, whole
Ithaca covers the property side of the day end to end: arrivals, departures, and walk-ins; folios, postings, and the night audit; housekeeping and maintenance; and groups & events — blocks, function sheets, and banquet event orders on the same spine as rooms.
It does not run the restaurant or the bar. That is a different day — the book, the floor, the pass, the stockroom — and it gets its own product, our F&B system, from the booking to the stocktake. The seam between them is the folio: a guest’s room charge rung at the bar posts to Ithaca through the platform’s public contract, the same governed action any integrator could call. One guest, one folio, two instruments.
In build, with design partners
Ithaca is in build. The kernel substrate and the console exist; the first screens are being scoped now against a coverage audit of what independent properties and small groups actually need. Design partners shape which screens land first — and their desk and audit realities are the specification.
If you operate a complex, multi-system hospitality business and want the PMS built around your day, request a design-partner briefing.