Platform architecture
Every company lives in complete isolation on a shared, multi-tenant foundation. One product instance, any number of companies, each with its own team, services, customers, and booking flow.
Tenant model
All operational data, users, providers, customers, services, bookings, payments, and settings, belongs to a company. Staff only ever see their own company's records.
Platform admin
Tenants
Create & manage
Users
Invite & roles
Settings
Plans & status
Bloom Hair Studio
Serenity Spa
Complete data isolation between companies
Access model
Five distinct roles, each with their own interface. No user ever sees another company's data or menus they don't need.
Platform admin
Creates tenants, manages users across all companies, oversees plans and account status.
Company admin
Full company dashboard: services, calendar, team, customers, payments, and widget settings.
Provider
Personal appointment calendar, notes, status management, and custom blocks.
Customer
Books online and views their own appointment history within the correct company booking flow.
Distribution
Each company gets a tenant-specific snippet. Drop it on any website to give customers a branded booking entry point that routes directly into the right company context.
<script src="/booking/widget.js"
data-company="your-slug" async>
</script>Scale
The data model is structured for SaaS growth: add more tenants, build bigger teams inside each one, and preserve complete data separation across every booking workflow as you scale.
∞
Companies
∞
Providers
∞
Services