About

Hestia was the Greek goddess of the hearth and the home — the fire a household gathered around and did not let go out. Hence Hesty. The modules take names from the same pantheon: Calliope, muse of epic poetry, handles content. Athena, goddess of order, handles staff. This is not just naming. The house is the container and the modules are the fire — one flame split into parts, rather than nine separate programs stacked side by side.

Most hotel systems are sold whole. You pay for everything and use a third of it. An eight-room guesthouse does not need what a chain needs, and yet gets handed the same price list. Hesty works the other way: the core is shared and modules switch on according to what your property actually does. When a need appears, a module appears. When it does not, you are not paying for it.

Portals earn their commission when they bring you a guest who has never heard of you. They stop earning it on a guest who has stayed five times and was coming anyway. That distinction is why Hesty has its own booking engine, and why almost everything else circles back to it — from vouchers to the statistics that show what commission is genuinely costing you.

Modules share data, not exports. One occupancy calendar for the whole system, so double bookings do not appear through lag between tools and nobody retypes figures from one window into another. Whatever you build on our API reads the same data reception does.