Comparison · Kodori vs NetDocuments
Kodori vs NetDocuments, honestly.
NetDocuments owns the modern cloud DMS market because it shipped before iManage moved off self-host and because ndMAX brought AI features earlier than incumbents. Here’s an honest side-by-side that doesn’t pretend we win every category.
| Dimension | NetDocuments | Kodori |
|---|---|---|
| Architecture | Cloud-native multi-tenant DMS. ndMAX adds AI features as add-ons; the core repository pre-dates the AI era. | 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 | ndSearch with FTS + metadata-faceted retrieval. Solid for case numbers + party names; concept queries depend on tag quality. | Hybrid: Postgres FTS + pgvector embeddings, fused via Reciprocal Rank Fusion. Concept queries surface relevant documents even without matching keywords. |
| Audit trail | Per-document audit log. Row-level integrity. SOC 2 Type II posture mature. | 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. SOC 2 Type II is sequenced after Type I (which is audit-pending today). |
| Email filing (Outlook) | ndOffice + ndMail Outlook integration. Mature, production-grade. Most firms use it daily. | Per-tenant ingest address PLUS native Outlook add-in shipped today. Filing email + attachments from the ribbon, with thread tracker, per-filing sensitivity override, and in-pane collection picker. Mobile capture from the phone's rear camera works in any browser, no app install. |
| Office add-ins | ndOffice for Word, Excel, PowerPoint. Save-as-version, check-in/out, version compare via Litera. Production-grade. | Outlook + Word + Excel + PowerPoint task panes all shipped (sideload via /office). One Kodori API key signs into all four. Save the active document as new doc OR new version with optional version label + significance flag. Self-hosting-aware manifests. |
| Ethical walls | Mature; integrates with conflicts management. Standard for legal compliance teams. | 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 | NetDocuments 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 | NetDocuments Records Manager. Mature, auditable, designed for the records-management persona. | Retention classes + human-confirmed review queue. No 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 | ndProfiler + ndMatter pre-fills profile metadata at save-time based on matter selection. Sensitivity + retention class via separate workspace policies, configured by records-management persona. | Configure default sensitivity tier + default retention class on any Collection (matter / project / drawer / folder / 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 in plain English: "apply the Smith matter's inheritance to every doc in there." See D294. |
| Bulk metadata operations | ndAdmin batch tools handle metadata updates at scale; UI-driven workflow, plus the open-API for scripted updates. Powerful but persona-restricted (records / admin staff). | Four bulk MCP tools (sensitivity / retention / collection-pin / freeform metadata jsonb) accept a source: collection, saved search, or "uncollected" docs. 500 per call, paginated, hold-deny-wins, audit-event per affected doc. The agent reaches for them automatically: "tag every contract from 2024 with clientCode=ACME." Same governance gates as the single-doc UI. |
| AI agent | ndMAX — copy-paste retrieval workflow, document Q&A, and PatternBuilder document automation. Retrieves; does not autonomously mutate. | Native typed-tool agent. Same MCP catalog the UI calls — rename, move, share, hold, retain, dispose, restore. Every consequential action behind a "what's your reason?" prompt. |
| Public API | NetDocuments API. Documented; partner ecosystem (Litera, NetCases, etc.). | 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. ndMAX adds an in-product chat assistant; third-party AI clients (Claude Desktop, Cursor, ChatGPT) can't connect to call NetDocuments tools. | 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) | NetDocuments searches NetDocuments. ndMAX summarizes documents you point it at — it doesn't reach into Slack threads, Outlook chains outside the email-filing flow, or SharePoint folders containing exhibits not yet imported. | 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. GDPR Article 17 right-to-be-forgotten purge on connector revoke. |
| Deployment | NetDocuments Cloud (managed). US, UK, Australia, EU regions. No on-prem. | 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, ISO 27017, ISO 27018, GDPR-ready, HIPAA-eligible. | 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, typically $40-$70 per user per month plus implementation. Total firm cost frequently $80k-$200k+. | Three tiers, per-seat pricing, no implementation fees. See /pricing for current numbers. |
| Migration | Cloud-only — moving OFF requires their export tooling and a destination. Workspace, profile, and version history portability documented. | Two paths today. (1) The dedicated NetDocuments REST connector (beta) walks /v1 directly — probe validates the OAuth2 refresh token at /v1/OAuth + lists repositories, discover uses cursor-based pagination on /v1/Search, download streams /v1/Document/{id}/Content. NetDocuments' Repository → Cabinet → Folder hierarchy maps to Kodori Collections, and the per-customer profile dictionary (MatterNumber, ClientName, ResponsibleAttorney, etc.) round-trips into Kodori metadata. Region-aware (us / eu / au / ca pods). (2) NetDocuments' export tooling produces workspace bundles that drop into the S3-bucket connector for air-gapped environments. The REST path is preferred for live migrations; the bucket path is the offline option. |
| 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 | PatternBuilder for template-driven document automation (paid add-on; rule-based, not LLM-based). | Use any Kodori document with extracted text as a structural template. Type instructions, Claude Opus drafts a new document preserving structure + adapting context. Bracketed placeholders flag values the operator needs to fill in. Counts against agent question quota; uses Opus by default with Haiku fallback on cap. |
Highlighted cell indicates the dimension favours that product on a generic mid-market deployment.
Common questions.
- Is Kodori a drop-in NetDocuments replacement today?
- 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, the public MCP server, AND the dedicated NetDocuments REST connector (beta) all ship today. What's still ahead: conflicts integrations (roadmap), SOC 2 Type I + Type II reports (Type I is audit-pending; Type II sequenced after), and the NetDocs connector flip from beta → ready (gated on the first real-tenant pilot). Usable today for a greenfield matter or a parallel-run evaluation, including REST-driven migration off NetDocuments.
- How does ndMAX compare to your AI agent?
- ndMAX retrieves and answers — RAG-style document Q&A, contract review, automated drafting via PatternBuilder. Useful but bolted onto the existing repository APIs. Kodori's agent uses the SAME typed MCP tools the UI calls — it can move, rename, share, hold, retain, dispose, restore. The architectural difference is what we mean by "AI-native" rather than "AI-enhanced."
- Will you migrate our NetDocuments workspace?
- Yes — the dedicated NetDocuments REST connector ships in beta today. It walks /v1 directly: probe validates the OAuth2 refresh token at /v1/OAuth + lists repositories, discover pages /v1/Search via opaque cursor 200 docs at a time (optionally scoped to one repository), download streams /v1/Document/{id}/Content. Repository → Cabinet → Folder maps to Kodori Collection paths, and schema-defined profile fields (MatterNumber, ClientName, ResponsibleAttorney, etc.) round-trip into Kodori metadata. Region-aware (us / eu / au / ca pods) so cross-pod tenants pick the right host upfront. Beta because it has been tested on mock fixtures only; the flip to ready follows the first real-tenant pilot. The S3-bucket connector remains the offline option for air-gapped environments via NetDocs' export tooling.
- How does Kodori compare to iManage specifically?
- iManage and NetDocuments share the broad architecture — older repository core with newer AI bolted on. Kodori wins on the same axes against both: AI-native architecture, hybrid search vs FTS-only, hash-chained audit, agent autonomy, pricing. iManage and NetDocuments win on Office add-in maturity, conflicts integration depth, and current compliance certifications. See /compare/imanage for the iManage-specific table.
- What about cloud regions and data residency?
- NetDocuments has the lead here — US, UK, Australia, EU regions today. Kodori is US-East at MVP; multi-region lands in Phase 6 when EU customers justify the operational complexity. If region-specific data residency is a hard contract requirement, NetDocuments wins this comparison.
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 NetDocuments for sixty days — we won’t pretend we’re a drop-in replacement; we’ll show you which gaps matter to your practice.