Hanzo is a specialist eDiscovery and investigations vendor focused on preserving, collecting, and assessing modern collaboration data before that data has to be flattened into a painful downstream review project. The strongest corroborated fit is for in-house legal, compliance, and litigation-support teams dealing with Slack, Microsoft Teams, Google Workspace, and other dynamic sources where legal hold, defensible capture, and context-preserving export matter more than generic document-hosting. Hanzo’s public site and use-case pages repeatedly emphasize in-place preservation, review-ready exports, and early investigation over broad end-to-end review leadership. Security posture is better documented than many mid-market legaltech vendors: Hanzo publishes a security page with SOC 2 Type 2, encryption, SSO, GDPR, and CCPA claims, though the detailed report is only available under NDA so this pass still treats most controls as vendor-published rather than independently inspected. Pricing remains private, and independent market validation is thinner than the incumbents: Reddit discussion exists but is sparse, G2/Capterra coverage did not surface clearly in Serper, and the strongest public proof points are vendor case studies plus directory coverage rather than broad practitioner review volume.
Capabilities
Spans 5 product areas: Electronic Discovery, Legal Holds, Compliance and Risk Management, Information , Governance.
Workflow Coverage
Based on published feature listings, this tool maps to 3 workflow areas:
- Filing & Compliance
- Research & Analysis — Early Case Assessment
- Document Review & Management
Workflow mappings derived from published feature lists. Not independently verified.
Company Info
- Founded: 2004
- Team size: 11-50 employees
- Funding: $18.6M
- HQ: United Kingdom
- Sector: Knowledge Management
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, Hanzo is used in these workflows:
What practitioners struggle with
Real frustrations from legal professionals — the problems Hanzo addresses (or should address). Sourced from practitioner reviews, Reddit threads, and case studies.
Legal hold notices go out by email, half the custodians ignore them, nobody tracks acknowledgment — six months later a key custodian deleted relevant Slack messages and now there's a spoliation fight
Company gets hit with a litigation hold and half the relevant data is in Slack threads, Zoom recordings, and Google Drive comments — the IT team exports Slack's native JSON dump and hands 4 million messages to legal, who can't search it, can't filter it, and has no way to identify which channels are relevant without reading every single thread
Where it fits in your workflow
Before Hanzo
Legal or compliance gets a new matter, investigation, or hold notice and realizes the most important evidence sits in Slack channels, Teams chats, Google Workspace comments, or other dynamic collaboration systems that are hard to preserve without losing context.
After Hanzo
Hanzo preserves data in place, scopes collections, and creates exports or review-ready datasets that can feed outside counsel review, internal investigations, regulator response, or broader eDiscovery platforms.
Integrations & hand-offs
Matter trigger or legal hold -> custodian and source scoping across collaboration systems -> in-place preservation and defensible collection in Hanzo -> culling, assessment, and export -> downstream review, production, or investigation memo.
Also used by similar teams
Community Data
Loading practitioner-sourced data…