Change your website. Keep your booking engine.

The short answer

No. You do not have to change your booking engine to change your website. The engine holds your rates, your availability, your payment flow and a contract you already negotiated. A website is different software, and it can be rebuilt around the engine you already pay for.

Why the two decisions get bundled together

Engine providers also sell websites. So the quote for a new site often arrives with a new engine attached, and a design decision turns into a commercial one. The hotel ends up renegotiating something that was working, in exactly the window when direct bookings are most fragile.

We separate the two on purpose. If your engine works, keep it.

Whatever engine you already run

Your engine is your provider's software and your contract with them. Ours is a website. Whichever engine you run, the work on our side is the same: the site takes the guest to your engine, in the language they are reading, and the booking happens there.

We do not resell engines, we take no share of your direct bookings, and we will not ask you to move. If you decide to change engine one day, that is your call, and the site does not have to be rebuilt for it.

What we build around it

A multilingual site that exists as HTML

Every page is pre-rendered at build time with Vite, React and vite-react-ssg, so the text sits in the HTML that gets served instead of being assembled later in the browser. One page, one question, one direct answer. Three languages as real routes, not a translation widget on top. The booking button points at your engine.

Content an AI assistant can read and quote

The crawlers behind ChatGPT, Claude and Perplexity fetch the raw HTML and do not run JavaScript. A site that builds its content in the browser serves them an empty page. We measured this on one project: an article page gave an AI crawler 14 characters of body text before the work and 11,421 after, while human visitors kept receiving exactly the same site. That was a corporate site rather than a hotel, but it is the same failure any site has when its content is assembled in the browser.

The hotel factsheet

The plain answers an assistant needs before it will name you: where the hotel is, what kind of hotel it is, room types and board, distances, check in and check out, parking, pets, accessibility. As text on the page and as structured data, in the three languages. Written with the answer in the first sentence.

The in stay operation

The booking belongs to your engine. The stay does not. Guests ask for towels, a table, a late checkout, a taxi. We build that as a real system: requests routed to whoever resolves them, restaurant menus read from the database instead of a PDF from last season, and a trail of what was asked and what happened.

Measured at one hotel over four months: around 2,500 guest requests, a median of 16 minutes to resolve, 93 percent created without a queue or a call to reception, and 90 percent closed in under an hour. Those are the platform's numbers, not a voice assistant's.

Measurement

We instrument the path a guest takes to your engine and report on it. We do not claim credit for your engine's conversion, because the booking happens inside software we did not write and cannot measure from the inside. What we do show: which pages are read, in which language, by people and by crawlers, and what changed after each release.

What stays exactly as it is

Your contract, your commission, your rates and availability, your confirmation emails, your payment flow and your guest data. All of it stays in the engine. Nothing we build sits between the guest and the booking.

For hotels running on our platform, isolation between properties is verified rather than assumed: 81 tables carrying a hotel identifier are checked by a test that discovers hotels and tables instead of listing them, running in continuous integration, with no leakage between two real hotels when it was last verified in August 2026.

The hotels behind this page

Hotel Talavera, whose case study is published on this site, and two hotels running our hotel platform in production today, with real guests. One of those two started in August 2026, with volume comparable to the first. We do not name them here, because whether a client appears by name is the client's decision and not ours.

That is the whole list, and it is short on purpose. Every project on it can be walked through end to end.