L
Lexbe
Lexbe is a cloud eDiscovery platform for law firms, corporate legal departments and managed review providers, sold by Lexbe Inc. of Austin, Texas, which was founded in 2006. The Lexbe eDiscovery Platform takes a matter from upload and processing through review, redaction and production, with privilege logs, Bates stamping, near duplicate grouping, email threading, Bayesian predictive coding and translation across 75 languages.
Three generative AI tools sit on top. CoPilot summarizes, pulls out entities and dates, finds personal and health information and translates inside the document viewer, linking each answer to its source. Pilot answers questions across a whole case and writes a Strategic Case Insights Report with a timeline, entity index and issues matrix. AutoPilot codes documents for responsiveness and privilege one at a time, returning a rationale and a confidence rating, and runs as a paid service set up by Lexbe staff.
The models come from OpenAI and Anthropic. Pricing is by gigabyte hosted, with unlimited users and CoPilot and Pilot included. Lexbe also sells digital forensics and managed eDiscovery services.
Lexbe, head to head
Side by side on the same 15 capability axes and 12 legal signals: where the two part company, and what neither one publishes.
Alternatives to Lexbe
Vendors in the same categories as Lexbe whose graded profiles look most alike, with a line on what each product does.
Similar is not the same, so check that each one does the job you need. No vendor pays for placement.
- OOpenText eDiscoveryOpenText eDiscovery is an electronic discovery platform covering collection, processing, analysis, review and production, sold to corporate legal departments, law firms and investigating…
- AAI.LawAI.Law is a litigation platform for solo and mid size firms that combines drafting tools with a full practice management system, with roughly sixty named tools.
- CCaseMarkCaseMark turns a litigation record into the work product a matter needs, with each statement cited back to the page it came from.
- DDISCODISCO is a cloud ediscovery and litigation platform covering hold, ediscovery, review, timelines, deposition management and case building, sold to law firms, corporate legal teams and government.
- EEpiq AIEpiq AI is the AI product line of Epiq Systems, Inc., a New York legal services and technology company whose other businesses include class action and bankruptcy administration, managed…
- BBriefCatchBriefCatch is legal writing and citation checking software for lawyers, judges and courts, used in Microsoft Word, Outlook or a browser.
Ordered by how closely the graded profiles match across the 15 capability axes, inside the same categories. See how each axis is graded in the methodology.
Capability grades
All 15 axes, graded from public sources on the date shown. 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.
Under the AI sits a full eDiscovery stack. It processes more than one million documents an hour on over 10,000 processors, then indexes, deduplicates, runs OCR, groups near duplicates, threads email, redacts, Bates stamps and produces with privilege logs. Generative AI runs through three tools layered on that base. CoPilot works inside the document viewer on one document or a selected group, Pilot answers questions across a whole case, and AutoPilot codes documents for responsiveness and privilege at volume.
Older machine learning sits beside them in Bayesian predictive coding, sentiment tagging, speech transcription and image recognition. Take the language models away and the processing, review and production platform still runs, which is how customers used it for well over a decade before CoPilot arrived.
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.
Every CoPilot result links back to the document it came from, and Pilot ends each answer with links to the case documents it drew on, which open in the document viewer. Pilot uses retrieval augmented generation over the case repository, and its Strategic Insights setting widens how much of the case it brings into an answer. AutoPilot returns a written rationale with each coding call. Lexbe describes Pilot as unable to hallucinate because grounding language limits each answer to the text sent to the model, and says AutoPilot's precision and recall beat traditional technology assisted review in internal testing. No precision, recall or error figure has been released, so neither claim can be tested from outside.
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.
Each of the three tools is framed around a supervising attorney. CoPilot follows a human in the loop model in which reviewers keep control of coding decisions and quality checks. AutoPilot is a first pass layer that returns a confidence rating from 1 to 10 and a rationale for every document. Its recommended workflow validates output against a human coded control set drawn before the run, tests a sample of the documents it did not flag, and leaves final responsiveness and privilege calls to attorneys.
AutoPilot is not self serve, since Lexbe's professional services team engineers the prompts and helps with quality control. Pilot is limited to fact questions and gives incomplete answers to requests for lists across a whole case. The master services agreement calls AI output probabilistic and tells customers to apply human review to it. The confidence level at which a document goes to a person is chosen per matter rather than fixed by the product.
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.
Lexbe says more than 8,795 legal professionals have relied on the platform and quotes named attorneys at named firms. A litigation partner at Logan & Lowry says it helped a three lawyer team win a verdict of nearly $9 million against Greenberg Traurig. Partners at Richman Greer, Curry & Friend, Vladeck, Raskin & Clark, The Brodsky Law Firm and Heslin, Rothenberg, Farley & Mesiti praise its pricing, speed and support.
The legal director of Disability Rights Ohio describes using it with co counsel on large document cases. An insurance defense case study covers a construction liability matter shared by five defense firms, with a Thomson Coe attorney quoted on the savings. The 70 percent cut in first level review time comes from a modeled 100,000 document example and internal testing rather than a named customer. None of the quotes is dated or carries a measured before and after figure.
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.
Section 3 of the master services agreement treats customer data as confidential and acknowledges it may be privileged or attorney work product, which Lexbe holds as agent of the attorneys on the proceeding. Lexbe discloses it only to the customer or on the customer's instruction, subject to law or a valid order, and promptly notifies the customer of a subpoena or investigative demand. Matter separation comes from seven fixed user types, case by case access and a Limited User who sees only tagged documents.
Joint defense groups can share one repository while each defendant keeps its own work environment. Pilot runs on Anthropic's Claude with zero data retention, and Lexbe states that no user data from it trains any model. That promise sits in the help center rather than the agreement, and section 9 has customers accept the OpenAI, Anthropic and AWS terms on retention and training when they use the AI services. No retention period for prompts or case data is stated.
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.
The agreement describes the platform as a supplemental tool for experienced lawyers and litigation professionals, not for people who cannot manage the litigation process unaided. Customers must be licensed attorneys or law firms, or have retained an attorney who advises them on proper use, and they rely on their own skill rather than on Lexbe for legal advice. Section 9 places every decision, piece of advice and action based on AI output with the customer, and tells it to apply human review to output that may be probabilistic.
Marketing pitches Pilot as a digital lead investigator for pressure testing case themes, yet every tool is sold to litigation teams rather than to the public. No ethics opinion or jurisdiction limit is named.
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.
Lexbe refers to a Responsible AI framework that keeps the attorney in control, with output tied to source documents and a person making the final call. It also describes how AutoPilot was built. Its professional services team and an AI research and development team developed and tested a prompt engineering method that, by Lexbe's account, exceeds the precision and recall benchmark for older technology assisted review.
Customers get guidance on validating output with control sets and tests on unflagged documents. The framework itself has not been released as a document, and no one inside Lexbe is named as accountable for AI. The results behind the benchmark claim are not shared, and nothing addresses uneven output across languages, custodians or document types.
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.
Case data sits on encrypted servers in the United States on Amazon Web Services, with AES-256 encryption at rest and in transit. Access runs through seven fixed user types, optional two factor authentication and single sign on, added in February 2026. Administrators can export a log of who viewed or downloaded each document, kept for two months. Account administrators delete cases themselves, and recovery from backup may be possible for a fee, depending on the backup delete cycle.
At termination Lexbe may delete customer data, and a paid case archive is available if requested beforehand. The AI integrations run with zero data retention at the model providers. The privacy policy, last uploaded in September 2021, is a general one, and no retention period during the subscription, breach notice practice or subprocessor list beyond the named AI providers is offered.
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.
Lexbe indemnifies customers against claims that the platform infringes a copyright, a United States patent or a trademark. It also indemnifies against claims arising from a breach of its section 17 warranties, which cover its authority to contract and commercially reasonable efforts to keep the platform available. A 99.9 percent monthly availability commitment carries pro rata credits as the sole remedy. Everything else is disclaimed.
The service is provided as is, and AI output is used at the customer's sole risk. Lexbe takes no liability for failures in the third party libraries and services it relies on, indirect and consequential damages are excluded, and claims must be brought within two years. No liability cap figure or insurance is stated, and nothing covers a wrong coding call or summary.
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.
The Clio integration pulls matter folders from Clio into a case. A user signs in to Clio once through the Third Party Applications page and picks a matter or folders within it. Up to 3,000 documents upload at a time, and Clio folder paths are kept in the Source FilePath metadata field. Single files cannot be picked, and the link is removed from the same page. CoPilot can also be tied to a customer's own OpenAI account by pasting an API key and choosing a model.
Productions received from other parties load with their load files through a .dat metadata mapping step, and outgoing productions carry load files for other review platforms. No connector to iManage, NetDocuments, Microsoft 365, Outlook or a matter management system is offered, so Clio is the only practice system in the list.
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.
The platform is cloud only and runs on Amazon Web Services, reached through a browser on Windows, Mac or a mobile device with nothing to install. All customer electronically stored information is kept on servers in the United States, and customers in the European Union and Switzerland are covered by Standard Contractual Clauses provided on request. Where the OpenAI, Anthropic and Amazon models process documents is not stated, and no tenancy model, region choice or private deployment is offered.
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.
No independent security attestation is claimed for Lexbe. Its security is described as AES-256 encryption at rest and in transit, data access controls and active management of the AWS environment, with optional two factor authentication and single sign on. No SOC 2 report, ISO 27001 certificate, trust center or penetration test summary is offered.
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.
The agreement names OpenAI, Anthropic and Amazon Web Services as the providers behind Lexbe's AI services, with Amazon Transcribe, Amazon Translate and Amazon Rekognition behind audio transcription, translation and image recognition. Release notes name the language models. GPT-4.1 and GPT-4.1 Mini were added to CoPilot in September 2025, Claude 4 Sonnet and Claude 4 Opus to Pilot and AutoPilot in June 2025, and five more OpenAI models to AutoPilot in April 2025.
Pilot runs on Claude with zero data retention. Customers learn of model changes through release notes after the fact, with no advance notice commitment, and where each model runs is not stated.
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.
Lexbe prices by data volume, the gigabytes uploaded and hosted, billed monthly in arrears on the highest usage in the month. Plans include pay as you go accounts with no commitment, flat monthly rate plans, subscriptions of a year or more for a set capacity and hibernation for inactive cases, with volume and subscription discounts. There are no user or case fees, ESI processing is free on subscription accounts, users are unlimited, and CoPilot and Pilot come with every hosting plan.
The billing policy spells out what counts toward storage, including the text index, capped at 35 percent of document size for billing. AutoPilot, professional services and forensics are billed separately at per gigabyte, per page, per document or hourly rates. No rate is published, and every plan routes to an estimate request.
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.
Lexbe is built for boutique and mid sized law firms with document heavy cases, and also sells to corporate legal departments, managed review providers, disability rights organizations and Mac users. Practice pages cover construction, environmental, insurance defense, intellectual property, labor and employment, securities and telecommunications litigation, and the platform handles third party subpoenas, internal investigations and compliance reviews.
Forensic collection covers phones, computers, email, cloud and collaboration accounts such as Slack and Microsoft Teams, social media, websites and drones. A few limits are stated. Use is meant for experienced litigation professionals working with a licensed attorney. Native upload batches should stay near 20 GB with mail files under 50 GB, and Pilot is not built for whole case list requests. No practice area, jurisdiction or firm size is excluded.
7 public documents
The public pages on file for Lexbe, with the recorded signals each one supports and the date it was last read. Open any of them and check the reading against the record.
-
Client Data in Training, Prompt and Output Retention
Read Oct 13, 2026
-
Third Party Request and Subpoena Notice, Outside Counsel Guideline Readiness
Read Oct 13, 2026
-
Court Disclosure Support
Read Oct 13, 2026
-
Ethical Walls and Matter Segregation
Read Oct 13, 2026
-
Refusal and Uncertainty Behavior
Read Oct 13, 2026
-
Billing and Fee Posture
Read Oct 13, 2026
-
Fabricated Citation Record
Read Oct 13, 2026
Legal Signals
What each signal meansA signal records what public sources say on the date shown. It is not a grade and it is not a recommendation. Where a signal reads Not addressed, it means the index did not locate the material in public sources on that date, which is a statement about disclosure rather than about the product.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
A public policy or trust page states no training on customer content, with no matching term located in the published agreement.
Lexbe states that Pilot runs on Anthropic's Claude with zero data retention, so no user data is kept by the model provider or used to train existing or future models. It says its AI integrations generally run the same way. The master services agreement has no training term. Its license limits Lexbe's use of customer data to providing the services, including improving functions within the customer's own account. Section 9 has customers accept the OpenAI, Anthropic and AWS terms on retention and training when they use the AI services. A customer can also link CoPilot to its own OpenAI account with an API key.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
Retention is acknowledged in public materials with no stated period.
Prompts sent to the model providers are not kept there, since Pilot and the other AI integrations run with zero data retention. Inside the platform, Pilot keeps past conversations, and users can share, pin or permanently delete saved prompts. No period is stated for how long prompts, outputs or case data stay on Lexbe's servers during a subscription, and at termination Lexbe may delete customer data, with a paid archive available if requested beforehand. Document access logs are kept for two months unless exported.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
The product maintains its own permission model, documented, requiring the firm to keep it aligned.
Access runs through seven fixed user types, from Account Admin to Read Only and Limited User, with case by case access granted by an account administrator. A Limited User sees only documents tagged to a shared field and has none of the case tools. For joint defense groups, one repository serves several firms while each defendant keeps a dedicated work environment for its own work product. Nothing says whether Pilot answers respect those permissions.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
Terms commit to notice where lawfully permitted. No transparency report located.
Section 3 of the master services agreement commits Lexbe to notify the customer or an account administrator promptly when a third party seeks customer data by subpoena or investigative demand. Lexbe hands the defense of the request to the customer and cooperates on the response. If legal process forces Lexbe staff to do work on a customer's matter, section 18 bills the customer for it. Otherwise data is disclosed only on the customer's instruction or under law or a valid order. 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?
No located public material identifies the corpus behind the product’s answers.
Lexbe's AI works on the evidence a customer uploads to a case, not on a body of law, so no legal content source or license is involved. CoPilot and Pilot draw only on the documents in the matter, and AutoPilot codes them one at a time.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
No located public material addresses whether authority is checked for subsequent history.
The platform reviews a party's own documents and does not retrieve case law, so no citator or subsequent history check applies. Its source links point to case documents, not to legal authority.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
The product exposes a confidence or grounding score without an explicit abstention path.
CoPilot and AutoPilot return a confidence rating from 1 to 10 with each responsiveness or privilege call, along with a rationale, to speed quality control. Pilot limits answers to the text sent to the model and gives incomplete answers to whole case list requests. No path is described for the product declining to answer when the documents do not support one.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
No court order, opinion or disciplinary record addressing fabricated or hallucinated legal citations produced by this product has been located as of the date shown. This is a statement about the public record on that one subject, not a finding about the product, and this signal is not a litigation history.
The AI Hallucination Cases database maintained by Damien Charlotin, which records court decisions worldwide that address hallucinated AI content and the tool involved where known, has no entry naming Lexbe. Lexbe's AI summarizes, codes and answers questions about a party's own discovery documents rather than drafting filings.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
No located public material engages with bar or ethics guidance.
Lexbe engages with no ethics opinion or bar guidance. Its agreement limits use to licensed attorneys or customers who have retained one, and its marketing stresses attorney control of AI output, without naming ABA Formal Opinion 512 or any state bar opinion.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Public materials claim time savings without addressing billing or disclosure, and the product sits inside a fee relationship between a lawyer and a client where those savings would change the bill.
Lexbe claims AutoPilot can cut first level review time by up to 70 percent. Its modeled 100,000 document review falls from about 2,000 reviewer hours at a $60 blended hourly rate to roughly 600, at an estimated $48,500 in review and platform cost against $120,000. Nothing addresses how AI assisted review should appear on a client's bill. Lexbe also says its pricing eases billing administration with clients, and it customizes invoices for each insurance carrier in a matter with claim numbers and cost breakdowns.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
A current subprocessor or model provider list is published.
The master services agreement names OpenAI, Anthropic and Amazon Web Services as the providers behind Lexbe's AI services, along with the Amazon services used for transcription, translation and image recognition. Release notes name the language models in use. No full subprocessor list or client facing disclosure pack is offered, and Standard Contractual Clauses are available on request.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
Some elements of the record are available, short of a document level export.
Parts of a disclosure record exist. AutoPilot gives a rationale and confidence rating for every document, and CoPilot and Pilot link answers to their source documents. Administrators can export a log of who viewed or downloaded each document. Before a production runs, a validation step flags partial email families, missing redactions and privilege coding across email families, and a privilege log can be exported afterward. No document level export ties a model, its sources and human verification together.