Booking & Scheduling Platform Templates

Multi-tenant booking platforms for salons, spas, and appointment-based services. Scheduling, Stripe payments, reminders, and custom domains.

Booking

Multi-Tenant

Salon & Spa

Scheduling

Custom Domains

Stripe

1 template available

BookEase Multi-Tenant Booking Platform

A launch-ready multi-tenant salon and spa booking platform built as one shared Fastify backend plus one shared Next.js web app, with one tenant database per business. It includes a control-plane for platform users, tenant registry, memberships, domains, audits, and migrations, while each tenant database owns services, staff, schedules, blocked times, customers, appointments, booking settings, payments, reminders, and tenant audit logs. The frontend runs in platform mode and tenant mode from a single codebase, using a host-aware BFF layer so tenant identity is resolved from the request host rather than browser-visible tenant ids. Public booking flows support service selection, optional staff selection, live availability, Stripe checkout, booking status polling, runtime tenant theming, and tenant admin surfaces under /admin. The platform also ships with branding controls, custom domain verification, demo reset and verify commands, worker processes for reminders and hold expiry, and localtest.me based launch testing. Ideal for salon chains, spa groups, appointment-based wellness brands, or founders building a white-label multi-tenant scheduling SaaS.

4.7$129

What you get

Booking and scheduling platform templates are multi-tenant SaaS starters — one codebase serving many businesses, each with its own database, branding, and custom domain. The reference implementation (BookEase) targets salons and spas but the architecture generalizes to any appointment-based service.

These templates include a control plane for platform operators (tenant provisioning, domain verification, audits), tenant-specific admin surfaces (services, staff, schedules, settings), and public booking flows with live availability and Stripe checkout.

The database-per-tenant model keeps tenant data fully isolated — important for compliance and trust with business customers. Host-aware routing resolves the tenant from the request host rather than exposing tenant IDs in URLs.

Best for

Founders building a white-label scheduling SaaS
Salon and spa chains that need a multi-location booking system
Service businesses (fitness, wellness, repair, coaching) needing appointment management
Agencies delivering multi-tenant scheduling to small business clients

How to decide

Database-per-tenant isolates risk

Single-database multi-tenant designs are cheaper to run but one bad query can leak data across tenants. Database-per-tenant is the safer default for any SaaS touching customer data.

Host-aware routing is production-grade

Resolving tenants from the request host (rather than a URL path parameter) lets each tenant use a custom domain and keeps tenant identity server-side through the BFF layer.

Frequently asked questions

Can tenants use their own custom domains?

Yes. The platform includes domain verification and routing so each tenant can connect a custom domain. The reference implementation uses localtest.me for local development of the multi-host flow.

Does this work for services other than salons?

Yes. Services, staff, schedules, and booking rules are all generic. The salon/spa branding is cosmetic — the core model works for any appointment-based business.

Related Collections

Grocery Subscription

Subscription commerce platforms

Offers & Rewards

Coupons and cashback platforms

Next.js Templates

SSR storefronts

Ready to launch your store?

Every template ships with source code, documentation, and free updates. Pick a starter kit and go live in days, not months.

Browse All Apps View Templates