N/001 · 2026-08

Local AI for finance: nothing leaves the building

The confidentiality problem with cloud AI in tax, and the local-first architecture that solves it.

Every finance team having the AI conversation hits the same wall: the tools are genuinely useful, and the data absolutely cannot be pasted into someone else's server. Client records, filings, working papers — in tax, confidentiality is not a preference to trade away for convenience. It is the engagement.

The answer isn't to skip AI. It's to move the AI to the data instead of moving the data to the AI. Open-weight models have become good enough to run serious tax workflows, and a single on-premise, DGX-class GPU server puts that capability inside the firm's own walls.

The architecture is simple to state: models run locally, workflows are sealed inside the network boundary, nothing calls an external AI API, and every automated step is logged. Data prep, first-pass checks, status tracking, drafting — all of it happens where the data already lives.

The last rule doesn't change with the hardware: automation prepares, humans sign. A local model earns the same skepticism as a cloud one. What changes is the risk surface — because the fastest way to make sure client data never leaks from an AI pipeline is for it never to leave the building at all.

Takeaways

  • Move the AI to the data, not the data to the AI.
  • Open-weight models on on-prem hardware make local-first practical.
  • Sealed boundary + logged steps + human sign-off = AI a compliance function can defend.