Booking Bible
A multi-tenant booking and studio-management platform built to replace Mindbody — payments, streaming, AI assistants, and a public API. The engine under every other project on this site.
Run your studio.
- Orange
- Amber
- Cream
- Ink
Plain language. No jargon.
One platform under every brand in this index — bookings, memberships, payments, streaming and a public API, multi-tenant from day one. Studios keep their name, their rules and their revenue; the engine stays out of sight.
One codebase, many venues — every studio gets its own brands, staff, pricing and rules, isolated at the database layer.
Stripe with MobilePay, VAT engines per purchaser type, split tenders at the front desk, and receipts that satisfy Danish bookkeeping law.
Hybrid classes stream through Mux — an encoder, a QR code, and a phone can broadcast a class.
Admins ask questions and delegate tasks in plain language; every write the AI makes is reversible by design.
The same contracts the sister sites run on — schedule, checkout, gift cards, SSO — are the product's public surface.
Studios arrive with years of history in other systems; imports are dry-run first, guarded, and audited.
First lines written. Yoga Bible becomes the dogfooding operator — 5 brands, ~150 clients, ~15 staff.
Mindbody switched off. Payments, bookings, memberships and streaming all live on Booking Bible.
Opened beyond yoga: from practitioners to salons, 19+ verticals on a plan ladder from free to enterprise.
Software a studio
can trust.
Why it exists
The room adapts per project: for the platforms this section carries screenshots, dashboards and an architecture sketch instead of interior photography.
Every studio in the ecosystem below runs its bookings, payments and schedules through this one platform — so this is the room where the diagram lives: tenants, plans, webhooks, the parts nobody visits but everything depends on.
The engine room
Every other project on this site is a customer of this one. The studios book through it, the streaming sites authenticate against it, the marketing suite listens to its webhooks. Building the whole ecosystem on one platform wasn't the business plan — it was quality control. If a feature annoys the founder at his own front desk at 07:58, it gets fixed.
It is also the most disciplined codebase in the house: staging-first migrations, kill switches on every risky subsystem, append-only audit logs, and a session log that remembers every change since the first commit.