BellaVista Project
Self-hosted booking & website platform
Hey Indie Hackers 👋
I just launched BellaVista — a self-hosted booking & website platform I’ve been building for quite a while.
The idea came from a simple frustration:
Most booking solutions are either heavy SaaS platforms, plugin-based CMS setups, or tools that lock you into subscriptions and third-party dependencies.
BellaVista started as an internal tool for accommodation websites.
Over time, it evolved into a full system I could actually own, extend, and reuse for real-world projects — without vendor lock-in.
It’s not a template and not a SaaS.
It’s a production-ready, self-hosted system built for people who want control.
I’d love some honest input:
• How do you usually approach building booking or niche websites today?
• And if you were in my position — where would you focus first to market something like this?
Happy to answer questions and really appreciate any feedback 🙌
30 Comments
I like the framing around ownership. ~
It’s usually not a starter feature, but it gets very compelling once someone’s already been burned.
From what I’ve seen, booking tools split people pretty cleanly:
Early-stage folks want speed and sensible defaults
Later-stage folks want control because something already broke
Your pitch feels much more aligned with that second group.
One thing that’s helped me with similar products is focusing the story on when someone switches, not what they’re switching to. “After Stripe changes pricing.” “After a plugin update breaks bookings.” “After a client asks for something the SaaS just can’t do.” Those moments create urgency.
On the build side, I default to boring-but-safe stacks until pain forces complexity. Booking is unforgiving — miss one edge case and users lose money or trust fast.
If you had to pick one scenario where BellaVista is the obvious answer, what would it be? Small hotels? Rentals? Agencies managing multiple sites?
Once that’s clear, it feels like both the product and the marketing get a lot easier.
This is a great breakdown - and I agree with you.
BellaVista is definitely not a day-one tool. It’s much more aligned with the moment after something broke or became limiting.
In practice, the switch tends to happen after things like:
a plugin update breaking bookings
a SaaS roadmap blocking a client request
pricing or policy changes outside your control
managing multiple properties or sites becoming painful
or simply hitting hard limits around customization and personalization
If I had to pick one scenario where BellaVista is the obvious answer, it’s developers or agencies managing multiple accommodation sites - especially once they’ve outgrown templates or hosted platforms
That group has usually felt the pain already and values predictability and ownership over speed. They don't want to rebuild booking logic over and over, but they also don’t want to fight against someone else’s constraints for years.
I also like your point about boring-but-safe stacks. Booking is unforgiving, you are right, and that mindset influenced a lot of my early decisions.
Framing the story around when someone switches rather than what they switch to is a really helpful insight - appreciate you sharing that - this is exactly the kind of perspective I was hoping to get here! :)
it`s nice
Love the ownership-first angle 👏
Too many booking setups today mean SaaS lock-in or bloated plugins.
If I were you, I’d start with a tight niche + real case studies to show why self-hosted actually wins.
Curious who you see as the first ideal user for BellaVista?
Thanks, I agree with that
The ownership angle really starts to matter once someone has already felt the pain or hit platform limits.
For a first ideal user, I see developers or small agencies managing multiple accommodation sites - especially once they’ve outgrown templates or hosted platforms.
They usually want a predictable core they can reuse, extend, and control, instead of rebuilding booking logic for every project or fighting SaaS limitations. That was exactly the situation that led me to start building BellaVista :)
I like your point about case studies too - focusing on real switch moments rather than abstract benefits feels like the right next step
Hello
Hey, nice to meet you
замечательная новость и я уже спешу глянуть на твой сайт
О, большое спасибо за ваши слова! Если у вас возникнут вопросы, я с радостью помогу. В противном случае буду рад получить обратную связь или предложения по улучшению)
good
Thank you so much!
Why bella?
Fair question
“Bella” comes from the Italian phrase "bella vista" - so “beautiful view”
I started building the project while working on accommodation websites in Italy, and I wanted a name that keeps the focus on the property itself, not the platform or a brand.
So the name stuck
That sounds really interesting, I'll definitely check it out!
Thanks, appreciate it!
If you end up taking a look and have any questions or feedback, I’d love to hear it :)
Love this
I appreciate that, thank you
fasfa
ffbhfd
54654
it`s nice
it`s nice
Yess that is great. I wish i would be like you. I love you man
prifict
Looks great!
Exactly, ownership only becomes a priority after someone has hit real friction.
What you’re describing with developers and small agencies mirrors what I’m seeing with insurance agents: once they outgrow templates, CRMs, or generic tools, the real pain shifts to execution and control, not features.
I like your point about “switch moments.” That’s where the signal really is, not abstract benefits, but the moment people realize their current setup is holding them back.
Curious: when you were building BellaVista, what was the clearest signal that made you say “we can’t keep doing it this way”?
good
This comment was deleted 7 months ago
This comment was deleted 7 months ago
This comment was deleted 7 months ago