System of insight, not system of record.
Your practice-management platform stores what happened. Praesensus tells you what it means. Five layers. One codebase. Three deployment postures. Every architectural choice is documented, measurable, and reproducible.
The fundamental distinction
Clio, Filevine, MyCase, Smokeball, iManage, NetDocs, Relativity — every legal-technology platform in market today is a system of record. It stores case data, tracks time, manages documents, automates forms. Each is a silo. Each sees only what you enter into it. AI features, where present, answer questions about data already inside that system.
Praesensus is a system of insight. It reads from every system of record the firm already uses — without replacing any of them — fuses the signals into a live operational picture, recommends the next action, governs it through a named-person approval ladder, and measures its own accuracy against real data.
The shift changes the operating posture of the practice. Instead of attorneys manually correlating information across platforms, the intelligence layer does it continuously. Instead of deadlines depending on someone's memory, they are projected from events. Instead of contradictions hiding until litigation, they surface on detection. Instead of governance depending on discipline, it is enforced by architecture. Instead of AI accuracy being a matter of faith, it is a matter of measurement.
The five layers
Litigation · Contracts · Compliance · Personal Injury
Ingest · Extract · Reason · Export
18 node types · 16 edge types · genuinely new IP
Seven-stage deterministic pipeline
Read-only adapters. One-way ingress.
The 7-stage Legal State Spine
Every advisory travels the same seven-stage pipeline. Deterministic. Reproducible. Explainable at every stage.
OBSERVE
NORMALIZE
DETECT_STATE
DETECT_TRANSITION
ESTIMATE_OUTCOME
RECOMMEND
VALIDATE
Perception vs. authorization
22 capabilities across 4 domains
Every claim Praesensus makes about the intelligence layer breaks down into 22 specific, measurable capabilities across four architectural domains. Every one has a corresponding entry in the competitive comparison — and in every one the structural difference between a system of record and a system of insight produces a qualitative gap no amount of incremental feature development on the record-keeping side can close.
Intelligence & Analysis
Architecture & Integration
Governance, Risk & Accountability
Portfolio & Operational View
Validated accuracy
Every competitor markets AI-powered features. None publishes accuracy metrics against public legal benchmarks. Praesensus does.
72.9%
96.9%
75.6%
Three deployment modes
Air-gapped first. Same codebase. Same behaviour. Deployment posture is a config flag, not a build target.
Air-gap on-prem
Best for: Healthcare payer, defence contractor, F100 regulated finance, government legal.
On-prem connected
Best for: Am Law 50-100, F500 GC offices.
Cloud tenant
Best for: Mid-market in-house, SaaS-native firms, PE portfolios.
Four appliance forms
Physical
Virtual
Container
Cloud SaaS
Integration surface
Praesensus integrates with the standards-based half of firm IT via native protocols (no custom shim required), and with the legal-vendor-specific half via read-only plugin adapters.
Standards-based (no custom code required)
| Category | Common vendors | Protocol |
|---|---|---|
| Identity provider | Azure AD, Okta, Ping, ADFS | SAML 2.0, OIDC |
| Directory / roster | Same as above | SCIM 2.0, LDAP, CSV bulk |
| SIEM / monitoring | Splunk, QRadar, Sentinel, Datadog | syslog, Splunk HEC, webhook |
| PKI / certificates | Firm CA, DigiCert, Entrust | X.509, PKCS#12 |
| Backup / snapshot | Veeam, Rubrik, Cohesity, Commvault | Standard VM snapshot APIs |
| Vulnerability scan | Rapid7, Qualys, Tenable | Standard VA agents inside appliance |
Legal-vendor-specific plugin adapters
| Category | Vendors |
|---|---|
| Email / Calendar | Microsoft 365, Google Workspace, on-prem Exchange |
| Document management | iManage, NetDocs, SharePoint, OpenText eDOCS |
| Matter / practice management | Clio, Filevine, MyCase, Smokeball, Litify, Aderant Elite, Elite 3E |
| Contract lifecycle mgmt | Ironclad, Icertis, ContractPodAi, Agiloft, DocuSign CLM |
| eDiscovery | Relativity, Everlaw, DISCO, Reveal |
| Court + docket | PACER, state e-filing, docket-alert services, CourtListener |
| Legal research | Westlaw, Lexis, Bloomberg Law, Fastcase |
| Billing / time | Aderant Elite, Elite 3E, TimeSolv |
Federation architecture
The Federation is the anonymised pattern-intelligence network that enables cross-firm benchmarks and standard-form defect detection. It operates without ever accessing your privileged content.
Federate patterns, not privileged content. The Federation processes only derived typed structure and outcome patterns — clause frequency signatures, deadline pattern statistics, judge outcome distributions, standard-form defect signals. It never processes and never accepts privileged text, client identifiers, matter identifiers, or attorney communications. Enforced architecturally.
Asymmetric flow
- Downstream (Praesensus → customer): daily authenticated pull. Fresh federated intelligence in.
- Upstream (customer → Praesensus): monthly signed push. Human-inspectable pattern digest out.
Authentication
Two-factor machine authentication for automated pull: mTLS client certificate (90-day rotation) + hardware-backed signed request token (HSM/YubiKey PIV). Optional weekly or monthly human Custodian Seal Renewal.
Composed foundations
Praesensus is the fifth vertical instance of the Atlas platform family. Every core module — the seven-stage spine, the governance gate, the transition detector, the deadline forecaster, the validation harness, the runtime, and the plugin surface — is lifted intact from production-tested siblings serving buildings, biopharma manufacturing, genetics, and critical facility infrastructure.
The Combining Layer + Knowledge Graph is the genuinely new IP for legal. Composition beats invention.
Zero third-party runtime dependencies. No LLM API calls at runtime. No SaaS AI providers. No vendor lock-in for the reasoning layer. The entire product runs on stdlib-only Python with rule-based classifiers — which is why air-gap deployment is a config flag, not a special build.