Every clinic, studio, salon, and venue runs on the same primitive: someone books a slot, someone gets paid, and something has to make sure the same room isn't double-sold. The tools that serve them are mostly rented SaaS — one-size-fits-all calendars that the business owner never truly owns, that hold the booking data on someone else's servers, and that resist the vertical-specific workflow every niche actually needs. That gap is the opportunity. If you know a vertical well enough to shape onboarding, terminology, and the exact booking flow it wants, you can build a booking-management SaaS that businesses buy because it fits them, not despite the fact that it doesn't.
This guide is about building that product on VBWD: a multi-tenant scheduling platform you sell to many businesses, where each business is a tenant, each tenant runs its own bookings, and you own the whole stack — code, data, and the customer relationship.
VBWD is a self-hosted, source-available full-stack SDK: one Python backend core, a Vue/TypeScript web front end, and native iOS and Android SDKs — all driven from the same backend. The core is agnostic, and capabilities live in a plugin system where features toggle on and off without a restart. For a booking product, several of these plugins map almost directly onto what you'd otherwise build from scratch:
These aren't aspirational names. Real vertical products already run on VBWD as proof the extension model works: a tarot booking app, a dice-market game (bdv), and a pharmacy shop (shop_pharma). The booking engine, billing, multi-tenancy, and integration seams are the parts you'd least want to reinvent — and they're the parts VBWD hands you.
VBWD is not a finished booking product you can rebrand and resell. It is a booking engine and a set of seams. What it deliberately does not do is your vertical.
The booking plugin knows about appointments, rooms, spaces, and seats — it does not know that a physiotherapy clinic needs 20-minute follow-ups blocked differently from 60-minute initial assessments, or that a music studio charges by the room-hour with an equipment surcharge, or that a wedding venue needs a hold-then-deposit-then-confirm flow with a contract attached. Those workflows, the onboarding that makes a non-technical salon owner productive in ten minutes, the terminology, the reminders, the no-show policy, the exact booking UX — that is your product. That is what you're actually selling, and it's what VBWD refuses to guess at so you can build it right.
Put plainly: VBWD gives you the booking engine, billing, multi-tenancy, native apps, and the integration seams so you're not rebuilding them. You bring the vertical-specific workflow, the UX, the onboarding, and the domain judgement. The line is clean, and staying honest about it is what keeps the build tractable.
The core workflow, concretely:
The natural model is per-seat or tiered SaaS, billed through the subscription plugin: a starter tier for a solo practitioner, higher tiers as a business adds staff, rooms, or locations, with add-ons for things like native app access or advanced integrations. You set the tarif plans; checkout, renewals, and add-ons are already handled.
The deeper argument is ownership. Booking data is sensitive — it's who went where, when, for what, often health- or appearance-adjacent. When you build on a self-hosted, source-available stack, that data lives on infrastructure you and your customers control, not inside a hosted platform that can change terms, raise prices, or fold. You own the source, so you can extend any workflow instead of waiting on a vendor's roadmap. And you own the customer relationship directly, rather than reselling someone else's hosted tool and hoping they don't eventually sell to your customers over your head. Renting a platform means every one of those levers belongs to someone else. Owning the stack means they belong to you.
The fastest way to see the pieces fit together is to run it. Clone the public SDK and stand up the backend, the web front end, and the plugins on your own machine:
github.com/VBWD-platform/vbwd-sdk-public
If you're building this as a commercial product and want a managed enterprise installation, a walkthrough of the booking and multi-tenant seams, or help scoping the vertical, get in touch:
VBWD is source-available under BSL 1.1 — free for commercial use while annual VBWD-attributable sales stay under the value of 6.7 BTC per year.
Build a business with VBWD — the series:Mobile game · Travel aggregator · Marketplace · Booking SaaS (this one) · AI assistant SaaS