Short version: subscribe to a hotel chatbot SaaS when you want a proven product running this week, you like having a vendor to call, and a predictable monthly fee fits how you budget. Have one built and own it when your volume makes per-room fees add up, you want your guest data to stay on your own European server, and you have someone to keep it current.
In an earlier Field Note, An AI Concierge for Your Guests, I described what a knowledge-base assistant is and how it answers guests in their own language around the clock. This post is the money question that always comes next: do you rent one from a software company every month, or do you have one built that you own outright? I run my own server and build the owned kind, so I have a side in this. Even so, I will lay out both honestly, because for some properties the subscription is the right call.
What These Assistants Actually Do for Your Guests
A quick recap, since the earlier post covers this in depth. Whichever route you take, the job of the assistant is the same:
- Answer the repetitive questions instantly: check-in and check-out times, Wi-Fi, parking, breakfast hours, directions, local tips.
- Reply in the guest's own language, German, Italian, English and more, day or night.
- Catch inquiries that arrive after hours, so nobody waits until morning for a two-line answer.
- Sit on your website, in a booking-confirmation email, and often on WhatsApp, all reading from the same source of truth.
- Hand off anything real, a cancellation, a broken radiator, a price negotiation, to you.
The Subscription Route: Rent a Finished Product
The hospitality software market has mature chatbot products you can switch on quickly. You pay a monthly fee, the vendor hosts everything, and you get an admin panel, integrations with booking engines and property-management systems, analytics, and a support team. Here are four active vendors as of 2026, with the pricing shape each one uses. Treat the figures as a starting point: every vendor quotes by property size and asks you to confirm current pricing.
HiJiffy, based in Lisbon, is one of the most visible hotel chatbots in Europe. It prices in tiers billed by your number of rooms: as of 2026 roughly 99 euro per month for a basic FAQ plan, around 159 euro for a plan with an omnichannel inbox and well over a hundred languages, and around 319 euro for the top tier with the AI concierge and WhatsApp campaigns, plus a one-time setup fee. The more rooms you have, the more you pay, with volume discounts higher up.
DialogShift, a German vendor used by chains such as Motel One, sells modularly. As of 2026 a base AI knowledge plan sits around 200 euro per month, and you add modules on top, a chatbot module, an email module, a phone module, each with its own monthly fee and setup cost. Pricing is quote-based and clearly aimed at the European market, which is a point in its favour on data questions.
Straiv by CODE2ORDER, out of Stuttgart, is less a pure chatbot and more a digital guest-journey suite: mobile check-in, a digital guest directory, and a digital concierge, used by more than 2,500 hotels across some 29 countries. Pricing is not published; it is quoted per property. Worth a look if you want the assistant to be one part of a broader in-stay digital experience rather than a standalone chat widget.
Asksuite, from Brazil, is a heavyweight in the reservation-assistant category, used by well over 5,000 hotels worldwide and repeatedly ranked at the top of hotel-tech awards. It leans hard on turning chats into direct bookings and integrates with hundreds of booking engines. Pricing is quote-based; small and mid-size independent properties typically land somewhere around 150 to 300 US dollars per month as of 2026.
What you get for the monthly fee is real: the product exists today, someone else runs it, updates and new features arrive without you lifting a finger, and the deep booking-engine and PMS integrations would take real work to build yourself. What you give up is also real: the fee recurs forever and grows with your rooms and the features you unlock, your guest conversations flow through the vendor's platform on their terms, and you never own the thing you are paying for. If you stop paying, the assistant goes dark.
The Owned Route: Build It Once, Run It on Your Own Server
The other path is to have an assistant built for your property and run it on infrastructure you control. This is the kind I build. There is no per-room monthly fee to a software company. Instead there is a one-time build cost to set it up, and a small running cost after that: a server, which for a single property is a modest monthly amount, plus usage of the AI model itself, which for the volume of a small or mid-size hotel is minor. You own the code and the knowledge base. It does exactly what your property needs and nothing you did not ask for.
Because it runs on my own Hetzner server in the EU, your guest data stays on European infrastructure that you and I control, not on a third-party platform. When the assistant does not need to store a conversation, it does not. That is a straightforward answer to give a guest, and to a data-protection authority.
The honest downside: an owned system needs someone to keep it current. When the AI model it builds on changes, when your property information changes, when something breaks at two in the morning during high season, there has to be a person responsible, me on a maintenance arrangement, or someone in-house. You do not get a large vendor's support desk. And the money arrives as an upfront investment rather than a small monthly line item, which suits some budgets and not others. An owned assistant is also, by design, an information assistant, not a booking engine with dozens of native integrations; if you need deep two-way sync with a channel manager, a specialised SaaS may simply do more.
A Simple Way to Decide
You do not need a spreadsheet. Answer these six questions honestly and the shape of the answer usually appears.
- Volume. How many guest messages do you really get a month? Low and steady, and a subscription's minimum fee is easy to live with. High, and per-room fees start to look like rent you could have owned instead.
- Seasons. Do you close for part of the year? A subscription bills you in the quiet months too. An owned assistant costs almost nothing while it sits idle.
- Data. Do you need your guests' data to stay on European infrastructure you control, not just "GDPR compliant" on paper? That pushes you toward owning, or toward a strictly EU-hosted vendor.
- Integrations. Do you need the assistant wired deep into your booking engine and PMS for live availability and upselling? SaaS vendors ship that today. If you mainly need fast, accurate answers, an owned information assistant is enough.
- Budget shape. Can you spend once as an investment (capex), or do you prefer a predictable monthly cost (opex)? Owning is a larger one-time cost plus a small run rate. Subscribing is pure monthly opex.
- Maintenance. Do you have someone to keep an owned system current? If yes, owning is on the table. If not, a subscription includes that upkeep in the fee.
A subscription is renting a good product. An owned assistant is a small asset that keeps working after the invoice stops. Neither is wrong. The right choice comes down to your volume, your seasons, and where you want your guests' data to live.
Most of the hosts I talk to in South Tyrol are not choosing between good and bad, they are choosing between renting and owning, and they just want the numbers laid side by side for their own property. That is a short conversation. Tell me your rough room count, how busy your inbox gets, and how you feel about your guest data leaving the EU, and I will give you an honest build-versus-subscribe estimate, including the cases where I would tell you a subscription is the smarter buy.
Get a build-vs-subscribe estimate