Multi-Tenant or Dedicated Database? A Practical Guide for Law Firms
When your practice grows past 50 users, the question of database isolation stops being theoretical. Here's the honest tradeoff matrix.
For small firms, a shared multi-tenant database is the right answer almost every time — it's cheaper, faster to set up, and the row-level isolation provided by modern SaaS platforms is genuinely sufficient for confidentiality.
But there's a tipping point. Once a firm crosses about 50 active users or starts handling matters with explicit data-residency clauses, the questions change.
When dedicated DB starts paying for itself
- Bar Council audit clauses that require provable physical separation
- Litigation against the SaaS vendor's other tenants becoming legally awkward
- Compliance reviews that demand independent backup + restore drills
- Performance — extremely large firms running deep reports against years of cause-list data
When dedicated DB is overkill
If your firm is under 20 users and your matters don't involve government data residency rules, dedicated databases mostly add cost and operational overhead without changing the day-to-day. The shared tier in AssociatesDiary already isolates tenants at the row level via every query — there's no situation where Firm A can read Firm B's data.
What's important is that the platform supports both — and lets you upgrade later without losing data. The 'Hybrid SaaS' design in AssociatesDiary lets a tenant move from Shared to Dedicated with a single host-admin click, and the existing rows are migrated transparently.