How HemmaBo works
How a booking site on your own domain takes bookings and payments.
Step by step explanation
- The host creates their own booking page via HemmaBo
- The page is connected to the host's own domain
- Booking calendar and availability are handled automatically
- Guests can book directly via the page
The system keeps working after the booking
A HemmaBo site is not only a booking button. It handles the practical steps around the stay so the host does not need to watch the calendar, inbox, and guest requests all day.
- HemmaBo Wallet: The guest gets one wallet for booking details, arrival information, add-ons, and stay-related requests.
- One more night: When the night after the stay is free, HemmaBo Wallet tells the guest the day before checkout. The guest asks from their page, and one more night is priced at the host's prices and paid there.
- The night between two bookings: The host offers the empty nights between two bookings or not, with their own minimum stay and the lower price the host sets.
- Early check-in and late checkout: The host can allow early check-in and late checkout, free or paid. Requests are checked against booking rules and calendar availability before they move forward.
- Guest-language emails: Practical information, arrival instructions, and door-code timing can be sent automatically at the right moment and in the guest language.
- Booking protection: HemmaBo uses rule-based conflict detection, booking locks, and control signals to reduce double bookings and unsafe booking flows.
What the host controls
- Domain, rules, pricing, and terms
- Whether bookings are instant or request-first
- Fees for early check-in, late checkout, and add-ons
- Which information the guest receives before and during the stay
How your property is found and verified — then booked on your site
When your domain is live it automatically exposes /llms.txt, structured data, a sitemap and VRP discovery. AI agents without a plugin can read your domain and follow /.well-known/agent-traversal.json: discover → verify keys → signed VRP offer → your booking page. The guest books there. Agents with MCP support reach host domains via hemmabo-mcp-server (6 tools). The AI function does not replace legal, financial or personal advice.
Alongside external channels
HemmaBo does not replace your existing listings. Run them in parallel while you build your own commission-free direct-booking channel on your own domain. Two-way API calendar sync — one calendar, no double bookings.
Calendar synchronization
Two-way API calendar sync — one calendar, no double bookings.
Own domain
Each booking page can be connected to its own domain. Customer pages are independently indexable with their own canonical URL and structured data.
Responsibility
Legally clear. No gray areas.
- As a host, you are responsible for the rental, guests, and terms.
- HemmaBo provides the booking website system: website, booking, payments, and operations.
- HemmaBo is not a party to rental agreements between host and guest.
HemmaBo exclusively delivers booking websites and is not a party to agreements between host and guest.
What is a VRP vacation rental?
A VRP vacation rental is a holiday home whose host runs its own booking site on its own domain and publishes stay offers signed by that domain under the Vacation Rental Protocol (VRP). Any guest or AI agent can check, over plain HTTPS, that the price, the dates and the conditions come from the host — with no listing site, catalog or connector in between.
HemmaBo is software that makes a host's home a VRP vacation rental: the booking site on the host's own domain, the signed stay offers, and payment straight to the host.