CloudLex vs EvenUp: how they compare in 2026

C
CloudLex profile
E
EvenUp profile
Last verifiedNovember 16, 2026
Verdict

CloudLex and EvenUp both serve plaintiff personal injury firms, but they sit at different layers of the firm. CloudLex is the case management system itself, running intake, matters, documents, calendaring and settlement, with its built in AI, Lexee, drafting demands, summarizing medical records and capturing leads inside the case file. EvenUp is an AI platform that sits beside a firm's system, syncing cases from Litify, SmartAdvocate or CASEpeer and building chronologies, demands and case strategy with its own Piai models and LexisNexis research. Both add human help, CloudLex through paralegal services and EvenUp through PLAAS, its pre litigation service. EvenUp shows more of its own security work, with a SOC 2 Type 2 report and HIPAA attestation in its name, where CloudLex relies on the certifications of Microsoft Azure. The contracts differ as well. CloudLex caps liability at the lower of the last invoice or $2,500 and limits training to deidentified pooled data. EvenUp caps liability at twelve months of fees and may use customer input and output to improve its products.

Which one fits

Choose CloudLex if

  • You want one system for the whole case. CloudLex runs intake, matters, documents, calendaring and settlement, with AI drafting and medical summaries inside the case file.
  • Your firm needs extra hands as well as software. CloudLex paralegal services retrieve medical records, index daily mail and staff a bilingual call center inside the same system.
  • Leads arrive after hours. Voice and chat lead capture turns website visitors and calls into intake records routed into CloudLex.
  • You want limits on how your data trains AI. CloudLex's terms bar training on customer data other than deidentified aggregated data and bind its vendors to the same.
  • Your team works in Microsoft 365. CloudLex connects to Word, Outlook and Gmail and attaches correspondence to the matter.

Choose EvenUp if

  • You already run Litify, SmartAdvocate or CASEpeer. EvenUp syncs cases from them at no extra cost and pushes insights back.
  • Security review wants the vendor's own attestation. EvenUp holds a SOC 2 Type 2 report and a HIPAA attestation in its own name, available on request.
  • Demands need legal authority as well as medical facts. Companion draws on Lexis+ with Protégé, with Shepard's Signal indicators on the case law it returns.
  • You want agents that do the follow up. EvenUp agents open insurance claims, follow up on treatment and chase records within workflows the firm configures.
  • You want to hand off pre litigation entirely. PLAAS puts EvenUp specialists on claim setup, care management, record retrieval, demands, negotiation and liens.

At a glance

Category
CloudLexPlaintiff & Claims AI
EvenUpPlaintiff & Claims AI
Founded
CloudLex2015
EvenUp2019
Headquarters
CloudLexNew York, New York, United States
EvenUpSan Francisco, California, United States
Last verified
CloudLexNov 16, 2026
EvenUpNov 16, 2026

All 15 axes, side by side

The same grid applied to every vendor in the index, graded from public sources. Hover a grade to see what the letter means on that axis.

AI Centrality

How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.

CloudLex
BB on AI CentralityThe models are the engine of a core capability, layered on a product that would still function without them as a document or workflow system.

Lexee's six AI features drive work a firm would miss, on a case management system that stands without them. They cover voice and chat intake, demand package drafting, medical summaries and chronologies, questions about a matter, a client facing website assistant, and voice to task. The medical chronology and the demand draft are core plaintiff work, and the AI drives both, reading from and writing back to the case file. Underneath is a complete practice management system: intake, matters, documents, calendaring, client communication, expenses, settlement calculation, analytics, electronic signature and archiving. The agreement treats the AI Tools as one part of the Services, and Lexee is marketed as one of four pillars alongside the platform, paralegal services and publishing.

EvenUp
AA on AI CentralityThe artificial intelligence is the product. Remove the models and there is nothing left to sell.

Piai is named as EvenUp's own AI engine, and the vendor's central technical claim is that it is trained on a large dataset specific to personal injury rather than adapted from a general model. Every deliverable is model output. Medical chronologies are generated from raw records with treatment timelines and ICD extraction, demand letters are generated end to end, case valuations come from a settlement repository, and analytics sit on top of the extracted data. Without the models, what remains is a document store the firm already had. Independent review material describes it as a vertical drafting engine trained on injury cases rather than a general legal assistant.

Citation Accuracy and Hallucination Disclosure

Whether the vendor publishes measured accuracy on citations and assertions, grounds output to primary sources, and says plainly what its system does when it does not know. Legal has a documented public record of fabricated citations reaching filed briefs, so an untested claim of accuracy is not evidence.

CloudLex
CC on Citation Accuracy and Hallucination DisclosureAccuracy is asserted without measurement, or grounding is claimed while output cites sources the reader cannot open and verify.

Grounding is claimed in general terms, the contract is candid about limits, and nothing is measured. Chat answers are described as grounded in the case's documents and notes, and medical summaries are written back into the case file. Nothing says whether a summary or demand paragraph links back to the source record. The agreement states that outputs may not reflect current legal standards, may get people, entities, places or facts wrong, and may not fit the case, and it disclaims accuracy. No accuracy figure, test set, evaluation or error rate is published on the Lexee AI page, the platform page, the pricing page or either terms of service.

EvenUp
BB on Citation Accuracy and Hallucination DisclosureGrounding is real and documented, with linked primary sources and a described retrieval method, short of published accuracy figures an outsider can test.

Medical chronologies and other outputs carry line level citations back to the source record, so a reviewer can trace any fact, citation or exhibit. Demand packages cite comparable verdicts from the Settlement Repository. Legal research runs through Lexis+ with Protégé inside Companion, with answers grounded in LexisNexis case law and statutes and marked with Shepard's Signal indicators. EvenUp claims demands are 69 percent more likely to reach policy limits, and Piai is described as resolving inconsistencies and surfacing missing information before analysis. No accuracy figure, test set or error rate is published with a method, and nothing describes what happens when a record is illegible or contradictory.

Autonomy and Oversight Model

What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.

CloudLex
BB on Autonomy and Oversight ModelA written commitment that the models work alongside a supervising lawyer, with real review surfaces, short of the full control structure: commonly the threshold at which the system stops or what happens after it is wrong.

CloudLex publishes its human review as a workflow. Its four step process for medical record summaries ends with Human Review: an attorney or paralegal reviews, edits and approves the output. Demand drafts are described as designed for staff review, and medical summaries as paralegal reviewed. CloudLex's FAQ says human review stays central to every workflow. The agreement requires outputs to be independently reviewed and validated, by a qualified attorney where applicable, before use in proceedings or client communications. The client facing website assistant verifies a caller's identity before releasing case details, under the firm's control. What is missing is the failure path: no abstention, confidence signal or threshold for declining, and no route to report a wrong output.

EvenUp
BB on Autonomy and Oversight ModelA written commitment that the models work alongside a supervising lawyer, with real review surfaces, short of the full control structure: commonly the threshold at which the system stops or what happens after it is wrong.

Output is a draft for attorney review, and the subscription terms make the firm responsible for overseeing the service and reviewing output for accuracy and completeness. Demand tiers run from instant AI generation to an expert tier reviewed by an in house team before delivery. Companion delegates work to agents that open insurance claims, follow up on treatment and chase records. Communication Agents cannot pick recipients or start calls outside workflows the firm configures, and the called party is told the call is recorded and transcribed. Agents cannot add tools or act beyond the permissions granted to them. Nothing says what the in house reviewers look for, and no confidence indication is given on generated content.

Operational and Outcome Evidence

Named, dated evidence that the product works in production at real firms or legal departments. Case studies with figures and identified customers count. Unattributed testimonials and launch announcements do not.

CloudLex
BB on Operational and Outcome EvidenceReal deployment evidence with substance, short of full attribution or measurement: a named customer without figures, or figures without the named customer.

Customers are named with their firms and titles, among them a partner at Pollack, Pollack, Issac & DeCiccio, a senior litigation attorney at Mitchell and Danoff, a founding partner at Rasmussen Injury Law and a paralegal at Abrams & Associates. Two figures come with them. Michael B. Cohan of Cohan Law says the firm handles about 40 percent more cases than with its previous software, and a migration of over 300 cases is described as completed without issue. Nothing measures time saved or intake conversion with a stated method, and no quote is dated. Client Stories and Client Reviews pages are also published.

EvenUp
BB on Operational and Outcome EvidenceReal deployment evidence with substance, short of full attribution or measurement: a named customer without figures, or figures without the named customer.

Customer results are published with named firms. Lerner & Rowe Injury Attorneys reports saving three months per case with PLAAS, and Batta Fulkerson reports 75 percent faster attorney review and case assignment. Omega Law Group reports more than 3,500 hours saved and 34 percent higher demand efficiency, and ELG Injury Lawyers reports 400 percent growth. Wisehart Wright describes moving from a $50,000 offer to a $1.75 million mediated settlement using Case Companion. EvenUp reports more than 2,000 firms, more than 10,000 cases a week and a 69 percent higher likelihood of reaching policy limits. None of these figures carries a method, comparison group or measurement period.

Privilege and Confidentiality Posture

How client confidences are handled: attorney client privilege and work product treatment, segregation of one client matter from another, whether client data trains any model, and what the vendor commits to in writing rather than in marketing.

CloudLex
BB on Privilege and Confidentiality PostureSubstantive published commitments on confidentiality and training use, short of the full picture: commonly silence on segregation between users or matters, or on what the underlying model provider may retain.

Confidentiality and training carry substantive commitments from CloudLex. The customer owns its data exclusively, and CloudLex may access it only to provide the service, fix problems, comply with the law, or at the customer's request. Safeguards include preventing access by CloudLex staff outside narrow exceptions. CloudLex will not use customer data for training other than deidentified Aggregated Data, and will not let its vendors or subcontractors do so. The AI section commits to keeping client data confidential under privacy laws and bar ethics rules. Two points cut against it: the agreement says customer data may travel unencrypted, and nothing describes separation between matters within a firm.

EvenUp
BB on Privilege and Confidentiality PostureSubstantive published commitments on confidentiality and training use, short of the full picture: commonly silence on segregation between users or matters, or on what the underlying model provider may retain.

The product takes in complete medical records, billing statements and treatment histories, so the confidential material includes third party protected health information. Case data is open only to authorized staff and providers under data processing and HIPAA business associate agreements, and a SOC 2 Type 2 examination covers confidentiality and privacy. OpenAI, Anthropic and other third party providers may not train on case files. EvenUp does use its experience across cases to improve its own models, and the subscription terms let it collect and aggregate customer input and output to improve its products. An AI and legal ethics FAQ discusses privilege and work product in general terms, without a contractual commitment on either.

UPL and Professional Responsibility Posture

Whether the vendor is clear that it supplies a tool rather than legal advice, who its audience is, and how it addresses unauthorized practice of law, competence and supervision duties, and jurisdiction limits. ABA Formal Opinion 512 is the reference point. Where the advice line is not the duty a product raises, the axis is read through the nearest professional duty it does raise: judicial conduct rules and the reviewing duty for products sold only to courts, and the duty to bill for time actually spent for products that draft time entries.

CloudLex
AA on UPL and Professional Responsibility PostureThe vendor states plainly what the product is and is not, who may use it, and how it supports a lawyer’s competence and supervision duties. Jurisdiction limits are named and any consumer facing surface carries a clear disclosure.

The professional responsibility position is complete, and it reaches the consumer. CloudLex is not a law firm, cannot give legal advice, and its AI creates no attorney client relationship. Use is limited to subscribers based in the United States. Outputs must be independently reviewed and validated, by a qualified attorney where applicable, before use in proceedings or client communications. The firm is responsible for its fiduciary, record keeping and trust accounting duties, competent representation, deadlines, and getting clients' consent to the service. Users are encouraged to disclose AI use to clients, and the firm is responsible for what the chatbot says to clients and prospects. The separate chatbot terms tell claimants directly that Lexee AI cannot give legal advice. What is missing: no bar authority is named.

EvenUp
BB on UPL and Professional Responsibility PostureA real position is published on advice versus tooling, short of full treatment: commonly a disclaimer without the supervision and competence dimension, or silence on jurisdiction limits.

The subscription terms state that the service, its output and EvenUp's professional services are not legal services or a substitute for the practice of law. They are intended only for use under the oversight of legal professionals licensed in the relevant jurisdiction, and deliverables are drafts. The firm is responsible for overseeing the service and reviewing output for accuracy and completeness. An AI and legal ethics FAQ on EvenUp's Trust Center covers client disclosure, privilege and the firm's supervision duties. Communication Agents tell the called party that the call is recorded and transcribed. No jurisdiction limit is named for who may buy the service.

AI Governance and Bias Disclosure

Published governance over model behavior: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.

CloudLex
CC on AI Governance and Bias DisclosureResponsible AI principles are published without a mechanism, a testing regime, or anything a buyer could audit.

Responsible AI principles sit in CloudLex's contract, with nothing published behind them. The agreement's Transparency and Responsible Use section says the AI Tools follow principles of transparency, fairness and human oversight, and encourages users to disclose AI use to clients. Marketing says Lexee is continuously trained to stay reliable and responsible, and is designed to support human judgment. Missing from the Lexee AI page, the platform page and both terms of service: an owner of model behavior, testing before release, any published result, model documentation and bias measurement. That gap matters because the AI talks directly to injured members of the public through intake and the client assistant.

EvenUp
CC on AI Governance and Bias DisclosureResponsible AI principles are published without a mechanism, a testing regime, or anything a buyer could audit.

EvenUp publishes an AI and legal ethics FAQ covering client disclosure, privilege, billing and the firm's supervision duties, with a section on AI agents. Agents use only the tools and integrations made available in the product, act within the permissions granted to them, and are logged. The subscription terms list known AI limits, including errors, missing context and bias carried from training data. No accountable owner, testing before release, bias measurement or result is published, although case valuation draws on historical settlements that carry the patterns of who was compensated well.

AI Safety and Data Stewardship

Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.

CloudLex
CC on AI Safety and Data StewardshipA generic privacy policy covers the product without addressing what happens to documents and prompts after processing.

Deletion deadlines are real, and for the rest CloudLex leans on Azure. After cancellation a customer has 30 days to export data, and a further 30 days on request for a one time migration fee. CloudLex securely overwrites or deletes customer data 90 days after termination. Its access to customer data is limited to four named cases, and safeguards cover access by CloudLex staff. The security page and FAQ describe AES-256 at rest, TLS 1.2 or above in transit, key rotation, multi factor authentication, role based access, backups and monitoring, attributed to Azure's framework. What is missing: no subprocessor list, and no incident response or breach notice practice. The agreement also says customer data may travel unencrypted across connecting networks and disclaims liability for deleting or failing to store data, and the privacy policy disclaims the unnamed infrastructure provider's failings.

EvenUp
BB on AI Safety and Data StewardshipSubstantive published policy covering most of the ground, short of the full set: commonly no named subprocessor list or no stated incident practice.

Case data is open only to authorized EvenUp staff and service providers on a need to know basis, under data processing agreements and HIPAA business associate agreements. Data is encrypted in transit and at rest, access is logged and monitored, penetration testing runs at least annually, and the incident response plan is tested. EvenUp honors deletion requests under the customer agreement, and backups may be kept for up to a year before deletion. Third party AI providers are configured for minimal or zero retention where available. No retention period during the subscription is stated, and no subprocessor list is published.

AI Liability and Recourse

What the vendor stands behind contractually when its output is wrong. Indemnities, caps, carve outs, insurance, and whether any of it is published or only reachable through a negotiated agreement.

CloudLex
CC on AI Liability and RecourseLiability is addressed only through a standard limitation clause that disclaims the exposure the product creates.

CloudLex disclaims the exposure its AI creates and gives nothing back. Damages for all claims are capped at the lower of the last paid invoice or two thousand five hundred dollars, so a monthly customer is capped near one month's fee. No carve out is named for confidentiality, security breach, gross negligence or willful misconduct. The service is provided as is, with every warranty disclaimed, and AI output carries its own disclaimer with no liability for errors or reliance. The only indemnity runs from the customer to CloudLex, covering the firm's own negligence, including malpractice, and any client or prospect interaction through the chatbot or other AI Tools. There is no vendor indemnity, insurance position or service credit. Disputes go to AAA arbitration in New York before three arbitrators, with legal fee recovery capped at twenty thousand dollars.

EvenUp
BB on AI Liability and RecourseA real published position on liability, short of the full picture: commonly a stated indemnity without scope or caps.

Subscription terms published in September 2026 set out the position. Liability for either party is capped at the fees paid under the Order Form in the twelve months before a claim, and indirect and consequential damages are excluded, with indemnification and use restrictions carved out of the cap. EvenUp indemnifies the customer against claims that the service infringes a United States patent, copyright or trade secret. It warrants that the service substantially conforms to its documentation, with correction or termination as the remedy. AI output is disclaimed, and the customer bears all risks of using the service and its output, so a wrong chronology or valuation falls on the firm.

Practice Systems Integration Depth

How deeply the product reaches into the systems legal work already lives in: document management such as iManage and NetDocuments, Word and Outlook, contract lifecycle management, matter management, e-billing, and court filing systems.

CloudLex
BB on Practice Systems Integration DepthReal integrations exist and are documented, short of depth: named connections without a description of what they actually move.

Named connections cover the tools a small firm uses. Microsoft 365 has its own product page, and there is a Word connector and Gmail and Outlook email management that attach correspondence to the matter. A Legal App Integrator, electronic signature, iOS and Android apps and a referral engine for sending cases to other firms are offered. The agreement covers third party modules, each under its own addendum and charged separately. What is missing: no API or developer documentation is published, and no document management or electronic billing system is named.

EvenUp
BB on Practice Systems Integration DepthReal integrations exist and are documented, short of depth: named connections without a description of what they actually move.

Case files and data flow into EvenUp from case management systems including Litify, SmartAdvocate and CASEpeer, and from SharePoint, Google Drive and Dropbox. Setup takes three steps, sharing access credentials, choosing the case types, files and fields to sync, and letting cases appear, and insights push back into the case management system. Firms on Litify get a link to a finished draft from inside their case management system. Companion has a Word plug in, and Lexis+ with Protégé is built into Companion. Setup carries no extra cost, and most firms connect within hours. Field level mappings, sync frequency and a public API are not documented.

Deployment Model and Data Residency

Where the software runs and where the data sits. Multi tenant cloud, single tenant, private deployment, on premises, and whether region of residence is a published option or an enterprise conversation.

CloudLex
CC on Deployment Model and Data ResidencyCloud delivery is implied and neither the tenancy model nor the region is stated.

Delivery is in the cloud on Microsoft Azure, which CloudLex names on its pricing page, with round the clock monitoring and 256 bit encryption. The agreement limits use to subscribers based in the United States. No region or data center, selectable residency option, tenancy model, or location for AI processing is stated. Two provisions pull the wrong way. The agreement says customer data may travel unencrypted across connecting networks, and the privacy policy says servers sit with an unnamed third party provider whose security CloudLex does not guarantee.

EvenUp
BB on Deployment Model and Data ResidencyDeployment model is stated clearly with partial residency detail, or residency is offered without the processing location being addressed, or the tenancy model is stated on its own with no residency detail published.

Case data is stored in United States data centers, according to EvenUp's Trust Center. The architecture is multitenant, with logical separation, authenticated identities, role based access and scoped permissions, and a separate single tenant environment for each customer is generally not offered. Data is encrypted in transit and at rest, and access is logged and monitored. No cloud provider or region is named, and nothing says where third party AI providers process case data.

Security Certifications and Trust Center

Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.

CloudLex
CC on Security Certifications and Trust CenterBadges appear on the site with no scope, no date, and no report available.

Every certification CloudLex names belongs to Microsoft, and it says so. CloudLex's FAQ says it is built on Azure and inherits Azure's SOC 1, SOC 2 Type II and ISO 27001 certifications and its audited controls, including penetration testing, geo redundant data centers and encryption. The security page adds compliance with HIPAA, IRS and AICPA standards. An infrastructure provider's certification covers the provider's controls, not the application on top. Nothing published claims CloudLex itself has been audited: no CloudLex SOC report, ISO certificate, auditor, scope, application penetration test, trust portal or route to request a report is published. HIPAA compliance is the one claim made in CloudLex's own name, without an attestation.

EvenUp
AA on Security Certifications and Trust CenterCurrent independent attestation with named scope, reachable without a sales call: a trust center carrying reports, dates and the standards actually covered.

A Trust Center at trust.evenuplaw.com describes security, privacy and compliance practices and offers a request access route to documentation rather than a sales gate. The attestation is named with its scope: a SOC 2 Type 2 examination covering security, availability, confidentiality and privacy, four of the five Trust Services Criteria. Currency is dated, with recertification announced in April 2026. Alongside it sits an independently conducted HIPAA compliance assessment and attestation, which matters because the product processes protected health information. The vendor explains that HIPAA has no formal certification and that what exists is a third party attestation. The auditing firm is not named for either the SOC 2 or the HIPAA assessment.

Model Supply Chain Disclosure

Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.

CloudLex
DD on Model Supply Chain DisclosureNothing published about the model supply chain a customer inherits.

Nothing published says what runs the AI. No model, provider, version or inference location is named on the Lexee AI page, its six feature descriptions, the platform page, the pricing page or either terms of service. The agreement defines AI Tools by CloudLex's own branding, and marketing calls Lexee a PI trained AI without saying how. The agreement mentions third party providers in a general integration context, naming Google, Facebook, Apple, Microsoft and Amazon as examples, and its training clause binds unnamed vendors and subcontractors. No notice of model changes is promised.

EvenUp
BB on Model Supply Chain DisclosureThe supply chain is partly disclosed: providers named without change notification, or architecture described without the providers.

Piai is EvenUp's own system of specialized personal injury models, which it says is trained on more than 100,000 injury cases and a million medical records with review by more than 150 medical and legal professionals. EvenUp also uses third party AI and names OpenAI and Anthropic as providers barred from training on customer case files, configured for minimal or zero retention where available. Companion's legal research runs on LexisNexis Protégé. No model version is named, no full list of providers or where they process data is published, and no notice of model or provider changes is promised.

Commercial Transparency

Whether a buyer can learn what this costs without entering a sales process: published rates, the unit being charged, what sits behind an enterprise tier, and what implementation adds.

CloudLex
DD on Commercial TransparencyNo pricing information published at any level, including the unit of charge.

No price is published at any level, and CloudLex says so. Its pricing page states it does not publish standard per user pricing, that pricing is customized by package, users, intake and case management needs, storage, integrations, AI and optional services, and that third party price figures are estimates only. There is no figure, rate, unit or package structure to price. The agreement gives billing mechanics instead: monthly or yearly billing in advance, automatic renewal at the original price, a ten day window to opt out after a renewal notice, no refunds for partial months or downgrades, a credit card on file, extra charges above subscribed users or matters, and separate charges plus a service fee for third party modules.

EvenUp
BB on Commercial TransparencyReal pricing is published for part of the range, with enterprise tiers withheld, or the unit and structure are stated without the figure.

Pricing is per case, a model EvenUp announced in May 2025 as one cost per case for the full platform, so cost follows caseload rather than headcount. No price, range or per case figure is published. The subscription terms of September 2026 set fees in each Order Form, payable in United States dollars in advance, noncancelable and nonrefundable, with Usage Limits on the service. EvenUp's billing guidance says it can document usage consumed, effective case pricing, itemized charges and usage based overages by matter. Integration setup carries no implementation fee. A price comes through a sales conversation.

Firm and Practice Coverage

Who the product is actually built for. AmLaw, midlaw, small firm and solo, in house departments, government and courts, and which practice areas are supported rather than merely claimed.

CloudLex
BB on Firm and Practice CoverageSegment and practice coverage is described with substance, short of the boundaries: what is supported is clear, what is not is left open.

CloudLex documents its coverage and states one hard limit. Nine practice areas have their own pages: personal injury, slip and fall, product liability, mass torts, workers' compensation, social security disability, motor vehicle accidents, wrongful death and medical malpractice. It is built only for plaintiff personal injury firms. The agreement limits use to subscribers based in the United States. Paralegal services cover no fault litigation processing, court calendar management and bilingual intake. What is missing: no firm size, matter volume or state level coverage for deadlines and calendaring is stated.

EvenUp
BB on Firm and Practice CoverageSegment and practice coverage is described with substance, short of the boundaries: what is supported is clear, what is not is left open.

EvenUp says it builds for plaintiff personal injury and nothing else, and independent review confirms it is not a general legal assistant. Inputs include police reports, medical records, billing statements, photographs and intake notes, and outputs include demand letters, chronologies, case valuations, negotiation preparation and caseload analytics, with a settlement repository supporting comparables by jurisdiction. Nothing says how many verdicts or settlements the repository holds, which jurisdictions it covers, its date range, how often it updates, or whether it is deep enough in a given venue for a comparable to carry weight in negotiation.

The 12 legal signals, side by side

Recorded rather than graded. These are the questions a practitioner has to answer before a tool touches a client matter, and the answers are taken from public material only.

Client Data in Training

Can material a lawyer puts into this product be used to train a model?

CloudLex
Never, in the contract

The firm terms (12 Dec 2025) say CloudLex will not use customer data other than Aggregated Data for training, and will not let its vendors or subcontractors do so, without a separate written agreement. Aggregated Data excludes anything that identifies the customer, its clients or any person or organization, and CloudLex takes a perpetual license over it, including to train AI models. A different contract points the other way.

The Lexee AI Chatbot Terms bind a firm's prospective client, not the firm: a person using the chat widget on a firm's website grants CloudLex a perpetual license over their own submissions, not limited to aggregated form, including to train AI models. So case data in the platform is protected by contract, and intake conversations from the firm's website are not.

EvenUp
Permitted, in the contract

The subscription terms of September 2026 let EvenUp collect, analyze and aggregate customer input and output and use it to improve its products, and EvenUp owns the deidentified data drawn from them. EvenUp says it uses its experience across thousands of cases to help its models recognize patterns in medical records and outcomes, and that the models are designed not to store or reproduce documents. Third party AI providers, including OpenAI and Anthropic, may not train on case files.

Prompt and Output Retention

How long does the product keep what a lawyer typed, and can that be set to zero?

CloudLex
Disclosed without a period

The end of the lifecycle has dates and the middle does not. After cancellation a customer has 30 days to export data, then a further 30 days on request for a one time migration fee. CloudLex need not keep data past 60 days, and securely overwrites or deletes it 90 days after termination. Nothing covers retention during the term or anything specific to AI: no period for prompts, outputs or chat history, and no zero retention setting. CloudLex can also set storage limits and disclaims liability for deleting or failing to store data.

EvenUp
Disclosed without a period

Case data, outputs, processing artifacts and logs are kept as needed to run the service. Deletion requests are honored under the customer agreement and applicable law, with limited retention for legal, security, audit, backup or dispute purposes, and backups may be kept for up to one year. No period is stated for case files, prompts or outputs during the subscription. Third party AI providers are configured for minimal or zero retention where available.

Ethical Walls and Matter Segregation

Does retrieval respect the firm’s ethical walls, or can the model read across them?

CloudLex
Not addressed

Nothing published describes separation between matters. No ethical wall, matter level permissions or scoping of AI features to one matter is described. Each user has a unique sub account, and the agreement makes the firm responsible for giving matter data only to people entitled to it. Marketing claims role based access with permissions set by the firm, which a firm could use to build a wall, but the vendor does not describe one. That matters for a plaintiff firm with adverse matters or a lateral hire to screen.

EvenUp
Claimed, not documented

Customers are separated logically in a multitenant architecture, with authenticated identities, role based access and scoped permissions, and case files do not appear in another customer's work product. Nothing describes permissions by matter inside a firm or how a firm walls off a conflicted matter. The Settlement Repository pools past outcomes for valuation across customers, and its boundary with a firm's own case data is not described.

Third Party Request and Subpoena Notice

If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?

CloudLex
Not addressed

CloudLex's terms let it access customer data to comply with the law, and let staff disclose it as compelled by law, as exceptions to its access limits. No commitment to tell the customer about a demand, give it a chance to object, resist or narrow the demand, or publish a transparency report appears in the firm terms, the chatbot terms or the Lexee AI and platform pages. The platform holds medical records and settlement information on injured plaintiffs.

EvenUp
Notice committed

The subscription terms allow disclosure under a valid court or agency order only if the disclosing party gives reasonable notice so the other side can contest it. On its Trust Center, EvenUp adds that, unless legally prohibited, it notifies the affected customer promptly and discloses only what is required. No transparency report is published.

Primary Law Corpus Provenance

Where does the law in this product come from, and does the vendor have the right to use it?

CloudLex
Not addressed

The AI reads the firm's own matter file, medical records and case data, so there is no vendor assembled body of law or content license to name. The customer owns its data, and CloudLex licenses only deidentified Aggregated Data. That pooled data is a corpus in practice: CloudLex takes a perpetual license to compile customer data across its users into Aggregated Data, including to train AI models and give analysis to users, and owns the resulting reports. Nothing says what that pool contains or how it is governed.

EvenUp
Sources named, basis unstated

The Settlement Repository is described as a database of past settlements used for benchmarking and case valuation, and comparable verdicts from it are cited inside demand packages, so that data is the substance of the argument sent to an insurer. No count of verdicts or settlements, jurisdictional coverage, date range or update frequency is given, and nothing states how the outcomes were obtained, whether from public court records, customer results or licensed data.

Piai is separately claimed as trained on a large personal injury dataset whose provenance is also unstated. Two central data sources are named, and neither is sourced.

Good Law Verification

Does the product tell you when the authority it just cited has been overruled?

CloudLex
Not addressed

Lexee AI reads a matter's own records and case data rather than legal authority, so no citator applies and none is claimed on the Lexee AI page, its feature descriptions, the platform page or either terms of service. The agreement does warn that outputs may not reflect current legal standards, and makes the user responsible for checking them.

EvenUp
Licensed citator, surfaced inline

Legal authority in Companion comes from Lexis+ with Protégé, with answers backed by citations, Shepard's Signal indicators and links to the underlying LexisNexis authority. Comparable verdicts from the Settlement Repository are outcomes rather than authority and carry no treatment signal. Nothing says whether authority cited in a generated demand letter is rechecked against Shepard's before delivery.

Refusal and Uncertainty Behavior

What does the product do when the answer is not in the corpus?

CloudLex
Not addressed

No abstention path, confidence indicator, threshold for declining, or behavior when the case file cannot support a question is described on the Lexee AI page, its feature descriptions, the platform page or either terms of service. The chatbot terms tell users that Lexee AI may not handle all inquiries or answer accurately in all cases. CloudLex relies on people instead: its published workflow ends with an attorney or paralegal approving output, and the agreement requires attorney validation before output is used in proceedings or client communications.

EvenUp
Not addressed

Nothing published describes an explicit no answer path, abstention behavior or confidence signal. Medical records arrive illegible, contradictory, incomplete or out of order as a matter of routine. Nothing states whether the system flags a gap in the treatment timeline, marks a low confidence extraction, or produces a clean looking chronology from an incomplete file. Independent material notes that missed items and misinterpretations occur in complex cases with extensive treatment histories, and the vendor does not describe how such misses are surfaced.

Fabricated Citation Record

Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?

CloudLex
None located

The AI Hallucination Cases database maintained by Damien Charlotin and several independent 2026 sanctions trackers record no court order, opinion or disciplinary record naming CloudLex or Lexee. Lexee drafts demands and summarizes medical records rather than citing law, so the nearer risks are a wrong treatment summary or a demand that overstates the records, which the vendor addresses through human review rather than measurement.

EvenUp
None located

The AI Hallucination Cases database kept by Damien Charlotin holds no entry naming EvenUp. The product generates documents citing both legal authority and comparable verdicts, sent to adverse parties.

Bar Guidance Alignment

Has the vendor engaged in public with the ethics opinions its buyers are bound by?

CloudLex
Generic reference

The agreement refers to bar ethics rules as a category and names no authority. The AI section commits CloudLex to keeping client data confidential under privacy laws and bar ethics rules. The firm is made responsible for its duties to clients, including record keeping, trust accounting, professional standards, competent representation and deadlines, and must get clients' consent to the service. Users are encouraged to disclose AI use to clients.

Nothing in either terms of service, the Lexee AI page or the platform page names ABA Formal Opinion 512, a state bar opinion or a specific rule.

EvenUp
Named guidance addressed

EvenUp's AI and legal ethics FAQ names ABA Formal Opinion 512 on generative AI, Model Rule 1.5 on fees and Formal Opinion 93-379 on billing expenses, and covers client disclosure, privilege and supervision. It points firms to state ethics guidance, local court rules and standing orders without mapping them by jurisdiction.

Billing and Fee Posture

Does the vendor address what happens to the bill when the work takes an hour instead of six?

CloudLex
Savings claims only

CloudLex pitches speed: faster drafting, record review and access to information, without separate AI tools. No per matter record of AI assisted work for fee purposes, and no guidance on billing or case cost treatment, is published. This matters for contingency firms, which recover case costs from the settlement, because an AI drafted demand or chronology replaces work that would otherwise be a cost. The agreement encourages disclosing AI use to clients, which is about use rather than fees.

EvenUp
Audit record and guidance

EvenUp publishes guidance on billing its costs back to clients, citing ABA Model Rule 1.5 and Formal Opinions 512 and 93-379, and on telling case costs apart from firm overhead. Depending on the service, it can document usage consumed, effective case pricing, the matters served, itemized charges and usage based overages by matter. A contingency firm can use that record to support a case expense, though the guidance leaves the decision to the firm and its fee agreement.

Outside Counsel Guideline Readiness

Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?

CloudLex
Not addressed

The agreements answer some client questions, and no supporting documents exist. A firm can point to the training limit to deidentified Aggregated Data, the four case limit on vendor access, confidentiality under privacy laws and bar ethics rules, HIPAA compliance and the 90 day deletion timetable. Not published: a subprocessor or model provider list, data processing addendum, security questionnaire, trust portal, audit report or AI disclosure pack.

The footer lists four documents: a privacy policy, the firm terms, the chatbot terms and a cookie policy. The privacy policy declines to name the infrastructure provider that holds the data.

EvenUp
On request only

SOC 2 Type 2, HIPAA and CCPA documentation is offered on request through the Trust Center at trust.evenuplaw.com, monitored by Secureframe. EvenUp names OpenAI and Anthropic among its third party AI providers and refers to data processing and HIPAA business associate agreements with its providers. No full subprocessor list, downloadable summary or business associate agreement template is published outside the request route.

Court Disclosure Support

If a judge’s standing order requires an AI disclosure, can the product produce one?

CloudLex
Guidance or template only

The agreement addresses the duty and no record exists to meet it. CloudLex encourages users to disclose AI use to clients and requires attorney review of outputs before use in legal proceedings, so it expects AI assisted work to reach a court. No model identification, log of AI use, or record of who reviewed and approved an output is described, even though human review is a published workflow step. No export, certification template or standing order guidance exists.

EvenUp
Partial record

Medical chronologies carry citations back to source documents, so any entry can be checked against the underlying record, and demand packages cite comparable verdicts from the settlement repository. A firm can show what a factual assertion or a valuation argument rests on. Nothing indicates that output records which model generated it, and no human verification record is captured. That includes the expert reviewed tier, where an in house team checks the document before delivery but no record of that check appears to reach the customer.

A demand package is a document prepared before litigation, so the forum is a claim file or a later suit rather than a court with a standing order, and the same question applies in either.

What neither one publishes

The questions both sides leave open

Derived from the records above rather than written, so it cannot favor either vendor. Take these into both conversations and ask each side the same question.

Signals neither addresses in public material
  • Refusal and Uncertainty Behavior

In summary

CloudLex

CloudLex is case management software built only for plaintiff personal injury firms in the United States, covering intake, matters, documents, calendaring, client communication and settlement calculation. Its built in AI captures leads by voice and chat, drafts demand packages, turns medical records into treatment chronologies and answers questions about a matter, and an attorney or paralegal approves output before use. Paralegal services, including medical record retrieval, chronologies, mail indexing and a bilingual call center, run inside the same system. According to the AI Legal Index, CloudLex runs on Microsoft Azure and relies on Azure's certifications rather than an audit of its own, and its terms bar training on customer data other than deidentified aggregated data. It publishes no price.

Source: AI Legal Index, 2026

EvenUp

EvenUp is an AI platform for plaintiff personal injury firms, founded in 2019 in San Francisco, which reports more than 2,000 firms as customers. Its Piai models turn raw medical records into chronologies with line level citations, and its tools cover intake, treatment, demands, negotiation, discovery and trial. Companion, its AI agent, works across cases and in Word, draws on Lexis+ with Protégé, and delegates tasks such as opening insurance claims to agents. Cases sync from Litify, SmartAdvocate and CASEpeer. According to the AI Legal Index, EvenUp holds a SOC 2 Type 2 report and HIPAA attestation and stores case data in United States data centers. It names OpenAI and Anthropic among AI providers barred from training on case files. Pricing is per case and not published.

Source: AI Legal Index, 2026

Questions buyers ask

How does CloudLex compare to EvenUp?

CloudLex is a personal injury case management system with AI built in, so the AI works on the matter where it lives. EvenUp is an AI platform that syncs cases from systems such as Litify, SmartAdvocate and CASEpeer, with its own Piai models, LexisNexis research and agents that act on a case. From the AI Legal Index, based on each vendor's own published materials as of November 16, 2026. No vendor pays for placement.

Is CloudLex's AI a separate product from CloudLex?

No. Lexee is the AI built into CloudLex and comes with the platform rather than as a standalone tool. It covers lead capture, demand drafting, medical summaries, questions about a case, a client web assistant and voice to task, while EvenUp sells its AI as the main product. From the AI Legal Index, based on each vendor's own published materials as of November 16, 2026. No vendor pays for placement.

What do CloudLex and EvenUp cost?

Neither publishes a price. CloudLex quotes each firm by package, users, storage, integrations, AI features and services, billed monthly or yearly in advance. EvenUp charges per case, with fees set in an Order Form and paid in advance, and connecting a case management system costs nothing extra. From the AI Legal Index, based on each vendor's own published materials as of November 16, 2026. No vendor pays for placement.

Do CloudLex and EvenUp train AI on client data?

CloudLex's terms bar training on customer data other than deidentified aggregated data, and its vendors are bound the same way. EvenUp's terms let it use customer input and output to improve its products, and it bars third party providers, including OpenAI and Anthropic, from training on case files. From the AI Legal Index, based on each vendor's own published materials as of November 16, 2026. No vendor pays for placement.

What happens if CloudLex or EvenUp output is wrong?

Both require attorney review and disclaim AI output. CloudLex caps its liability at the lower of the last invoice paid or $2,500, and only the customer gives an indemnity. EvenUp caps liability at the fees of the prior twelve months and indemnifies only against intellectual property claims. From the AI Legal Index, based on each vendor's own published materials as of November 16, 2026. No vendor pays for placement.

Disclosure

Neither vendor paid for inclusion, placement or a grade, and neither reviewed this page before it published. Everything on it comes from public material on the dates shown. How the index grades.

Neither vendor publishes a price or an accuracy figure for its AI. CloudLex names no model provider and holds no security audit in its own name. EvenUp names OpenAI and Anthropic but not where they process data, and neither vendor publishes a subprocessor list.

Contact

Correct a record, or ask how something was graded

Every grade and every signal on this index is drawn from public sources and dated. If a record is wrong, out of date, or missing an artifact the index did not locate, send the source and it will be reviewed and the record redated. Vendors are welcome to submit documentation. Nothing on this index is for sale, including a listing, a placement, or a grade.

AI Legal Index

The AI Legal Index is an independent index that tracks changes to AI vendors in legal. It holds 535 vendors across 9 categories, each graded on the same 15 capability axes and recorded against 12 legal signals, from public sources. No vendor pays for inclusion, placement, or rating.

Index Status
Last index update
November 19, 2026
The AI Legal Index is an editorial reference. It is not a regulatory body, not a law firm, and nothing published here is legal advice or a recommendation to retain or avoid a vendor. Records are verified against published sources, bar guidance and public court records. Where a record reads not addressed, the material was not located in public sources on the date shown. See the Methodology page for evaluation standards and limitations.
© 2026 AI Legal Index
3801 N Capital of Texas Hwy, Ste E240 · Austin, TX 78746