Hospitality operating system
Your entire property works
as one team.
Front desk no longer hunts through chats. Housekeeping knows which room is critical. The kitchen does not receive duplicate orders. Management sees the owner, deadline, and next action—not a stream of disconnected notifications. In GostelOS, the guest, room, order, task, shift, money, and inventory are connected by one process.
68 rolesa dedicated workspace for each
504 scenariosfrom request to outcome
24 E2Eend-to-end processes
GostelOSWhat needs a decision now
ReservationArrivalStaySettlementReturn
More than a notificationRisk · owner · ETA
Shift handoffContext and SLA preserved
Does this look like your workday?
The problem appears between departments.
That is exactly where GostelOS resolves it.
Automating a single screen is not enough. A promise to a guest must reach the person who will deliver it; a physical room must return to sale only after every check; and a payment or order must not be duplicated after a failure.
“The status is in the PMS, the details are in chat, and only the shift knows who is responsible.”
The GostelOS solution
A unified process card stores the guest or asset, status, SLA, owner, history, evidence, and next step. A handoff transfers work to another shift without losing promises or deadlines.
“The room is clean, but the fault has not been checked—and it is already back on sale.”
The GostelOS solution
Occupancy, housekeeping, engineering, and commercial statuses are separate. A room returns to sale only after independent housekeeping, engineering, and safety gates.
“After the system froze, an employee clicked again—and created a second order or payment.”
The GostelOS solution
Idempotent commands, durable queues, and reconciliation protect reservations, payments, printing, write-offs, issuance, and notifications from duplicate business effects.
“Management receives everything, yet cannot see what actually needs a decision.”
The GostelOS solution
The home page answers four questions: what is critical, what should be done now, what is overdue, and what is waiting for your decision. Every KPI opens its source register.
“When the network goes down, field work stops or disappears.”
The GostelOS solution
The PWA preserves the local ID, original timestamp, and pending state. Once the network returns, the command synchronizes exactly once and any conflict is shown explicitly.
“A new employee learns from an outdated file and sees functions they do not need.”
The GostelOS solution
Role-based help is generated from the same catalog as processes and permissions. Employees see only their own scenarios; directors and administrators see the complete operating model.
One business fact—one record
The channel changes.
The process logic does not.
Web, PWA, Telegram, MAX, the website, POS, and integrations call the same domain commands. Employees and guests therefore see the same current status, not several competing versions of the truth.
01TriggerA guest taps a button, an OTA reservation arrives, a sensor fires, or a shift begins.
02ProcessRules validate permissions, resources, required data, the SLA, and the permitted transition.
03ExecutionThe role receives a personal queue, checklist, evidence requirement, ETA, and handoff.
04OutcomeEventLog, the ledger, and a reviewer confirm the business effect—not merely a button click.
WebsiteWeb / PWATelegramMAXGostelOS CoreState machine · RBAC · SLA · EventLog · LedgerOTA / PMSPOS / KDS1C / banksAPI / webhooks
Complete operating model
From a guest's first interest
to the next sale
Modules do not stop at their own boundaries: reservations account for rooms and money, restaurants for guests and inventory, repairs for saleability, and shifts for the actual availability of staff.
PMS, Booking Engine, and Channel Manager without manual gaps
Search and total price, direct and OTA reservations, groups, room rack, pre-arrival, online check-in, room assignment, early/late departure, no-show, folio, checkout, and reconciliation.
- Inventory and restrictions
- Room assignment conflicts
- Payment links
- Documents and audit
Guest 360 and Service Recovery
One profile and its consents, stay history and preferences, requests from every channel, public and internal messages, guest confirmation of the outcome, reviews, CAPA, and loyalty.
Room readiness you can trust
Dirty -> cleaned -> inspected, DND/MUR, routes prioritized by the next arrival, QR/geo/photo evidence, offline checklists, rework, linen, minibar, lost & found, and public areas.
From request to asset reliability
Asset register, work orders, preventive maintenance, spare parts, warranties, downtime, OOO/OOS, RCA, rounds, emergency playbooks, chain of custody, HSE, and CAPA.
Dining room, POS, KDS, production, and inventory speak one language
Table reservations and waitlists, orders by guest/seat/course, modifiers and allergens, kitchen stations, serving, split/merge, tips, room charges, recipes, lots, FEFO, purchasing, production, food safety, and cash reconciliation.
- Tables and seating
- Exactly-once write-off
- Room service
- EGAIS / Mercury / product marking
A shift is part of the process, not a separate spreadsheet
Availability, published schedules, open shifts, swaps, vacation and sick leave, clock-in/out, breaks, timesheet corrections, skills and clearances, payroll snapshots, and a personal account.
Composite booking without hidden conflicts
The specialist, room, equipment, capacity, and buffers are reserved simultaneously. Forms and data-access restrictions, packages, memberships, rentals, waivers, and weather closures are included.
The BEO becomes an executable plan
Event CRM, contract, space block, BEO versions, section approvals, resources, timeline, change orders, banquet execution board, actual extras, and final invoice.
Money reconciles before the period closes
Immutable folio and ledger; charges, payments, refunds, and deposits recorded separately; cash desk, AP/AR, three-way match, PMS-POS-PSP-cash register-bank-OTA reconciliation, business date, and period lock.
From an indicator to the source fact
Occupancy, ADR, RevPAR, revenue, margin, labor and food cost, SLA and first-pass quality, process bottlenecks, owner reports, and multi-property benchmarks with one version of every formula.
Sell the property as it actually operates
CMS and SEO, a property map to scale, cottages, paths, spa, parking, and infrastructure, plus a venue and table editor. Existing connectors and editors are retained and continually developed.
Role workspace
Everyone sees their work.
No one sees unnecessary data.
GostelOS is deny-by-default: the role template, permission, property, department, active employment, and data policy are intersected at the moment of action.
View role-based helpFront deskReservationsRevenueGuest RelationsHousekeeperSupervisorTechnicianChief EngineerSecurityHostServerCookChefStorekeeperSpaBanquetingHRFinanceITDirectorOwner+ 47 more role templates
Personal queue: asset, priority, SLA, checklist, prominent action, camera/QR, and genuine offline work.
Workload, overdue items, waits, rescheduling, handoffs, confirmation, and rework.
Complete functionality, 24 E2E processes, EventLog, roles, permissions, integrations, and diagnostics.
Web, Telegram, and MAX
One button— one core command
A messenger is a convenient channel, not a separate database. Its menu is built from the role's capabilities, callbacks are acknowledged, repeated actions are protected from duplication, and the result appears in a new message beneath the main menu. If external delivery fails, the business process remains available in GostelOS.
MAX · GostelOS
What would you like to do?
✅ Task accepted
Room 305 · SLA 14:30
Room 305 · SLA 14:30
Same Case IDSame statusSame permissionsSame EventLogNo 'bot spreadsheets'
Reliability is part of the feature
A failure must not become
a duplicate sale.
GostelOS designs recovery alongside the primary flow: correlation IDs, inbox/outbox, retries, dead letters, replay, health checks, business probes, reconciliation, and a clear status for uncertain operations.
Separate tenant databaseProperty data, users, files, and settings are isolated.
IdempotencyA repeated click, webhook, or replay does not repeat the effect.
EventLog and auditThe actor/source/before/after/correlation timeline reconstructs every decision.
Backup and rollbackUpdate checks, backup, atomic release, and diagnostics.
Integration Hub
Connect your systems.
Do not multiply manual entry.
OTA, PMS, CRM, telephony, payments, cash registers, 1C, POS, locks, Wi-Fi, reputation services, and partner APIs connect through one lifecycle: manifest -> credentials -> mapping -> test -> sync -> reconciliation.
OTA / ChannelTravelLinePayments / SBPCash registers / fiscal data operator1C / EDIEGAISMercuryLocks / EdgeTelephonyWi-FiTelegram / MAXREST / webhooks
An honest integration boundary. Private APIs require a contract, official specification, credentials, and sometimes partner certification. GostelOS never presents a catalog card as a completed connection.
What changes for the business
Fewer losses at handoffs.
More service under control.
Context follows the request between the website, bot, front desk, and person performing the work.
Readiness is composed of independent physical checks, not a single convenient flag.
The queue accounts for the SLA, next arrival, risk, role, skills, and actual availability.
Every transaction references its source; a correction compensates for it without deleting history.
Instead of compiling reports manually, managers drill down to the exact facts, owner, and expected resolution.
Roles, processes, tests, and Help use the same catalog, so the release and its instructions change together.
Frequently asked questions
Before the demonstration
Do we have to replace every existing system at once?
No. GostelOS can become the unified operating core gradually: roles and processes first, followed by data and individual integrations. Existing property-map editors, connectors, and working modules are retained.
Is the system suitable for more than traditional hotels?
Yes. The resource catalog and composite bookings are designed for country resorts, cottages, restaurants, bathhouses, spas, rentals, activities, and events.
How are Telegram and MAX different from standalone bot automation?
They do not create separate logic. A button calls the same domain command as web/PWA, so status, permissions, SLA, and history remain unified.
What will an individual employee see?
Only the permitted workspace and help for their role. Administrators and directors have access to the complete operating model; documents, health data, payroll, CCTV, and secrets are controlled by separate permissions.
Can we test the system before implementation?
Yes. Open the separate demo database and walk through role scenarios and end-to-end processes. For production, we recommend UAT with your own roles, rules, data, and integrations.
Do not click through a presentation—walk through a process
See GostelOS through the eyes of your role
Explore the queue, role-based help, and the path from an event to a confirmed outcome in a separate demo database.