Uncover Legal is a real litigation-workflow product, but it is no longer a straightforward standalone startup story. The public site remains live, with modular pricing, feature pages, and free-trial CTAs, yet the company was acquired by Opus 2 on October 9, 2025 and is now also presented as ‘Uncover by Opus 2.’ The strongest March 2026 evidence points to a document-intensive litigation assistant rather than generic case management: automatic document structuring, chronological summaries and timelines, a ‘Junior Lawyer’ AI assistant for large document sets, source-linked citations, client access, and integrations with iManage, Epona, and SharePoint. Public security posture is unusually strong for a young legal AI product: ISO 27001 certification, GDPR certification, AWS infrastructure, SSO, user management, AES-256 at rest, and TLS in transit. The company also has public modular pricing, with Uncover Base from €50/month billed yearly and add-on pricing published for chronological summaries, lawyer assistants, client access, and document-capacity upgrades. Independent validation exists but is still limited: Legaltech Hub documented both the July 2024 Dutchyard funding and the October 2025 Opus 2 acquisition, Penrose published a Dutchyard investment note, and the site includes named testimonials from Jeroen Plink, Mike Lennard, and Marc Hanraets. What remains weak is broad practitioner proof: no meaningful Reddit, G2, or Capterra footprint surfaced, and most of the detailed product claims still come from Uncover’s own marketing pages.
Company Info
- Founded: 2022
- Team size: 1-10 employees
- HQ: Netherlands
- Sector: Litigation, Miscellaneous
What We Haven’t Verified
This page was assembled from publicly available information. Feature claims and workflow mappings are based on what the vendor and third-party listings publish — not hands-on testing or practitioner feedback.
Workflows
Based on practitioner evidence, Uncover Legal is used in these workflows:
What practitioners struggle with
Real frustrations from legal professionals — the problems Uncover Legal addresses (or should address). Sourced from practitioner reviews, Reddit threads, and case studies.
Documents scattered across email, shared drives, attorney desktops, and filing cabinets — paralegal can't find the key document when it's needed for court or a deposition
eDiscovery tools require a dedicated specialist to operate — Relativity needs an admin, but most small/mid litigation teams don't have one and need something a paralegal can use after a 30-minute demo
When my litigation team receives 100,000 documents in discovery and the partner wants an early case assessment by Friday, I need to understand the key facts, players, and timeline before we've even started formal review — but right now the only option is throwing associate hours at it and hoping we surface the right documents
Litigation paralegal gets a 500-page case file and needs to build a chronology for trial prep — reading every document, extracting dates and facts, and organizing them into a timeline takes 3 days of manual work that could be spent on actual case strategy
Where it fits in your workflow
Before Uncover Legal
Litigation team or document-heavy legal team receives a chaotic matter file from multiple sources -> documents need to be structured, searched, summarised, and turned into a reliable matter narrative before lawyers can draft, advise, or prepare for hearings
After Uncover Legal
Uncover structures the file, builds summaries and timelines, answers document questions, and prepares initial drafts with citations -> lawyers verify the results -> outputs move into briefing, advice, due diligence conclusions, or client-facing updates
Integrations & hand-offs
Documents arrive from existing DMS or collaboration repositories -> Uncover ingests and structures the corpus -> AI assistant, summaries, and timelines produce usable work product -> lawyers and clients can access the matter through the platform. Public integration pages name iManage, Epona, and SharePoint, but implementation detail beyond those names is still shallow.
Community Data
Loading practitioner-sourced data…