Common questions
The questionsoperators actually ask.
What the platform is, what it does not do, and where your data sits. Commercial questions — pricing model, implementation cost, contract length — are answered next to the numbers on the pricing page.
What is HotelOS?
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.
Do we have to adopt all of it at once?
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.
Does it replace our PMS?
Your PMS remains the system of record for reservations and folios. HotelOS is designed to work above it. We confirm compatibility, permissions and supported data flows for your property before agreeing an integration.
Which systems do you connect to?
Availability is confirmed in writing for your property. Provider permissions, technical validation and any required approvals must be in place before activation. A request does not guarantee delivery.
See the roadmapHow do you approach AI governance?
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.
Read the trust postureWhere does our data live?
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.
Full data architectureWhat stage are you at?
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.
What does the first conversation look like?
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.
Book a walkthroughStill unanswered?
Ask the question we have not thought of.
A founder reads the contact inbox. If the answer belongs on this page, it ends up here.