Security & compliance
Isolation is non-negotiable.
Schema-per-tenant isolation with a row-level-security backstop, AU Privacy Act alignment, and data residency in ap-southeast-2.
Tenant isolation
Schema-per-tenant, with an RLS backstop.
Each tenant's data lives in its own schema — a hard boundary — with row-level security as a second line of defence. A bug can't leak across tenants.
- Schema-per-tenant hard boundary
- RLS defence-in-depth
- Provision a tenant in under an hour
Tenant · isolation
Compliance & residency
Built for AU data residency.
Hosted in ap-southeast-2 with AU Privacy Act 1988 alignment, full audit logging, and customer-controlled retention.
- ap-southeast-2 residency
- AU Privacy Act aligned
- End-to-end audit logging
Audit · log
How it fits the workflow
Hard isolation
Schema-per-tenant means no shared rows.
RLS backstop
Defence-in-depth even if app logic slips.
AU residency
Data stays in ap-southeast-2.
Explore more of the product
Stop chasing updates. Start closing.
See how Florix plans the week, works offline, and keeps your pipeline fresh — book a 30-minute demo.