Matters, ledgers and documents are scoped to the firm. Postgres row-level security enforces isolation on reads and writes. Firm roles from owner down to paralegal carry per-module permissions that authenticated server routes enforce, and provider keys and internal secrets are read on the server only. A matter record is simply what a fee earner sees from inside that boundary.
See how it is enforcedReview the platform with procurement, IT and compliance before signing. Every module is included; SCIM provisioning is available and SSO remains on the roadmap. Custom integrations and service commitments are scoped in your Enterprise agreement.
Per-firm tenant isolation
Postgres row-level security isolates every firm's data on shared infrastructure — enforced in the database engine, not just the application layer.
SCIM provisioning (SSO on roadmap)
Available now: SCIM v2 provisioning and deprovisioning of firm members from your identity provider, with a bearer token issued in Settings, Provisioning. On the roadmap: SAML 2.0 and OIDC single sign-on through Okta, Entra ID, Ping, or JumpCloud.
Data residency (Roadmap)
All data is stored in a single region today (Asia Pacific, Sydney). Planned: regional hosting across US, EU, UK, APAC, and India, with in-region storage and processing for local rules of professional conduct. Ask us before you commit if residency is a requirement.
Audit trail + retention
Role changes, ethical-wall changes, firm data exports and invoice finalization are logged with the person and the time. Per-module permission toggles are not yet audited. Firm retention settings you can align to state bar and regulator requirements.
Direct founder access
Direct access to the founding engineer who built the platform — no ticket tiers, no handoffs. Answers come from the person who wrote the code.
Custom integrations
Outbound webhooks to your existing billing, conflicts, and document management stack. Custom connectors are scoped and built under an Enterprise agreement.
Multi-office firms, in-house legal teams and regulated practices have different requirements. Plan the workspace configuration, access rules and review process around the way your team works.
Multi-office firms
Office-level roles, matter visibility rules, and conflict checking across your workspace — enforced by row-level security, no extra data warehouse required.
In-house legal
Budget tracking on matters, built-in approval workflows, and department-level workspaces for each business unit.
Regulated practice areas
AML/KYC workflows, conflict management with audit logging, and trust-account ledgers with built-in reconciliation for IOLTA reporting.
The outline below is a proposed six-week rollout, subject to your data, pilot results and agreed scope. The self-serve import brings over contacts, companies and matters from your export files; other records are not imported by it. Configure a pilot workspace and roles, then schedule training and go-live. Any managed migration work and incident-response coverage are defined in the signed agreement.
Plan a migration- Week 1Import contacts, companies and matters from Clio, MyCase or PracticePanther exports, or any CSV or XLSX file, and review them before they commit.
- Week 2Pilot workspace with a selected matter group and roles configured.
- Week 3–4Templates, workflows, and approval chains customized to your firm.
- Week 5Full user onboarding + 2 training sessions per practice group.
- Week 6Go-live with dedicated incident-response coverage for 30 days.
Review data residency, penetration testing and offboarding with IT, procurement and general counsel. Any service or compliance commitment must be written into a mutually signed agreement.
Talk to sales