Enterprise legal AI platform with agents, a document vault and legal research, deployable in US, EU, Swiss or Australian regions and sold by quote only.
Large firms and in-house teams whose security committee will decide the purchase before the lawyers do. Harvey publishes the deepest compliance detail of any legal AI vendor we looked at: processing region choice across the EU, Switzerland, Australia and the US, plus compliance badges for SOC 2 Type II, AIUC-1, CCPA, GDPR, ISO 27001, ISO 27701 and ISO 42001, and enforcement of your existing iManage ethical walls. It also has real developer documentation with per-endpoint rate limits, so a firm that wants to wire Harvey into its own tools has a published path.
Any firm that needs to know the cost before investing weeks in procurement: harvey.ai publishes no price, no tier list and no trial, harvey.ai/pricing returns 404, so the first number you see comes from a sales conversation. Small practices and sole practitioners are effectively out, because API tokens, Assistant API access and connector availability are all governed by your order form rather than a plan you can buy. Firms that need a specific connector contractually committed should also note that the Connector Library page names dozens of connectors but publishes no availability status for any of them, and the iManage and NetDocuments setup articles sit behind a customer login.
Pros
Cons
Harvey does not publish pricing. There is no pricing page, no tier list, no per-seat rate and no free trial anywhere on harvey.ai, and harvey.ai/pricing returns a 404, so every quote comes through a demo or contact request. What your firm can actually use is set by the order form, including whether API tokens appear in workspace settings, so scope that in the same negotiation.
Harvey runs on Microsoft Azure and lets customers choose processing in the EU or Switzerland, or in Australia, with the US also listed. Subprocessors are held to the same localisation. The developer docs back this up with regional API hosts: api.harvey.ai, eu.api.harvey.ai and au.api.harvey.ai. Customers set their own retention period and can delete data at any time.
No, not by default. Harvey states it does not use inputs, outputs or uploaded documents to train underlying models and that its contracts prohibit model providers from doing so, with Zero Data Retention required of those providers. Training on your data happens only if you explicitly request it, and Harvey says the resulting bespoke model is created exclusively for you and never used for other customers.
Yes to both. The platform page lists Word and Outlook under 'Use Harvey in' and iManage under both 'Use Harvey in' and 'Pull context from'. iManage also appears in the Connector Library under document management and ethical walls. Note that the Connector Library page publishes no availability status for any connector, so confirm each one on your order form.
Facts sourced from the vendor’s own site, last verified 2026-10-24.
The Weekly Source
One email a week. New listings, repriced tools, and the ones we would skip - including this one if its pricing changes.
