← All projects

MERN · Stripe · Socket.io

Multi-Tenant Booking & Subscription Platform

A white-label booking SaaS: each business gets its own branded site, staff calendars, deposits and recurring plans, all on one codebase.

ReactNode / ExpressMongoDBStripeSocket.ioAWS
Staff calendar with live bookings
Services and membership plans
Owner dashboard: revenue and bookings

Screens are illustrative layouts of the product, not client screenshots.

Overview

What it is

A booking platform that many businesses use as their own. Each tenant gets a branded booking site, staff calendars, services and pricing, deposits and recurring membership plans, while the team maintains a single codebase.

The problem

Why it was needed

Small service businesses juggle calendars, payment links and spreadsheets, and off-the-shelf tools either look generic or charge per seat. The goal was a branded, subscription-ready booking product that onboards a new business in minutes.

1 codebaseserves every tenant with its own branding
Livecalendar changes appear instantly for everyone
Auditedevery payment event is logged and retried safely

Features

What We Built

Tenant branding

Logo, colours, domain and booking rules per business.

Staff calendars

Availability, breaks, services and buffers per team member.

Deposits and plans

One-off deposits and recurring memberships through Stripe.

Live updates

Socket.io keeps calendars in sync across staff and client screens.

Roles and access

Owner, staff and client roles with tenant-scoped data.

Billing events

Webhook handling with idempotency, retries and an audit trail.

Architecture

How It Fits Together

  1. React appsclient booking, staff, owner
  2. Node / Express APItenant-aware, role-based
  3. MongoDBtenant-scoped collections
  4. Socket.iolive calendar events
  5. Stripepayments, plans, webhooks
  6. AWShosting, storage, email

Every query is scoped by tenant, so one deployment safely serves many businesses.

Roadmap

From Idea to Launch

A typical delivery roadmap for a project of this kind.

  1. 1

    Discovery

    1 week
    • Map the booking journey for each business type
    • Decide the tenancy model and branding limits
    • List payment and plan rules
  2. 2

    Core booking

    2-3 weeks
    • Services, staff and availability engine
    • Booking flow and confirmations
    • Tenant onboarding
  3. 3

    Payments

    2 weeks
    • Deposits and refunds in Stripe
    • Recurring plans and failed-payment handling
    • Webhook processing with an audit trail
  4. 4

    Realtime and admin

    2 weeks
    • Socket.io live calendar
    • Owner dashboard and reports
    • Notifications by email and SMS
  5. 5

    Launch

    1 week
    • Load and permission testing
    • Pilot tenants
    • Documentation and support setup

Want something like this?

Tell us what it should do and we'll come back with a stack, a scope and a timeline.