Run your hotel with AI.

One system for bookings, housekeeping, maintenance, stores and reports, with an assistant that works in every department.

10+
hotels run on it today
2 to 3 weeks
to go live, for 40 to 100 keys
First shift
the founding team is on site
1 bill
per property, per month, every screen included
Connects to
  • Telegram
  • WhatsApp
  • Instagram
  • Messenger
  • Email
  • iCal
  • Payme
  • Click

Everything the product has today, on one bill.

A property gets every screen, and a person who belongs to several properties finds the same screens at each.

Front desk

  • Dashboard
  • Room map
  • Reservations
  • Timeline
  • Guests
  • Events and halls

Operations

  • Housekeeping
  • Maintenance
  • Lost and found
  • Stores
  • Expenses
  • Channels

Outlets

  • Restaurant and bar
  • Kitchen screen
  • Pool and spa
  • Meal plans

Management

  • Staff, rota, time clock, payroll
  • Reports and exports
  • Night audit
  • Assistant, Ctrl/⌘ J anywhere
  • Registration cards and invoices, printed in two languages
  • English and Russian, Uzbek planned

Your guests' data stays with the hotel.

Operated from Uzbekistan
Operauz is run from Uzbekistan; the contract and the data-processing agreement come from there.
One property, one boundary
Every record is isolated per property in the database itself. A person sees a property only because they belong to it, and the audit log records who changed what.
Data protection
Built to GDPR principles, with a data-processing agreement sent before a walkthrough. Aligned, not certified.
Your data, exportable
Reservations, guests, folios and every report export as spreadsheets any day you ask. You leave with everything.

Built on the shift floor of a resort at 2,000 metres.

Operauz grew up on the shift floor of a mountain resort, where the outlets, the pool and the full-board plans were never an afterthought. Today more than ten properties run on it, each moved off its old system by the founding team, who sat the first shift. We are taking a small number of properties this year, with the founders on the implementation.

A hotel running on Operauz, entrance at dusk
A hotel running on Operauz, exterior
The road into a mountain resort, a peak ahead

Questions we get asked.

Which AI model does it use, and where does our data go?

The property chooses. The assistant talks to Anthropic or to any OpenAI-compatible endpoint under the property's own key, and a prompt goes to that provider and nowhere else. DeepSeek is configured out of the box because it is inexpensive and reads Russian well; a property that wants its records kept with a European or American provider swaps the endpoint in Settings in a minute. Card numbers and passport images never enter a prompt. Hosting and retention are set out in the data-processing agreement we send before a walkthrough.

We run a legacy desktop PMS. How does migration work?

The same way our first properties did: they moved off a FoxPro-era desktop system. Reservations, guests, rate plans and open folios are imported from an export of the old database, reconciled against the room map, and run in parallel for a few days before the old system is switched off. We do it with you.

Does it work in our languages?

Every screen runs in English and Russian today, chosen per person from the top bar; Uzbek is planned. Registration cards, invoices and function sheets print bilingually by the property's own document settings. The assistant answers in the language the property sets.

Which messengers, channels and payment providers does it connect to?

Guests write where they already are: the assistant connects to WhatsApp, Instagram, Facebook Messenger, Telegram and email, and answers in the same channel as the hotel. A rates-and-availability calendar with iCal both ways and a booking import for the online channels; Payme and Click for the Uzbek market; cash, card and company accounts in one audit. Direct two-way connections to specific channel managers are on the roadmap, and we will say which at the walkthrough.

How is it priced?

One figure per property, per month, with every screen and the assistant in it. The assistant runs on your own model key, so its usage cost is yours to see. We quote at the walkthrough, once we know the key count and the outlets; there is no price list because there is nothing to add on.

How long does implementation take?

A property of forty to a hundred keys is typically live in two to three weeks, with the founding team on site for the first shift.

Show us your house. We'll run it in the first hour.

A walkthrough is a real session on a real system with your room types and rate structure loaded. If it doesn't fit how your property works, we would both rather find out in the first hour.

or write to hello@operauz.com