Built like it holds your licence. Because it does.
Archer Hub carries your buyers, your vendors and your compliance record. This page says plainly how that data is protected, in claims you can test on a walkthrough, written by the people who built it.
Your agency’s data is walled off
Multi-tenant isolation is enforced at the database, not just in application code.
- Row-level security enforced on every tenant table
- Every query runs inside your agency’s scope; the database refuses anything else
- Agency identity comes from the authenticated session, never from the request
Access is earned, on every request
Roles are checked server-side each time, not once at login.
- Principal, office manager, sales and leasing roles, enforced fail-closed
- Only principals can invite, remove or change team access
- Authentication by Clerk, with two-factor authentication available
Records that cannot be quietly edited
The registers that protect your licence are append-only by design.
- Key custody ledger: the database itself blocks edits and deletions
- Property lifecycle history: every stage change written, permanently
- Compliance actions land on tamper-evident audit trails
Built and supported in Australia
Your data and the people responsible for it are here.
- Australian data residency
- AI drafts are reviewed by your team; nothing sends itself
- No lock-in: your data is yours, and exports are part of the product
No security theatre. Ask us anything.
We will not claim certifications we do not hold or paste a wall of badges. What we will do is walk your team, or your IT advisor, through exactly how isolation, access control and audit trails work, on the real system.
Security questions get engineering answers, from the engineers. Email hello@archerhub.app and it lands with the people who wrote the code.
Bring your hardest question to a walkthrough