Blog/Private AI for M&A due diligence document review
M&A

Private AI for M&A due diligence document review

By Samuel Seidel · Updated September 9, 2026

AI can take junior-associate hours out of due diligence, but a general-purpose AI API puts a vendor between the deal team and a data room full of material non-public information. This post covers what changes when the review model runs on a dedicated machine instead, and what doesn't. It is not legal or financial advice and doesn't replace outside counsel or the deal team's judgment.

What sits in a data room before a deal is announced

A due diligence data room for an acquisition typically holds financial statements not yet public, customer contracts with pricing terms, cap tables, pending litigation summaries, employee compensation data, and often a first draft of the deal terms themselves. All of it is material non-public information under securities law in most jurisdictions, and all of it is sensitive independent of whether the deal ever closes. If the deal falls through, or leaks before signing, the damage isn't hypothetical: stock moves, competitors adjust, and counterparties who trusted the confidentiality of the process stop trusting it.

Deal teams increasingly want AI to help work through the volume: summarizing hundreds of contracts for change-of-control clauses, flagging inconsistencies between representations and underlying financials, or drafting first-pass diligence memos. That saves real associate time. The question is where the documents go to get that summary.

What changes with a dedicated review model

A general-purpose AI API is a shared endpoint. Whatever the vendor's contract says about retention or training, a signed NDA with the counterparty doesn't automatically cover what your AI vendor does with the text you send it. Running the review model on a dedicated DGX Spark removes the AI vendor: the deal documents go to your own model on a machine assigned only to you. There's no vendor log and no plan-tier distinction between "used for training" and "not."

A rented Spark is still a GPUwerk-run machine (its own in Czechia, or a partner's in the country the console shows), operated under its published DPA, and your NDA may say who can process deal documents, so check it before a live data room goes on the machine.

In practice this looks like Open WebUI pointed at the deal team's document set, or a retrieval setup over the data room contents so associates can ask questions against the actual filings instead of re-reading each one. The architecture in the guide to on-premise RAG applies directly; only the sensitivity of what's indexed differs.

How a deal team uses this

A typical setup: the data room's contract set gets loaded into a retrieval index on the Spark, and associates ask it questions like "which customer contracts have change-of-control termination rights" or "flag any employment agreements with golden parachute clauses above a threshold." The model returns citations back to the specific document and page, which a human still opens and reads before it goes in a memo. Law firms use the same pattern in internal document review tools. Here it runs on one machine for one deal instead of a firm-wide platform, which matters when even the fact of the negotiation is not yet public.

Because a Spark is billed per minute against a prepaid balance, a deal team can start one for the diligence window and terminate it once the deal signs or dies, instead of paying for a document-review platform between deals. Terminating deletes the workspace from the node, so the deal material doesn't sit in a standing system after the reason for access is gone. GPUwerk keeps no other copy of the workspace.

Where the line still sits with counsel

None of this changes who is responsible for the substance of the diligence. Deal counsel still reviews the actual representations, still runs the real risk assessment, and still decides what goes in the closing memo. An AI-assisted first pass through hundreds of contracts is useful for the same reason a well-organized data room is: the lawyers spend their time on judgment calls instead of opening every file. It doesn't change the standard of care expected of them, and it shouldn't be treated as having done the legal analysis on its own.

What this doesn't solve

Self-hosting the model doesn't create attorney-client privilege, doesn't substitute for a lawyer's read of a representations and warranties clause, and doesn't change who on your team has access to the data room; that's still governed by your own access controls and the deal's confidentiality agreement. An AI summary of a contract is a starting point for a human reviewer, not a substitute for one, particularly on anything that will end up in a purchase agreement. What a dedicated model removes is one specific exposure: a third-party AI vendor sitting between your deal team and documents that, if they moved at all before signing, would move the stock.

Related pages

First top-up: pay $20, get $30 in credit

Run diligence review without an AI vendor in the data room.

Rent a Spark for the diligence window and terminate it when the deal signs or dies. Read the Open WebUI setup →

A dedicated DGX Spark in Europe, North America or East Asia, $0.79/hour, billed per minute. $30 of credit is about 37 hours of compute.

Your data stays on a machine assigned only to you. GPUwerk processes it under its published DPA.

Create account See private LLM hosting