For multi-clinic & DSO
One PMS, every clinic, one version.
For groups operating two to twenty clinics under one organisation — where the office manager runs the chair and the COO runs the spreadsheet that consolidates everything. Oralstack's tenant model is built for this from day one, not bolted on after a single-clinic install became popular.
Built for the people consolidating across clinics
The buyer for a multi-location group is rarely the front desk — it's a VP of Ops, a COO, or a Director of Clinical Operations. They live in dashboards and consolidated reports. Their question isn't “does this work for one clinic” — it's “does this give me one consistent view across all of them?”
What multi-clinic ops actually need · 1
Tenant isolation, not multi-database juggling.
Most legacy PMS were built for one clinic and adapted to multi-clinic later — typically by running a separate database per clinic, with reconciliation reports that pull from each one. Oralstack uses Postgres row-level security to enforce per-clinic data separation in a single database, with one login that surfaces every clinic the operator has access to. No DBAs, no consolidation pipelines, no reporting drift.
What multi-clinic ops actually need · 2
One version across every clinic.
Version drift is the silent killer of multi-clinic operations. Clinic A is on PMS version 14.3.1; clinic B is still on 13.8 because the upgrade got deferred. Reports don't reconcile. Front-desk staff who rotate between clinics learn two slightly different products. Oralstack deploys continuously: every clinic in the group is on the same version every week.
What multi-clinic ops actually need · 3
Operations analytics that surface where operators look.
Chair utilisation across all locations, by chair and day. Revenue per chair by clinic, week-over-week, with delta callouts. Recall coverage rate per location. No-show rate trended in clinic-local timezones. Daily snapshot in the dashboard, weekly digest in the inbox — built for the COO who wants the punch list, not the spreadsheet pull.
What it costs
$200 × clinics
Pilot pricing scales linearly per clinic. No tier upcharges for multi-clinic features. Multi-location and group discounts on request once the pilot proves out.
Talk to us about a group pilot. Full pricing →
Questions multi-location operators ask first
- Tenant isolation: Postgres row-level security enforces per-clinic data separation at the database layer, not the application layer. Security posture →
- Audit logs: every read and write is logged with user, clinic, and resource. Queryable per-clinic for PDPC, IRAS, or internal audits. What auditors look for →
- Migration: we run group migrations clinic-by-clinic, on a three-week cadence per location, no fallback diary kept in parallel. The migration playbook →
- Reporting: chair utilisation heatmap, revenue per chair, recall coverage, no-show trend — all timezone-correct per clinic. Operations workflow →
Talk to us about a group pilot.
Tell us how many locations, what your current PMS is, and a target start date. We come back with a tailored pilot proposal — usually a two-clinic pilot first, then group rollout — within two working days.