Our manifesto: system first, intelligence second.
We don't build generic software. We start from how hospitality operations actually break, and the order in which we build follows from that.
The diagnosis
The root of the problem
Whoever runs a restaurant or a hotel isn't looking for more software. They're looking to stop holding the operation together with memory, chat threads and constant presence.
Why now
Customers no longer tolerate waiting, costs are tight, and regulation — electronic invoicing included — raises the bar on what a business must be able to prove.
The new standard
Guests compare your booking flow to an OTA's and your menu to a delivery app's. The bar has already been set by products that aren't yours.
How we build it
Where we are going
We are building toward a unified hospitality operating layer that connects customer conversations, reservations, orders, payments and operational systems. It does not exist yet: what is in production today is Gastro's digital menu and Travel's storefront with direct booking, and the rest is being built on those foundations.
In what order
First the system knows how to manage something; then it gets automated. An assistant can only sell what the product already handles, so every new module widens what automation will be able to do.
Who it is for
Restaurants, cafés and bars that want control over their menu and their floor. Hotels, glampings and lodges that want to sell directly without depending entirely on intermediaries.