One platform. Many salon chains. Each chain's data kept private.
Gloup is salon software. It lets many salon chains and branches run on one shared system, while each chain sees only its own data.
The situation
Running one salon is simple: appointments, stock and staff schedules. But salon chains are not separate islands. Owners want one view of the money. Branch managers must never see another branch's customers, staff pay or stock.
The initial inclination for many teams is either to deploy separate database instances per location (expensive, impossible to maintain) or write ad-hoc WHERE location_id = ? filters in every application query (dangerous and vulnerable to human error).
Salon B ── Database B
Salon C ── Database C
Result: Zero unified view
┌─────────┼─────────┐
Salon A Salon B Salon C
Atomic Isolation · Centralized Ops
The real problem
The tricky part was where one customer ends and the next begins.
The problem was not just a busy Saturday of bookings. It was keeping each chain's data separate while still letting owners see the combined picture.
Branch managers needed to change schedules instantly. At the same time, regional directors needed live reports across many locations, without freezing the checkout screens.
We wanted a guarantee: even if a developer forgot a safety check on a new feature, the system itself would stop one chain from seeing another's data.
What we did
Instead of patching the existing code, we rebuilt the foundations:
Every request knows who it belongs to
Every signed-in request is tagged with the chain it belongs to as soon as it arrives. The database then only shows that chain's data, without developers having to remember anything.
Privacy enforced by the database
The database itself enforces who can see which rows, even for custom reports. A developer cannot accidentally expose another salon's client records.
Reports that don't slow down checkout
We moved the combined reports away from the live booking and checkout system, so owner dashboards update quickly without getting in the way.
Clear roles for owners and staff
Owners can decide what each staff member is allowed to do, review price changes, and move stock between branches easily.
The Result
One platform that works reliably for many salon chains.
Gloup took on several salon chains without redesigning the system or setting up a separate database for each new client.
Branch managers get fast local appointment booking, while franchise headquarters receive consolidated financial rollups from the same platform.
Some details are generalised to respect client confidentiality. Specific figures are shared on a call.
What we learned: keeping customers apart is not just a database decision.
Many teams treat this as an afterthought: "we'll just add a company column." In reality it touches everything: how background jobs run, how saved copies are kept, how changes are tested, and how failed messages are retried. Planning for it early saves expensive emergency rewrites later.
Have a system that's getting harder to change?
Tell us what is going on. You will talk directly to Rajesh, with no sales handoff.
Request an Architecture Review →