RLS policies + composite foreign keys — the technical architecture ensuring branch-A data never leaks into branch-B.
Multi-tenant + multi-branch are two different isolation dimensions. Tenant isolates by company, branch isolates by location within the same company.
Technically: composite foreign keys (fk_id, tenant_id) ensure every query implicitly includes tenant_id. Plus PostgreSQL RLS as a second-line defense.
The result: 4 branches running on a single database, real-time aggregated dashboard, but data never mixes — even when a developer writes a wrong query.
Every attendance is an accounting event. Splitting payroll into separate software loses the truth — and forces end-of-month reconciliation from scratch.
StoryThe founder's story and the decision to skip off-the-shelf software — starting from 60 admin hours per month and 5 Excel files.
Try free for 14 days. No credit card. We help migrate your data.