The questionsoperators actually ask.

An operating layer that sits above your PMS. Guest communication, housekeeping and service execution, finance operations, governance and F&B run against one shared context instead of seven disconnected tools. Your PMS stays the system of record — HotelOS is where the work around it actually happens.

No. Every property we have worked with started with the one surface where coordination cost was already visible — usually Desk for guest messaging or Flow for housekeeping — and expanded when there was a measurable reason to. The suite is designed to be entered at one door.

No, and we would be suspicious of anyone who said otherwise. Mews, Cloudbeds, Opera and Apaleo hold the reservation and the folio. HotelOS reads from them and writes back through governed paths, so the PMS stays authoritative and your team stops re-keying between systems.

The architecture is built around the stack independent hotels actually run — PMS, accounting, POS, payments and messaging. Rather than publish a static list that ages badly, we keep the live picture on the roadmap page, including what is shipped and what is still in build. If the system you depend on is not there, tell us: we read every request and publish the ones we commit to.

Nothing consequential happens without a rule that permitted it and a record that it happened. Command is the policy spine: brand defines identity, approvals and policy once, properties inherit them, and the audit trail writes itself behind every decision. An agent proposes; the workflow that owns the action decides whether it executes.

You elect residency per tenant at provisioning — US (Virginia), EU (Frankfurt) or APAC (Singapore). Stateful data, object storage and backups stay in the elected region, and nothing crosses regions without your written instruction.

Private beta, recruiting a founding cohort. That is a deliberate constraint, not a soft launch — the roadmap is shaped by the operators in it, and we would rather be honest that you would be early than discover it together in month three.

Twenty minutes, screen-share, your questions first. We run the operating layer against your stack and your shift pattern rather than a generic deck, and you get an honest answer on fit — including when the answer is not yet.