Reference
The wiki
The product pages are short on purpose. This is the long version: every capability, what drives it, and how far along it is.
Start here
The long version of everything on the product pages: every area, every capability underneath it, and the reference tables behind them.
The size of it
Counted from the working tree at v1.10.0, not estimated.
Front desk
Reservations, availability, folios, housekeeping, tickets and the guest record.
Accounting
A complete double-entry system: ledger, cash, payables, receivables, assets, stock, payroll, period close and tax.
What posts, and where
The operational events that write to the ledger, and the entry each one makes.
Guest rooms
Room automation driven by the booking: lighting, climate, curtains, presence, energy and door access.
The IoT backends
Four transport backends. A room speaks to exactly one of them.
Device functions
Door locks
Two of these encode a key card today. The other two are described exactly as they work.
Compliance
ZATCA e-invoicing and the Saudi government platforms.
Integrations
Accounting sync, channel distribution, payment capture and outbound messaging.
Accounting providers
What each connection was tested against, and what it needs from you.
Why a synced invoice cannot drift on VAT
Reports
Ninety-four built-in reports across six families, plus the dashboards and the measures behind them.
The catalogue
Platform
Identity, roles, entitlements, tenant isolation, audit records and the built-in manual.
The habits behind the numbers
Properties the codebase holds itself to, each one enforced by a test rather than by a convention.
Deployment
What ships, how it sits on your network, and how rooms are commissioned.
Still want the short version?
The product pages say the same thing in a tenth of the words.