Clarus CLM
Contract Intelligence That Thinks at the Clause Level
Clarus treats every clause as a versioned, searchable, queryable entity — not a range of text inside a PDF. Amendments create new clause versions instead of overwriting documents, and search understands meaning, not just keywords.
Most CLMs store PDFs. Clarus stores clauses.
Traditional CLMs treat a contract as a file with metadata wrapped around it. Clarus decomposes every agreement into individually versioned clauses, tied to the vendor relationship, so every change has its own history.
Document-centric CLM
- • One PDF per amendment, stored side by side
- • Keyword search across file text
- • Version history at the document level
- • Obligations live in spreadsheets or tags
Typical vendor folder
The contract's current legal state lives across five files and a spreadsheet. Which clause is in effect? Good luck.
Clarus (clause-first)
- • Amendments rewrite specific clauses with full lineage
- • Hybrid semantic + keyword search over clauses
- • Version history at the clause level, not just the document
- • Obligations extracted from clause language
- • Amendment actions classified (Replace, Modify, Delete, Add, Add New Section)
- • Playbook deviations flagged inline as you read
- • Vendor-scoped search across MSAs, SOWs, and amendments
- • Missing-clause detection per document type
- • Reusable clause library drawn from approved language
- • Risk scoring and pattern analysis at the clause level
- • Signature-optional types can be marked in-effect by performance, payment, or email
- • Public review tokens with configurable expiry and read-only export
- • Real-time co-editing with presence and audit trail
- • Full contract history export as a structured bundle
Built for the way contracts actually work
Every feature is designed around clauses — the atomic unit of every contract.
Clause-first architecture
Every uploaded contract is segmented into classified clauses with immutable version history. Current-state text and full lineage live side by side.
Hybrid semantic search
Combines vector embeddings with full-text search, scoped to a vendor or across the whole portfolio. Find clauses by meaning, not just wording.
Amendment intelligence
Amendment language is detected and classified (Replace, Modify, Delete, Add, Add New Section) and applied atomically to the right clauses.
Playbook compliance
Define your approved clause language and thresholds. Clarus flags deviations inline in the editor so reviewers see risk as they read.
Type-aware workflows
31 document types mapped to the right approval and signature path. Signature-optional types (SOWs, POs, rate cards) can be marked in-effect by performance, payment, or email.
Obligations & renewals
Deliverables, payments, notices, and renewal dates are pulled from clause language into a tracked obligation list with configurable alert thresholds.
From upload to clause-level insight
Each contract flows through ingestion, extraction, and normalization — then you work with structured clauses instead of files.
Upload & ingest
Drag and drop PDFs, DOCX, TIFF, PNG, or ZIP batches. Parent-child relationships between MSAs, SOWs, and amendments are resolved automatically.
Extract & classify
Text is pulled via direct parse or OCR, segmented into sections, classified by clause type, and indexed for semantic retrieval.
Edit, approve, execute
Work in a rich-text clause editor with clause-level versioning, route through a 5-stage approval workflow, collect signatures, and track obligations once executed.
Enterprise-grade security, by default
Every tenant is isolated by database-level row-level security on every tenant-scoped table. Authentication uses httpOnly JWT cookies with CSRF double-submit protection. Server-side encryption at rest and TLS 1.2+ in transit.
Ready to rethink contract management?
Enterprise is live today. Starter and Enterprise Secure are launching soon — book a demo to see the platform and get early access.