Meet Guestavo
We built Guestavo for hospitality people who are tired of duct-taping five different tools together. Bookings, the staff schedule, menus, events, campaigns, loyalty, and a guest portal — one system, one login, one bill, so you can spend less time on software and more time with your guests.
How this started
Why Guestavo exists
Running a restaurant, bar, cafe, or event-led venue means juggling separate tools for online bookings, staff schedules, digital menus, email campaigns, loyalty cards, event RSVPs, and guest data. Each one has its own login, its own monthly bill, and its own way of doing things. That costs real time and real money, and guests fall through the cracks because nothing talks to anything else.
Guestavo puts it all in one place. Bookings your guests cancel and move themselves, and a staff schedule priced against the covers those bookings put in the room. Digital menus with AI scanning and 14 EU allergen tags. Events with RSVPs and waitlists. Follow-up campaigns over email and SMS, with WhatsApp where your venue already uses it. A loyalty program with points, badges, and tiers. And a guest portal where your regulars manage everything themselves. One login, one dashboard, one bill. When a guest books a table or scans your QR code, their visit feeds directly into your campaigns and loyalty program without you lifting a finger.
We are a small team based in Slovenia. We built this because we saw hospitality businesses paying for four or five separate tools and still losing track of their regulars. There had to be a better way, so we made one.
What we believe in
Four principles that shape every decision we make.
- 01
Your guests, your data
GDPR-compliant from day one. Your guest list belongs to you, period. We will never sell, share, or hold your data hostage.
- 02
Simple by default
No engineering degree needed. If you can use a phone, you can run Guestavo. We handle the tech so you can focus on your guests.
- 03
Built to pay for itself
Every feature exists to help you bring guests back through the door. More repeat visits means more revenue, and that is the whole point.
- 04
Honest pricing
What you see is what you pay. No surprise fees after onboarding, no hidden limits buried in the fine print.
Infrastructure
How the project is put together
A practical overview of the stack behind Guestavo and what runs where today.
Project layout
ArchitectureGuestavo is built as a pnpm monorepo with thin apps on top and shared packages underneath for database access, billing, queues, storage, workers, emails, and common types. That keeps product logic centralized instead of scattering it across the web app.
Domains
CurrentGuestavo and Gustek are one deployment behind two domains. The domain decides the brand name and the default language, so each market gets its own front door without a second codebase.
DNS and edge
CurrentCloudflare is the control layer for DNS, SSL, and traffic routing, and uploaded files live in Cloudflare R2. Even when services sit with different providers, domain management stays in one place.
Staging
CurrentStaging runs the full stack against its own database and queue, so a change can be tested end to end on infrastructure we control before it reaches production.
Production
CurrentProduction runs on a Hetzner server we manage ourselves, with Dokploy building and deploying three containers: the web app, the API, and a background worker. PostgreSQL holds the data, Redis carries the queues and caching.
We describe the setup as it actually runs rather than as a plan, so branding, deployment, and operations stay aligned as Guestavo grows.