Most hospitality groups run a PMS, a booking engine, and a guest-messaging tool per property, pay OTAs 15% to 25% on every reservation, and watch the guest split across sites. Rehost is one branded guest app, one guest profile, and direct booking across every property, owned in your name.

What a per-property hospitality stack actually costs.

• The PMS and its add-ons bill per property. Cloudbeds is reported at roughly $180 to $600+ per property per month depending on room count and plan, and Mews is quote-only but reported to start near 17 USD per room per month with a typical floor around 300 EUR per property. Stack a guest-messaging tool like Akia (reported from about $43/mo) or Canary (quote-only, realistically materially above $200/mo for a mid-size property running check-in plus messaging) on top, and every property carries the full subscription again. A five-property group buys the stack five times before a single guest is unified.
• OTAs take 15% to 25% off every reservation they source. Booking.com's base commission is reported around 15% and can rise to 18% or more with its visibility programs; Expedia is reported at 15% to 25% for independents once promotions are factored in. That cut lands on every property, on every reservation the OTA sources, and the effective rate climbs higher after discounts and cancellations. The OTA is genuinely good at filling rooms, but it owns the guest relationship, and you rent your own customer back on every stay.
• Guest profiles silo per property. Each PMS keeps its own guest record, each booking engine keeps another, and the messaging tool keeps a third. A guest who stays at your coastal property in spring and your downtown property in fall is two separate profiles on two separate systems. You can't see a true repeat guest across the group, so you market to your most loyal travelers as if they just found you.
• Loyalty and direct booking don't span the group. Most PMS-bundled loyalty and booking engines are scoped to the property that enrolled the guest. A stay credit or member rate earned at one property typically doesn't carry to another, and the booking flow a guest lands on is tied to a single site. For a group that wants one brand, one member rate, and one reason to book direct, the per-property stack is the opposite of what loyalty is for.

One guest app, one profile, owned by the group.

We build and operate one branded guest app, one website, and one direct-booking and loyalty layer for the whole group, with a single unified guest profile that spans every property. It integrates around the PMS each property keeps running, Cloudbeds, Mews, or whatever each site is on, so the front desk and housekeeping workflows don't change. What changes is that the guest is one record everywhere: a repeat traveler is recognized, member rate and stay history intact, the first time they book your second property. Direct bookings flow through your own app instead of an OTA, so the reservations you source stay yours rather than handing a reported 15% to 25% to the marketplace.

Rehost is a software lease with an operating team. We build it and we run it: design, App Store submissions, content changes, and the AI guest-messaging layer are handled by our team, and your staff never logs into a dashboard. You own the App Store account, the domain, the code, and the guest data from day one. And the bill is by total monthly active app users across the whole group, not per property and not per room: $950/mo up to 2,000 MAU, $1,500 up to 10,000, $2,500 up to 50,000. Opening or acquiring a sixth property doesn't add a sixth subscription.

What multi-property operators ask.

Related.