Comparison · Kodori vs iManage Work
Kodori vs iManage, honestly.
iManage owns the legal DMS market because it earned the trust of records partners over twenty years. We’re the new entrant. Here’s a side-by-side that doesn’t pretend we win every category — what you trade getting either choice.
| Dimension | iManage Work | Kodori |
|---|---|---|
| Architecture | Document store + add-on AI ("iManage Insight"). The agent is bolted on top of existing repository APIs. | AI-native from the ground up. Every operation — classify, file, retain, share, search — is a typed MCP tool the agent calls with the same authority as a human. |
| Search | Full-text via Ravn / RAVN.AI. Permission-trimmed. Strong for exact-phrase + metadata queries. | Hybrid: Postgres FTS + pgvector embeddings, fused via Reciprocal Rank Fusion. "agreements about confidentiality" surfaces an NDA even when the word "NDA" never appears. |
| Audit trail | Per-document audit log; tamper-evidence depends on the back-end deployment. | Per-tenant hash-chained event log. Every event's prev_hash is the SHA-256 of the previous event — tampering is detectable without re-running anything. |
| Email filing | Outlook plugin — multi-click dialog, per-user install, brittle on platform updates. | Per-tenant email ingest address. Forward from any client. The agent auto-classifies sensitivity, suggests a matter, and proposes keywords. Human confirms. |
| Ethical walls | Mature; integrated with conflicts management; the gold standard for legal. | Per-document deny rules in the same permissions table that grants explicit reads. Deny always wins, enforced at the index. Conflicts integrations land in Phase 4. |
| Legal hold | iManage Records Manager add-on. Subject preservation; release workflow. | Built-in. Bind documents in one click. Held records refuse delete, refuse retention disposal, refuse sensitivity downgrade. Subjects stay on the hold record forever as audit evidence. |
| Retention | iManage Records Manager. Mature, auditable, designed for the records-management persona. | Retention classes + human-confirmed review queue. No 3 a.m. auto-deletion in v0 — every disposal is human-approved with a captured reason. Auto-tombstone behind a tenant flag in v0.2. |
| Matter-level metadata inheritance | Workspace-level defaults via custom1..custom30 fields and matter-type templates. Configurable but stored in a separate table; sensitivity / retention defaults live in Records Manager workflows that are configured separately. | Configure default sensitivity tier + default retention class on any Collection (matter / project / drawer / folder / cabinet / custom). Members inherit on add — sensitivity is highest-tier-wins (never demotes), retention is no-override (preserves any existing assignment). One MCP tool sets the rules; another backfills across pinned + rule-matched members. Apply in plain English: "set the Acme matter to confidential and 7-year retention." See D294. |
| Bulk metadata operations | Mass-update via Documate / iManage Workflows: select N docs, apply fields. Functional but UI-driven, hard to script across saved searches / collections programmatically. | Four bulk MCP tools (sensitivity / retention / collection-pin / freeform metadata jsonb) all accept a "source" argument: collection, saved search, or "uncollected" docs. 500 per call default, paginated for larger sets, hold-deny-wins where applicable, audit-event per affected doc. The agent reaches for them automatically when you ask "tag every doc in Q1 Invoices with matterNumber=2024-0042." |
| Office add-ins | Word, Outlook, Excel, PowerPoint — all production-grade. | Outlook + Word + Excel + PowerPoint task panes all shipped (sideload via /office). One Kodori API key signs into all four. Outlook files email + attachments from the ribbon; Word / Excel / PowerPoint save as new doc OR new version with optional version label. Self-hosting-aware manifests. |
| Public API | iManage Work API; documented; partner ecosystem. | REST API at /api/v1 (read + write), OpenAPI 3.1 manifest, opt-in scopes per key, HMAC-signed webhooks (with native Slack Block Kit format). |
| Public MCP server | No MCP surface. Insight is iManage's own UI; third-party AI clients can't connect. | POST /api/mcp speaks the Model Context Protocol over Streamable HTTP. Claude Desktop, Cursor, ChatGPT desktop, and Kodokyo's agent connect with a Kodori API key and call the same 75+ tools the internal agent uses. Audit-attributable. |
| Inbound search across firm-wide content (Slack / Outlook / SharePoint / Drive) | iManage searches iManage. The Slack thread where partners argued about scope, the Outlook chain where opposing counsel raised an objection, the SharePoint folder where exhibits live — none of those are searchable from inside iManage Work. | Six external connectors live: Slack, Gmail, Outlook, SharePoint, OneDrive, Google Drive. Messages and file attachments index into the same FTS + pgvector retrieval Kodori uses for native uploads. The agent's `unifiedSearch` tool fires both legs in parallel and fuses via RRF — partners ask "every reference to the Brennan staircase incident" and get hits across native documents AND connected Slack / email / Drive in one ranked list. OAuth tokens encrypted at rest (AES-256-GCM, BYO-KMS-extensible). GDPR Article 17 right-to-be-forgotten purge on connector revoke. |
| AI agent | iManage Insight — RAG-style retrieval, copy-paste workflow, no autonomous mutation. | Native typed-tool agent. Asks "what is in this matter?" using the same hybrid search the UI uses; can rename, move, share, hold, retain, dispose, restore — every consequential action behind a "what's your reason?" prompt. |
| Deployment | iManage Cloud (managed) or self-host (Work Server). Region selection at the top tier. | Vercel + Neon + Cloudflare R2, US-East at MVP. BYO-bucket at the top tier. Multi-region from Phase 6 when EU customers justify. |
| Compliance posture | SOC 2 Type II, ISO 27001, HIPAA-ready, 21 CFR Part 11-capable. | SOC 2 Type I is `audit-pending` (substrate ready; auditor engagement gated on revenue / funding). Type II sequenced after Type I (12-month observation). HIPAA + BAA is `customer-anchored` (substrate ready; engagement starts on a healthcare design-partner contract). 21 CFR Part 11 conformance claim is **live today** (section-by-section at /legal/21-cfr-part-11). Honest cert table on /security. |
| Pricing | Enterprise contracts, often $80–$120 per attorney per month plus implementation. Total firm cost frequently $250k+. | Three tiers, per-seat pricing, no implementation fees. See /pricing for current numbers. |
| Migration | Owns the ecosystem; migrating OFF is the question, not migrating IN. | iManage Cloud REST connector ships beta today (real OAuth2 client-credentials, paginated discovery, custom-field metadata pass-through, document content download). S3-bucket connector ships ready for the universal export-to-bucket pattern. Discovery + commit are both live; commit is batch-by-batch with credentials in-memory only (never persisted in Kodori's DB). Design-partner co-development for first iManage cutover. |
| Document compare / redline | Litera integration (paid third-party software, per-seat license). | Word-style word-level redline shipped built-in. Insertions in green, deletions in red strikethrough on /doc/[id]/compare; mode toggle to unified line-level view for code or data. No third-party dependency, no per-seat license. |
| AI document generation | No equivalent. iManage Insight retrieves; doesn't draft. | Use any Kodori document with extracted text as a structural template. Type instructions, Claude Opus drafts a new document preserving structure + adapting context. Generated draft lands as a Kodori record with metadata linking back to the template — audit chain captures the lineage. |
Highlighted cell indicates the dimension favours that product on a generic mid-market deployment. Your firm’s specific weighting may differ.
Common questions.
- Is Kodori a drop-in replacement for iManage today?
- Honestly: not for the entire iManage feature surface, but the gap has closed substantially. Office add-ins (Outlook + Word + Excel + PowerPoint), Word-style redline compare, AI document generation from templates, AP three-way + line-item match, AEC RFI tracker, compliance reports, and the iManage migration connector (beta) all ship today. What's still ahead: conflicts integrations (roadmap), SOC 2 Type I + Type II reports (Type I is audit-pending — substrate ready, gated on auditor engagement; Type II sequenced 12 months after), and field-tested iManage migration on a real customer tenant. Usable today for a greenfield matter or a parallel-run evaluation; the migration path to cut over is the engineering conversation.
- When will the iManage migration connector be ready?
- Connector code is real and shipping today (status: beta). The OAuth2 client-credentials flow + paginated discovery + custom-field metadata pass-through + document content download are all real REST against iManage Work Cloud. "Beta" because it's field-tested only after the first customer migration project — operators with iManage developer credentials can run discovery + batch commit today; we tune pagination + field-mapping based on real-world behavior on the first cutover. Design partners get prioritized white-glove migration support.
- How does Kodori compare to NetDocuments specifically?
- NetDocuments shares iManage's broad architecture but is cloud-first. Most of the analysis above transfers — Kodori wins on AI-native architecture, search quality (hybrid vs FTS-only), audit defensibility (hash-chained vs deployment-dependent), pricing, and email filing UX. NetDocuments wins on conflicts integration depth, Office add-in maturity, and current SOC 2 / HIPAA posture.
- What if we love iManage Insight's RAG?
- iManage Insight retrieves and quotes; Kodori retrieves, quotes, AND mutates. Asking the agent to file an email, apply a hold, defer retention, or rename a document calls the same MCP tool the UI button does — auditably, reversibly, with a captured reason. That gap is the architectural reason we're calling Kodori "AI-native" rather than "AI-enhanced."
- Can we run both side by side?
- Yes. Today's recommended path for firms shopping us is exactly that: keep iManage as system-of-record, point a few specific matters at Kodori for a 60-day evaluation, validate that search, audit, hold, redline, and retention all hold up to your firm's standard. The iManage connector (beta) handles the cutover when you're ready.
Try Kodori on your own matter.
Five minutes from Google sign-in to a working DMS on your own documents. Run it side-by-side with iManage for sixty days. We won’t pretend we’re a drop-in replacement — we’ll show you which gaps matter to your practice.