Three ways to run the hospitality business. One platform underneath.
Hotels, short-term rentals, and serviced apartments each get a solution shaped to how they work, all on the same database, the same login, and the same 57 products.
Hotels & Resorts
For a 12-room boutique to a 200-property chain: reservations, channel and revenue management, housekeeping, multi-outlet F&B, digital keys, and the guest folio on one login.
Explore →Short-Term Rentals
For solo hosts to multi-region property managers: channel distribution, dynamic pricing, direct-booking sites, guest messaging, turnover operations, and owner statements in one system.
Explore →Serviced Apartments & Extended Stay
For fifteen units to three hundred: long-stay records, corporate folios and billing cycles, multi-property management, housekeeping, and guest + owner portals across every unit.
Explore →Fifty-seven products. One record.
A guest, a booking, a folio, a payment, an owner statement: entered once and read by every surface. The whole property runs from a single database instead of a twelve-vendor patchwork.
Six apps. One stay.
A guest, a booking, a folio and a payment entered once and read by every surface. What follows is not an integration list, it is the same record seen from six places.
Bookings
Reservation → Folio
Units, rooms and blocks on one availability record, where a direct booking and a channel booking are the same reservation posting to the same folio.
Sync
Channel → Calendar
Distribution held against the same calendar the front desk reads, so an availability change reaches the channels without a second inventory to keep honest.
Station
Outlet → Charge
Food, beverage, retail and services run on one terminal layer, and a charge reaches the stay without the outlet needing to know anything about the booking system.
Dispatch
Departure → Turnover
Turnover and maintenance move with the departure rather than with a phone call, and a fault raised on site becomes a work order with an owner and a due time.
Navigator
Guest → Key
The guest app, the digital key and the in-stay screen read the same reservation, so a change granted at the desk is a door that still opens.
Ledger
Revenue → Books
Accommodation, outlet and ancillary revenue post to one set of books, including the owner statement, so a property P&L does not need three exports first.
From a 12-vendor patchwork to operator-grade intelligence
The before, during, and after of consolidating a property onto one platform. The same transformation whether you run a hotel, a portfolio of rentals, or a block of serviced apartments.
Before: The 12-Vendor Patchwork
A property-management system in one app, a channel manager in another, revenue, housekeeping, maintenance, messaging, payments, owner statements, and the booking site each on their own login. A dozen invoices, a dozen systems, zero shared guest record. A rate changes on one channel and stays stale on three others because nothing syncs.
During: One Connected Platform
One login, one guest profile, one folio, one calendar. Reservations, channels, housekeeping, payments, messaging, and owner accounting share a single data layer. Products from the Core, Commerce, Ops, Nexus, Work, Interact, and Engage suites connected by design, not by integrations you maintain.
After: Operator-Grade Intelligence
Data from every suite drives every decision. Rates adjust to demand. Housekeeping predicts turnover. Marketing re-engages past guests and owners. The routine is automated so your team focuses on the guest.
A booking confirms in Core, the rate and folio open in Commerce, the turnover schedules in Ops, the guest and owner portals update in Nexus, the confirmation and check-in messages send via Interact, and the loyalty points post in Engage, one action moving across every suite. No re-entry, no exports, no twelve-vendor patchwork.
Hospitality is rarely one thing, and nobody expects it to be.
Nothing here is an integration. It is one set of records that more than one part of your business already writes to.
Frequently asked questions
Consistency fails at the handoffs. The front desk knows the guest is a repeat visitor and the kitchen does not; the spa holds a slot the reservation system cannot see. Calisto removes the handoffs rather than documenting them. One login, one guest record, one folio, so there is only one version of what happened.
The inspection photo from the clean, the door access log for the stay, and the folio line for the charge sit on the same booking, each timestamped. A disputed minibar charge is settled from the record rather than from what anyone remembers.
Yes. Unlimited properties with consolidated dashboards, cross-property reporting, brand-standard enforcement via Assure, a central reservation system (CRS) for portfolio-wide inventory and rate management, chain-wide pricing strategies with property-level overrides, and owner statements with trust accounting for each property. Staff permissions by property, department, and role. One login for the entire portfolio.
Each outlet, from the lobby restaurant and pool bar to room service, the spa cafe, the golf clubhouse and the rooftop, gets its own terminal, menu and kitchen display. Every charge posts to the guest folio as it is rung. The folio that used to require night-audit reconciliation across four POS systems now balances itself.
The Deals pipeline tracks every group inquiry from initial RFP through signed contract, priced from the same rate engine the OTAs read. Won deals automatically create group blocks with room allocations, release dates, and rooming list templates. Live runs virtual site tours for remote planners.
Access issues digital keys through Navigator with Apple Wallet and Android support. Keys auto-provision at check-in and auto-revoke at checkout, and every access event is logged. No per-door monthly fees, and no hardware replacement: six smart-lock vendors are supported.
A portal instead of a monthly email, with occupancy, ADR and payout history updating as the stays happen. Their guests get a guidebook and a working door code instead of a combination sent at 9pm. Producing that by hand is a full-time job, which is why the difference shows on the first statement.
The reference image for that room and the cleaner's photo of it, both timestamped against the turnover that finished before check-in. The claim is settled from the record rather than from what the cleaner and the guest each remember.
Her checklist, her reference photos and the owner's standing instructions, all on the property record rather than in her head. A covering crew works the same list on the first day, which is why the twelfth stay of the season matches the first.
No. There is no tier to migrate to and nothing to replatform. Solo hosts start with channel sync, messaging, and digital keys. Owner portals, trust accounting, and field crew dispatch switch on against the same record, and nothing already set up gets rebuilt to reach them.
Airbnb, Booking.com, VRBO, Expedia, Agoda, and 200+ OTAs with real-time rate and availability sync. iCal feed support for the niche platforms that never built a direct integration.
No. Calisto drives the major smart-lock brands directly, and a property still on a keypad works from a scheduled code. Either way the code is issued for the stay dates and expires at checkout, with every entry logged against the booking.
No, because the property is one record. The listing you market for sale and the unit you manage as a rental are the same record in Listings: the sale pipeline in Deals, the rental calendar in Bookings and the owner reporting in Ledger all read it. Taking on management after a closing adds nothing to re-enter, nothing to sync and no second login, and the seller who becomes your owner keeps the history you already built with them.
A task list waits for somebody to work it. This assigns on GPS proximity, routes the crew between properties, opens work orders off a failed inspection, prices the repair, holds the equipment history on the unit and carries the timestamped photos. It is native field service management, the same platform the trades run, and running distributed lodging is running a hotel whose rooms are spread across a city.
The checklist, the reference photos and the work order load before the crew leaves range and complete on the phone offline. Everything syncs when they are back in coverage, timestamped to when the work actually happened rather than to when the upload landed. A rural cabin is inspected to the same standard as an urban key.
When a stay crosses the nightly-to-weekly or weekly-to-monthly threshold, the applicable rate applies without a manual trigger. The folio updates. The corporate account receives the correct figure.
Every stay linked to a cost center closes into a single statement at the end of the billing period. Finance receives one document.
The end date updates. The rate tier recalculates. Access credentials extend. The housekeeping calendar adjusts. The booking channel sync removes availability through the new date.
Split billing rules sit on the corporate account. Accommodation posts to the company folio on the agreed net-30 or net-60 terms with the PO number and VAT ID attached. Parking, laundry, and late fees post to the resident's own folio. Both close in the same billing run.
Each owner holds a segregated ledger. Gross revenue posts to the unit. The management fee, typically 15 to 18 percent, calculates against it. Maintenance expenses log against the unit that incurred them. The net distribution statement renders in the owner's portal. No owner sees another's figures.
No minimum. The same stay record runs behind a single apartment and behind a portfolio of buildings, and nothing is replaced when the next building joins.
They are not paying for the apartment. They are paying for an arrival that works at 11pm, a leak fixed the same night, and a unit that matches what they were shown. A guest staying several weeks finds out within a day, and the reviews already told them before they booked.