Isolation by design
The platform is multi-tenant by design. Every client's data is scoped at the application layer and enforced in the database with PostgreSQL row-level security (RLS), so one tenant can never reach another's data.
What this looks like in practice
- Every query is scoped to your organization at the application layer.
- Isolation is enforced a second time inside the database with PostgreSQL row-level security (RLS).
- Rows outside your tenant simply don't exist for your session — even a bug in application code still hits the database's wall.
Why it matters
One client can never reach another's data. That guarantee doesn't rest on a developer remembering to add a filter — the database enforces it on every row, every time.
- Multi-tenant by design
- App-layer scoping
- PostgreSQL row-level security
- Defense in depth
Have a security question?
We're happy to walk through our practices in more detail, share documentation, or hear about a concern. A human reads every note.
This page describes our security posture at a high level for transparency; it is not a contractual commitment.