Property management systemEarly access

The hotel, modelled once.

For independent hotels and small groups.

Aerandil keeps one record of the hotel: the guests, the rooms, the bookings and the bills, and who changed what, when. Every screen and every system works from it. Ithaca, our property management system, is the first product built on it, and it launches first.

Book a walkthrough See how it's built

Live on this page: a Saturday at Alderline Pendrake, a 44-room resort that does not exist, its bookings and dinner bills from our calibrated demand generator, replayed through the same model. Hover a room for its stay.

Alderline Pendrake · 44 rooms · syntheticSat 31 Oct · 06:00

No customer logos yet.The product is on this page, live.A few design partners run it with us first.

The problemWhy a model

Hotels run on systems. Operators run between them.

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.

The old modelEvery application rebuilds the hotel. Business rules drift into screens, scripts and spreadsheets, and no two systems agree on who is in room 108.

The Aerandil modelModel the operation once. A reservation is a typed object connected to a person, a property, a room type, a rate plan, inventory, a stay and a folio, with rules governing how it can change.

Launching firstProperty management · early access

Ithaca runs the desk.

Arrivals, departures, housekeeping from a phone, the money in both directions, and a night audit that says what is in the way. Built for independent hotels and small groups, one screen at a time, against a hotel with guests in it.

A minute at the front deskRecorded on Ithaca itself. The guests are made up; every click is the real product.

01Check-in in one dialogRoom, arrival time and card guarantee confirmed together, then the guest is in. No “Are you sure?” in front of the guest.

02Rooms ready the moment they're cleanHousekeepers finish a room on their phone and the desk sees it ready straight away. A fault found in a room goes straight to maintenance.

03An audit that says what's in the wayGuests who never arrived and departures still in house are listed before the close starts, with a preview of exactly what it will post.

04Mistakes reversed, never erasedEvery check-in, charge and payment records who did it. A wrong charge is reversed rather than deleted, so the history always adds up.

Demonstrable today, with its first hotels; not yet generally available.

Take the self-guided tour More about Ithaca ->

The model, in numbers

176Object types

397Link types

376Actions

43Domains

2,389API operations

Counted from the registry, not the brochure. Regenerated with every schema change.

Under every screenForge, the platform

One model under every screen.

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.

Aerandil Explorer — the reservation ledger of a live property, with the object catalogue on the left and the live event feed on the right

Explorer, the platform's console: every object, link, action and event in the ontology, live.

Typed operationsObjects, links, actions and functions carry declared contracts. The model is executable, not a diagram.

Governed changeEvery mutation is permissioned, validated, idempotent, and recorded as an immutable event.

Open foundationsVanilla Postgres, OpenAPI, JSON Schema, MCP and generated SDKs. Nothing here needs us to stay portable.

The ontology, the engine, the contracts. Forge ->

IngestionSource systems → one model

Your PMS doesn't have to know we exist.

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.

01ExtractConnectors pull from the systems you already run — PMS, POS, workforce, procurement — on their own schedules.

02Land verbatimEvery vendor record is staged raw, exactly as it arrived. Nothing is dropped or coerced at the door.

03Fold through actionsVersioned mappings replay each record through the same governed actions as every operator — validated, idempotent, audited.

Every sync run is an audited object in the same ontology it feeds. How ingestion works ->

Design principle

AI acts through the same rules as everyone else.

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 ->

The Explorer approvals inbox — agent-proposed actions awaiting human confirmation

The familyBuilt on the same model

Forge is the platform. Ithaca runs the desk. The rest is built the same way.

Forward deployed

Building the operational foundation hospitality is missing.

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 walkthrough is where that starts: we set up a hotel shaped like yours and work the day with you, live.

Book a walkthrough

Walkthroughs run live, over a video call. Design partners are chosen from them.