Lawra Conflict Check
lawra.io
- Web
What Lawra Conflict Check is
Lawra Conflict Check is a web tool that searches a firm's client and matter database for potential conflicts and scores each result by severity. Its semantic matching can find connections involving shared parties, beneficial ownership, subject matter, or doctrinal position. The tool classifies direct, positional, and business conflicts, then assigns a score from 1 to 10 with a plain-language explanation. It recommends proceeding without a waiver, proceeding with a waiver, or declining, based on jurisdictional ethics rules. Each check records its timestamp, inputs, results, and decision; Lawra describes the audit trail as SOC 2 and bar-evidence ready. Listed uses include matter onboarding, lateral-hire client-list checks, and building a database from billing records, email, and engagement letters. Lawra says hosted SaaS runs on Google Cloud Firebase, supports multi-region residency needs, and uses TLS 1.3 for traffic and AES-256 for stored data. The company says it does not sell, rent, or repurpose customer data and does not use it in an internal model-training pipeline. Prices are described as USD billed monthly, but no Conflict Check-specific price is shown. Lawra lists GDPR and LGPD as compliant; SOC 2 Type II, ISO 27001, and ISO 42001 are roadmap items with 2027 targets.
Who it suits
Lawra presents Conflict Check for mid-size firms, boutiques, solo practitioners, firms with frequent lateral hires, and firms that still rely on manual checks. It may suit teams formalizing conflict reviews during onboarding or lateral hiring.
Good to know, and what to watch
- Semantic matching covers parties, ownership, subject matter, and doctrine.
- Scores conflicts from 1 to 10 with explanations.
- Recommends a course based on jurisdictional ethics rules.
- Logs check inputs, results, timestamp, and decision.
- Supports multi-region residency needs.
- No Conflict Check-specific price is shown.
- SOC 2 Type II is a roadmap item, not a completed certification.
The verdict
Lawra Conflict Check pairs semantic matching with severity explanations, recommendations, and a recorded audit trail.
What the maker publishes
- AI confidentiality
- For registered paying customers, Lawra says sensitive entities in documents are tokenized before content reaches an AI provider and the original document does not leave Lawra’s perimeter. source
- Audit trail
- Each check is logged with its timestamp, inputs, results, and decision; the page describes this as SOC 2 and bar-evidence ready. source
- Audit trail
- Each check is logged with its timestamp, inputs, results, and decision; the page describes the trail as SOC 2 and bar-evidence ready. source
- Certification status
- Lawra lists SOC 2 Type II, ISO 27001, and ISO 42001 as roadmap items with 2027 targets; it lists GDPR and LGPD as compliant. source
- Company
- Lawra identifies Carlos Miranda Levy as its founder and Innovator in Chief. source
- Conflict types
- The tool identifies direct, positional, and business conflicts and scores each from 1 to 10 with a plain-language explanation. source
- Conflict types
- It identifies direct, positional, and business conflicts, each scored from 1 to 10 with a plain language explanation. source
- Data handling
- Lawra says it does not sell, rent, or repurpose customer data and does not use customer data in an internal model-training pipeline. source
- Data isolation
- Lawra says documents and conversations are isolated by matter and that privileged work product is flagged and segregated. source
- Data protection
- Lawra says its hosted SaaS runs on Google Cloud Firebase, uses TLS 1.3 in transit and AES-256 at rest, and supports multi-region residency needs. source
- Data residency
- The hosted SaaS runs on Google Cloud (Firebase) with multi-region capability, while Sovereign Suite deployments run inside the customer's infrastructure. source
- Encryption
- Lawra's security page states that client/server traffic uses TLS 1.3 and stored data uses AES-256 encryption. source
- Integrations
- Lawra says its broader platform interoperates with systems such as courts and registries, accounting, HR, document management, signature platforms, and payment rails; the Conflict Check page names no specific integrations. source
- Intended users
- The product is presented for mid-size firms, boutiques, solo practitioners, firms with frequent lateral hires, and firms relying on manual conflict checks. source
- Intended users
- The product is described as best for mid-size firms, boutiques, and solo practitioners relying on manual conflict checks, especially firms with frequent lateral hires. source
- Matching
- Semantic matching can detect conflicts involving shared parties, beneficial ownership, subject matter, or doctrinal position. source
- Matching
- Semantic matching looks for shared parties, beneficial ownership, subject matter, and doctrinal position beyond keyword search. source
- Pricing
- Lawra’s pricing page says displayed prices are in USD and billed monthly, but it does not show a Conflict Check-specific price in the page content reviewed. source
- Pricing availability
- The pricing page says prices are in USD and billed monthly, but the opened page does not show individual plan prices or plan details. source
- Purpose
- Lawra Conflict Check runs semantic conflict checks across a firm's client and matter database and scores each conflict by severity. source
- Purpose
- Lawra Conflict Check runs semantic conflict checks across a law firm’s client and matter database and assigns severity scores. source
- Recommendations
- For each conflict, the tool recommends proceeding without a waiver, proceeding with a waiver, or declining based on jurisdictional ethics rules. source
- Recommendations
- For each conflict, the product recommends proceeding without a waiver, proceeding with a waiver, or declining based on jurisdictional ethics rules. source
- Security certification status
- Lawra lists SOC 2 Type II as a 2027 roadmap item and says no audit is under way; the product page separately calls its audit trail SOC 2 ready. source
Checked against the maker's pages on 5 Oct 2026.