August 28, 2026
Discernis Discovery asks a litigator to paste guiding questions from a review protocol into a box, then reads every document in the collection and ranks what answers them. The measures that bear on whether that result holds up are not the ones on the home page. They sit in the FAQ.
Discernis, a New York company, announced a $2.5 million seed round on Aug. 25. The company named Newfund Capital as lead investor, with participation from Triple Impact Capital, Remarkable Ventures and C2 Ventures, and said the software is in use at Am Law firms on active matters. The SaaS News and Law.com’s Legaltech News carried the round. The money matters less to practitioners than the design premise behind it, and that premise is stated plainly enough to test.
The company sells two products, and Discernis Discovery is the one aimed at first-pass review. A reviewer enters or pastes the guiding questions already written into the review protocol, and the software assesses every document for responsiveness and prioritizes what it finds. Output travels back out as load files, .dat files or a CSV listing responsive documents with their scores and the model’s explanations.
Read the full article at ComplexDiscovery
ComplexDiscovery Editor’s Note: A federal magistrate in Colorado spent part of March writing contract terms into a protective order, and a seed-stage discovery vendor has since made that order the centerpiece of its marketing. The appeal is easy to see. Morgan v. V2X, Inc. bars confidential material from any AI platform unless the provider is contractually barred from training on inputs and from passing them onward except as essential to delivering the service, and Discernis Discovery describes an architecture that speaks to those concerns.
What this piece adds is the distance between them. Morgan asks for contractual prohibitions, a contractual deletion right, and retained written documentation. Discernis publishes architecture, deployment descriptions, and a 30-day removal window. Those are different kinds of claim, and the public pages do not show the customer contract. The company also publishes three statements of throughput and three ways of stating performance, a reminder that vendor numbers need a denominator.
Practitioners in cybersecurity, data privacy, regulatory compliance and eDiscovery share one interest here, because a court order that specifies what a vendor’s contract must prohibit turns procurement language into a discovery obligation. Watch whether other courts adopt Braswell’s provision, and whether vendors start publishing contract terms rather than architecture.