Aerandil builds the systems a property runs on, from the front desk to the restaurant to the bill, all on one governed record of the operation. Ithaca, our property management system, is the first.
No customer figures yet; these are the product's own rules and our own measurements. The first design partners' numbers go here when they exist.
A property runs a PMS, a point of sale, a channel manager, a payment terminal, a housekeeping sheet and a spreadsheet for whatever is left. Each one invents its own guest, its own room and its own bill. The desk re-keys between them, and the record of what happened lives nowhere.
Arrivals, departures, housekeeping from a phone, the money in both directions, and a night audit that says what is in the way. Built one screen at a time, against a hotel with guests in it.
Demonstrable today, with its first hotels; not yet generally available.
Counted from the registry, not the brochure. Regenerated with every schema change.
Ithaca has no private door. Every board writes through the same typed, permissioned, validated actions the platform exposes to any integrator, SDK or agent. The audit trail is not a feature of the product. It is the only way anything gets written.
Explorer, the platform's console: every object, link, action and event in the ontology, live.
The ontology, the engine, the contracts. Forge ->
A design partner does not start by switching systems. Connectors read what the property already runs, and the model fills from the record as it stands.
Every sync run is an audited object in the same ontology it feeds. How ingestion works ->
An agent's tools are ontology operations: typed, permissioned, validated, audited. When confidence is low or the stakes are high, the agent proposes and a person confirms.
# a governed action — not raw database access POST /v1/actions/apply → validate → event # one path: the desk, an integrator, an agent
Our flagship agent lives by these rules. Meet Talos ->
Answers checkable in the product or the docs. The rest is a conversation.
One governed model of a hotel's operation: the guests, rooms, bookings, bills, staff and suppliers, and every change to them, made through a typed, permissioned action and kept on an append-only record. Our products are built on it. Your own systems connect to it through the same contracts.
Our property management system: the front desk from arrivals to the night audit, a phone app for housekeeping and maintenance, and payments on the same bill as the stay. It is in early access with its first hotels, demonstrable today and not yet generally available.
Apply on the design partner page. You get three times for a fifteen-minute call straight away; after it we shadow your property from your current system, you run a private demo on your own data, and go-live is rehearsed before the night. The first three months are at cost.
No. Connectors read what the property already runs and the model fills from the record as it stands. Switching is a later decision, and when a hotel makes it we rehearse the cutover against its own data before the day.
An agent's tools are the same actions the desk uses, with the same permissions, validation and audit. Where the stakes are high or the confidence is low, the agent proposes and a person confirms. Nothing is written any other way.
In vanilla Postgres, portable to any host. With Proxima it runs in a single-tenant cell of your own, in the region and jurisdiction you choose, with residency enforced by the model rather than by policy.
Ithaca is priced per room per month, with no setup fee. The figure is agreed with design partners during early access and published at general availability.
Forward deployed
Aerandil is in private development. The first hotels run Ithaca with us on site, as design partners, and their day shapes what the model learns next. A private demo is where that starts: we set up a hotel shaped like yours and work the day with you, live.
Book a private demoPrivate demos run live, over a video call. Design partners are chosen from them.
