Booking platform workspace

Platform architecture

A multi-tenant foundation for booking groups and SaaS operators.

Each company operates independently while the platform admin can oversee tenants, users, settings, and company performance from one product.

Tenant boundary

Company-scoped records by default.

The platform links operational records to a company so a booking company can only work with its own users, providers, customers, services, bookings, availability, payments, and settings.

Company

Brand, slug, plan, status, website, and account details.

Users

Admins, providers, staff, and customers attached to one tenant.

Booking data

Appointments, availability, services, and payments scoped per company.

Settings

Booking rules, widget text, notices, and confirmation content.

Access model

The right dashboard for every role.

Platform admin

Creates companies, manages tenant users, and reviews company-level settings.

Company admin

Runs the company dashboard, services, calendar, team, payments, and integration settings.

Provider

Manages their own appointment calendar, statuses, notes, and custom calendar blocks.

Customer

Books online and views their own appointment history inside the correct tenant.

Integration

Embed-first distribution.

Companies can keep their existing websites while adding a tenant-specific booking entry point that routes customers into the right company context.

<script src="/booking/launcher.js" data-company="company-slug" async></script>

Scale path

Ready for many companies.

The data model is structured for SaaS growth: add more companies, add teams inside each company, and preserve separation across every booking workflow.

Talk through rollout