Augmetec vs Nuix Neo: how they compare in 2026

The models drive several core capabilities and sit on an investigations platform that would work without any of them. The AI functions are named and specific on the platform page as modified in November 2025: identifying relevant evidence and building fact patterns against a Line of Enquiry using what the vendor calls accurate AI algorithms, document fraud detection, automatic identification of witnesses and preparation of interview questions, chronology building, and AI-driven triage, scoping and categorisation of cases. Underneath sits a full case management system that predates the models and delivers a great deal on its own: a centralised datalake, evidence management, reusable templates, customisable workflows, dashboards, collaboration, single sign-on, enterprise integrations and automated evidence bundle creation. Strip the models out and an investigations team still has a working command centre, which is what keeps this off the top band. The master services agreement reinforces the point by never mentioning artificial intelligence in its operative terms at all. Checked 5 September 2026.

The models are the engine of a core capability layered on a product that would still function without them. Nuix Neo's AI classifies and contextualises data, applies language models described as trained for the customer's use case to cut review volume, and drives automated redaction; remove them and the Nuix Engine, processing more than a thousand file types into searchable form, plus early case assessment, review in Nuix Neo Discover and investigation workflows remain, which is the product the company has sold for years. The EULA restricts use to internal ediscovery, investigations and information governance projects and describes the licence by data volume processed, not by AI. Home page, products page, Neo Legal and Discover pages and EULA read 6 September 2026.

Accuracy and defensibility are the central promise and neither is measured. The platform page states that a team can answer questions defensibly, that investigations are conducted accurately and defensibly, and that evidence identification runs on accurate AI algorithms, alongside industry-leading document fraud detection. Not one of those claims carries a figure, a test set, an evaluation, an error rate or a statement of failure modes, and no accuracy or benchmark material appears anywhere on the estate. Nor is grounding described: nothing states whether a finding surfaced against a Line of Enquiry carries a link back to the document and page it came from, which is the control a reader would look for on a product whose output feeds regulatory reporting. The agreement is markedly more candid than the marketing and the gap is the finding: clause 2.5 has the customer acknowledge that the software may contain bugs, errors and other defects, may contain design flaws, and may produce unexpected results from its functionality. A product sold on defensibility and contracted for on an acknowledgement of unexpected results is exactly the marketing-against-agreement shape.

Accuracy is asserted without measurement, and the primary-authority limbs do not apply. The vendor states that its language models improve accuracy and reduce the data to review, and the telecommunications page claims elimination of up to ninety-five per cent of non-relevant data early, with no test set, method or recall figure published; EULA section 10.1 disclaims any warranty of truth or accuracy of data or information generated and makes the licensee responsible for determining whether generated information is accurate. The product classifies and culls documents rather than citing law, so the citation limbs are not held against it; what the band asks of a review tool, a measured statement of how often its classification is wrong, is not published on the surfaces read. Product pages and EULA read 6 September 2026.

The level of automation is stated with unusual precision for one feature and no control structure is described anywhere. The platform page says case scoping is semi-automated, that smart actions suggest team actions to progress cases, and that witnesses are identified and interview questions prepared automatically in real time. Semi-automated and suggest are real words about where the machine stops, and they are why this is not the floor band. What is absent is everything around them: nothing states which outputs require review before use, what a reviewer sees, at what point the system acts without a person, what happens when a fraud detection flag is wrong, or whether generated material is marked as generated. No abstention behaviour or confidence signal is described. The agreement allocates the consequence without describing the mechanism, clause 10.2 providing that the customer assumes sole responsibility for results obtained from use of the software and for conclusions drawn from such use. On a product that prepares interview questions and identifies witnesses in a fraud or bribery investigation, the unstated review point is the live question.

A written commitment that the models work alongside reviewing people, with real review surfaces, short of the full control structure. The review product is described as responsive review with AI-enabled workflows that support faster and more precise human review, the bring-your-own-AI option is described by a named customer as running within its own environment under its own compliance controls, and automated workflow templates run culling and redaction that a reviewer then works from. What is not published is the threshold at which a document is excluded from review, what executes without a person, or a stated route back after a misclassification beyond ordinary review. Discover, Neo Legal and Neo pages read 6 September 2026.

No production evidence was located. No customer is named anywhere on the estate, no logo wall appears, no case study exists, and no deployment is described or dated. The single customer voice is one unattributed sentence on the About page, carrying no name, role or organisation, saying that LEIAA is clearly built by practitioners for practitioners. Two figures are published on the platform page and neither is attributed or explained: administrative effort alleviated by up to 45 per cent, and the platform being up to 80 per cent cheaper than other platforms, the second being a competitive pricing claim rather than an outcome and naming no comparator. The founding team's own experience is set out in detail, including more than 150 investigations conducted by the chief executive before founding the company, which is credential rather than deployment evidence and is recorded as such. Searched the home, about, platform and security pages, the master services agreement and the site navigation on 5 September 2026.

A named customer without figures, and figures without a named customer. Donn Hoffman, Chief Privacy Officer and Deputy District Attorney at the Los Angeles County District Attorney's office, is quoted on the on-premises Discover page about implementing bring-your-own-AI within the office's own environment, with no measured outcome; IAV GmbH is named on the same page as an ediscovery services customer. The up-to-ninety-five-per-cent data reduction figure on the telecommunications page is unattributed and undated. Nothing joins a named customer to a figure. Discover on-premises page and telecommunications page read 6 September 2026; customer stories were not opened.

Substantive contractual commitments, a rare express reference to privilege, and no privilege treatment as such. Clause 8.3 of the published master services agreement is the core: the customer retains full title to Customer Content, and without the customer's consent Augmetec will not access, use or disclose it except as reasonably necessary to support the customer's use of the software, respond to support requests, or for any other purpose authorised by the customer in writing. That is a closed purpose list rather than an open licence. Clause 8.4 permits collection of usage and performance data expressly excluding anything that could identify the customer or its own customers or that is confidential or privileged in nature, which names privilege directly. Clause 6 makes Customer Content the customer's confidential information under a five-year regime, and the addendum requires everyone processing the data to be under a strict duty of confidentiality. Separation is documented rather than claimed, with each customer on a dedicated instance and Annex II stating that segregation procedures prevent other customers from accessing customer data. What is missing is treatment rather than acknowledgement: nothing describes how privileged material is handled once inside, no matter-level walls within a customer are described, and no model provider is named.

Substantive published commitments, structural and contractual, short of the full picture. The deployment is on-premises under the EULA: one copy installed in the licensee's own production environment, so matter data stays with the licensee, and EULA section 3.4 has the licensee own Licensee Data and license it to Nuix solely to provide support. Section 9 treats licensee data as confidential information and sections 9.3 and 9.4 commit, on any legally compelled disclosure, to prompt notice where permitted, assistance in seeking a protective order, and disclosure of no more than counsel advises is required. The bring-your-own-AI option keeps third-party models inside the customer environment. Not located: any statement on training use, since the agreement is silent on machine learning, any description of matter-level segregation inside the review product, and any treatment of privilege or work product. EULA read in full; product pages read 6 September 2026.

Nothing published addresses the advice line. No statement that Augmetec is not a law firm, no disclaimer that output is not legal advice, no description of the professional judgement required before a finding is acted on, no jurisdiction limit and nothing on supervision or competence was located on the platform page, the about page, the security page or in the master services agreement, which is the natural home for such a clause and contains none. The nearest provision is clause 10.2, under which the customer assumes sole responsibility for results obtained and conclusions drawn, which allocates liability rather than describing what the product is not. The exposure is specific on this product class: the platform builds fact patterns, identifies witnesses, prepares interview questions and produces investigation reports in matters concerning fraud, bribery and improper conduct, where a conclusion carries consequences for named individuals. The terms of use page governing the website was not opened in this pass and is the rebuttal route.

The advice line is not drawn and the audience is broad. The EULA confines use to the licensee's internal ediscovery, investigations and information governance projects and makes the licensee responsible for the accuracy of generated information, but no surface read states that the product does not provide legal advice or how it supports a supervising lawyer's duties; the buyers named span law firms, corporate legal, law enforcement, financial regulators and telecommunications companies. No jurisdiction limit is named beyond export control and the territory clause. EULA and product pages read 6 September 2026.

No governance position of any kind was located. There is no responsible AI page, no principles statement, no accountable owner or function named for model behaviour, no pre-release evaluation regime, no AI management system and no certification such as ISO 42001. Nothing addresses uneven output, and the omission has a sharp edge on this product: a system that identifies which individuals are witnesses, flags documents as fraudulent and builds fact patterns about alleged improper conduct is making determinations about named people, and nothing published describes how those determinations are tested or governed. The governance material that does exist is security governance and is credited on the stewardship row rather than counted twice, comprising an information governance committee and ISMS group, a dedicated person overseeing information security and compliance, and certified security staff. The chief security officer holds a doctorate in machine learning, which is a credential rather than a governance framework. Navigation and footer inventoried 5 September 2026.

Responsible-use language without a published mechanism, testing regime or accountable owner. The review product is marketed as powered by ethical AI, the Neo page describes language models trained to the customer's use case, and the vendor writes about capturing AI productivity responsibly; no governance framework, ISO 42001 or equivalent, pre-release testing description or statement about uneven classification across document types or languages is published on the surfaces read. Product pages read 6 September 2026.

Among the most completely documented stewardship positions in this corpus, held off the top band by one absence. The published addendum's Annex II runs to several pages of specifics: AES-256 at storage system and storage device level with separately keyed backups, TLS 1.2 or greater in transit, VPN and multi-factor authentication, access control lists on a need-to-know basis with differentiated access profiles, automatic account locking and idle logout, network separation through a DMZ, a web application firewall, logging of access, modification, entry and deletion, intrusion detection, disaster recovery and continuity planning, physical security of data centres described down to visitor logging and video surveillance, an ISMS group and a named accountable security function, internal and external audits, penetration testing with triage and remediation, and a responsible disclosure programme. Incident practice is contractual rather than asserted: clause 2.13 commits to informing the customer of a security incident without undue delay and within 72 hours, with cooperation on the customer's own reporting duties. Deletion is addressed at clause 2.14, destroy or return on written instruction at termination. What is missing is a retention period: nothing states how long data is held while the agreement runs, only that it is retained as required to perform obligations.

Some of the ground is covered, much of it by the deployment model rather than by published policy. Under the EULA the licensee installs the software in its own environment and is solely responsible for backing up and securing Licensee Data, Nuix processes personal information only with prior written consent and then under a DPA that prevails over the licence, and Usage Data sent to the licensing server excludes Licensee Data. No retention period, deletion commitment, sub-processor list or incident-notification practice for hosted deployments was located; the DPA at the URL the EULA names and the 2020 Discover SaaS terms of use were not opened and are the rebuttal route for the hosted product. EULA read in full 6 September 2026.

A real two-sided position published in full, with a cap a buyer should read before signing. Clause 9.2 commits Augmetec to indemnify the customer against direct damages arising from third-party intellectual property infringement claims connected to use of the software, with a remedy ladder at 9.3 covering procurement of continued rights, replacement or modification on stated equivalence conditions. Clause 10.3 preserves liability for death or personal injury, fraud and wilful misconduct outside all caps. Against that, clause 10.1 provides the software as is with the customer assuming all associated liability, and clause 10.4 sets the ceiling at the lesser of one hundred per cent of a contract year's subscription fees or twenty thousand US dollars, with the intellectual property indemnity capped at the lesser of two hundred per cent or fifty thousand dollars. On an investigations platform sold to enterprises, twenty thousand dollars is a low absolute ceiling and it is the operative number for everything except the IP indemnity. The exclusions at 10.4 are also unusually pointed for this product, expressly excluding loss of privilege and loss of confidentiality. Nothing warrants the accuracy of any output.

A real published position on liability, short of the full picture because the vendor gives no indemnity. EULA section 11.2 caps Nuix's aggregate liability at the licence fee paid under the applicable order form in the preceding twelve months, section 11.1 excludes indirect, consequential, and lost-profit claims and bars claims not brought within a year, both carving out intentional misconduct, gross negligence and bodily injury; section 10.3 gives repair, replacement or a prorated refund as the sole remedy for a warranty that cannot be excluded, section 10.1 disclaims accuracy of generated information, and section 11.5 states that Nuix is not an insurer and the licensee looks to its own insurance. Only the licensee indemnifies, under 11.6. A signed direct agreement supersedes the EULA. EULA read in full 6 September 2026.

Integration is claimed as a core proposition and no counterparty is named. The platform page promises core enterprise integrations, single sign-on and secure integrations with existing platforms, document management systems, and Microsoft and Google, which identifies the productivity and identity estates by name and the document management layer only as a category. The agreement contemplates the mechanism at clause 4, covering third-party services the customer connects and single sign-on authentication, and confirms that connecting a service authorises Augmetec to access and store information from it. Nothing published states what data moves between LEIAA and any external system, in which direction, on what trigger, or what a firm must configure, and no API or developer documentation was located; the addendum's data description mentions material from Microsoft Teams, Slack, WhatsApp, Telegram, Amazon Chime and Google Meet, but as categories of personal data that may be uploaded rather than as connectors. A knowledge base exists on a third-party support platform and was not opened in this pass; it is named here as the limit.

Integrations are referred to without documentation an implementer could use on the surfaces read. The Engine's ingestion of more than a thousand file types and connection to data sources is the product's core, the EULA contemplates APIs as ancillary software licensed for use with the software, and the Neo Legal page describes orchestrating business applications across the enterprise, but no integrations page or documentation was opened and no document, matter or review system connection is described with what moves and in which direction. Product pages and EULA read 6 September 2026; the documentation is the rebuttal route.

The tenancy limb is answered more completely than on any other record in this pull, and the region limb is not answered at all. The security page states it plainly under its own heading, your LEIAA, your environment: each customer's instance is hosted on a separate, dedicated environment available only to and accessible by that customer, on a virtual private cloud architecture segregated for data isolation. The agreement repeats it at clause 10.1, that the instance allocated to a customer will be held on separate, dedicated infrastructure, and the software is defined as reached at a customer-specific subdomain of leiaa.com. Annex II adds that customer data is separated on their own instances with segregation procedures preventing access by other customers, and names Google Cloud Platform as the hosting infrastructure. Against that, no region is named anywhere. The virtual private cloud is described as a global network spanning multiple regions, which describes reach rather than residency, no region choice is offered, and no residency commitment appears in the agreement, though the addendum does carry full restricted-transfer machinery through the EU standard contractual clauses and the UK addendum.

The deployment model is stated clearly and residency for hosted deployments is not. Nuix Neo Discover is offered as a native on-premises deployment for organisations with data sovereignty and chain-of-custody requirements, the EULA licenses one copy installed in the licensee's production environment, and the vendor's own description is that the customer keeps complete control over its sensitive information; a hosted route exists through service provider partners and third-party hosting providers under separate terms. For on-premises use residency is wherever the licensee puts it, which answers the question fully; for the hosted route no region, tenancy model or processing location is stated on the surfaces read. Discover on-premises page and EULA read 6 September 2026.

Four certification marks displayed as images, no scope, no date, no auditor, no report, and an agreement that describes something weaker than the badges imply. The security page carries marks for ISO/IEC 27001:2022, HIPAA, GDPR compliance and an AICPA SOC logo, each an image with no accompanying text claiming certification, naming a certifying body or stating a period or scope, and one of the image filenames misspells the statute it refers to. Nothing in the page text asserts that any certification is held. The published agreement is more precise and points lower: Annex II lists regular benchmarking and testing with industry standards, giving ISO 27001, the SANS Top 20 controls and NIST guidelines as examples, and qualifies it as applying on certain systems. Benchmarking against a standard on certain systems is not certification to it, and a buyer reading the badge and then the annex would find two different propositions. A trust page exists at a published subdomain, named twice in the agreement as the location for backup and disaster recovery detail and for subprocessor change notices, and was not opened in this pass; it is the rebuttal route and the cheapest upgrade on this record.

Certification is stated on the product's own surface, short of a report reachable without asking. The Nuix Discover page states that the product holds globally recognised certifications including ISO 27001 and SOC 2. No auditor, coverage period, report type or route to the report is published, and no trust centre was located on the surfaces read; the EULA adds no security warranty beyond the licensee's own obligations. Discover page and EULA read 6 September 2026.

The vendor refers to its algorithms and identifies nothing underneath them. The platform page speaks of accurate AI algorithms and AI-powered analytics, and the addendum's own definition of the services includes the development of future functions, features, tools, algorithms and models, so a model layer is acknowledged as existing. No model is named, no version, no provider and no hosting arrangement for the model layer, and no commitment to notify customers when any of it changes was located. Clause 2.4 concedes the shape of the gap without filling it, stating that the services may use technology and data licensed by Augmetec from third parties, sublicensed to the customer, and naming none of them. One infrastructure provider is named and is not a model: Google Cloud Platform, identified in Annex II as the hosting environment and as the source of the secret management service. The approved subprocessor list at Annex III is referenced in the agreement and fell outside the extraction window of the published PDF, so its contents are unread and nothing is inferred from them in either direction.

The supply chain is partly disclosed. The vendor describes proprietary AI in the Engine and bespoke language models trained for the customer's use case, and a bring-your-own-AI option that lets the customer run its chosen models inside its own environment, which places the third-party model, where it runs and who controls it with the customer; a named customer describes using the latest AI advancements within its own environment on that basis. What is not published is the name of any model Nuix supplies, any provider behind its own models, or a change-notification commitment. Neo page, Discover on-premises page and EULA read 6 September 2026.

The unit and the commercial structure are established from the published agreement, and no figure appears anywhere. There is no pricing page in the site navigation and every route is a demo request. The agreement supplies the shape: the software is licensed under an Order Form as a Package with stated features and pricing, User Rights itemise the number of user licences and the software instance subscribed to, each authorised user holds a single non-shareable account, and the commitment runs across an Initial Term with defined Renewal Terms. A buyer can therefore establish that this is per-user licensing on a committed term with the package defined in an order form, and cannot establish any rate, band, minimum or implementation cost. One published number is a comparative claim rather than a price and is recorded as such: the platform page states that the product is up to eighty per cent cheaper than other platforms, naming no comparator and no basis. The floor band does not fit, because the unit of charge is published even though the price is not.

The unit and structure are stated in the agreement without the figure. EULA section 5.2 defines a consumption-based licence with a unit of one terabyte of uncompressed data processed per annum, aggregated across instances, expiring unused at the end of each twelve-month term, with quarterly usage reporting and true-up at order-form overage rates; section 7.2 sets automatic twelve-month renewals with ninety days' notice and section 4.1 folds standard support into fixed-term licence fees while premium tiers cost extra. No figure, tier name or price page was located. EULA read in full 6 September 2026.

The practice is defined with real precision and the buyer boundary is left open. What the product covers is stated repeatedly and consistently: internal and regulatory investigations end to end, from inception through scoping, evidence management, witness interviews and analysis to reporting, extending to ethics, compliance and regulatory reviews. The subject matter is evidenced rather than asserted, with the addendum's own data description naming identity documents, invoices, expense receipts, financial payment data and material from corporate and ephemeral messaging applications, and the founder's stated background covering fraud, money laundering, bribery and corruption. That is a clearer account of the work than most records in this lane manage. Users are addressed as law firms and in-house professionals, and beyond that nothing is stated: no firm or organisation size band, no jurisdiction despite an English-law agreement and a UK base, no statement of which investigation types or regulated sectors the product does not suit, and nothing on languages for a platform ingesting multilingual messaging data.

Segment and coverage are described with substance; the boundaries are partly stated. Primary users are listed on the Neo Legal page as law firms managing large-scale ediscovery, corporate legal teams handling regulatory matters and disputes, financial services firms, compliance officers, investigation teams and security leaders, with separate solution lines for investigations, data privacy and industry pages for telecommunications, integrity agencies and financial regulators; the Engine's coverage of more than a thousand file types is stated. The EULA's territory clause and the on-premises option are stated boundaries; no matter type or practice area is named as unsupported. Product pages and EULA read 6 September 2026.