One platform for the daily running of a hotel, built by people who listen to hoteliers

Why we are building it

A small resort can easily have one system for the website, another for bookings, a third for the front desk, a spreadsheet for transfers and a till in the restaurant that knows nothing about the guest. Each works on its own. The cost shows up in the gaps: the dinner that never reached the bill, the room sold twice, the morning spent copying arrivals from one screen to another.

Hemmz puts those jobs on one platform that shares the same guests, rooms, rates and bills. We started with the booking engine and the rate and availability calendar and have been extending it into the daily running of the property: the front desk, housekeeping, maintenance, transfers, experiences and, in pilot, the restaurant.

The platform was first called Kaamos. It became Hemmz in 2026, a name that is easier to say and spell wherever a hotelier happens to be. More on the change of name.

How we work

We say what is ready and what is not. Every module on this site carries a label for how far along it is, and we would rather lose a sale than let a property discover a gap after signing.

We roll out in stages. A property keeps its current systems until each replacement has been tested with its own bookings and accepted by its own staff.