Sovereign contract intelligence
Private-pilot MVP for supervised contract review; runs in a customer-controlled environment.
Founder-developed contract-intelligence software for Vesh AI that runs on a machine you control. Deployment and evaluation services fit it to the contracts your team actually handles, and a reviewer signs off every answer.
14-day diagnostic · written brief · risks · deployment price
Models, runtimes and hardware · by evidence
The premise
Everything useful a firm knows is already written down.
Everything useful a firm knows is already written down — in packs, mail and working papers. When that material cannot leave the building, the model must go to the file. We draw the boundary once, and the work happens inside it.
The offer · 14 days
No installation, no procurement, no platform commitment. Two weeks of access to the process that hurts, and a written answer at the end of it.
If a sample file is required to write an honest brief, it is listed, time-boxed, and destroyed on the last day. The destruction is written down. Nothing is installed until you say so.
Application MVP · measured on public contracts
Illustrative interface examples; not customer data or production evidence.
Why Vesh
Files stay in your environment
The demonstrated chat, embedding and OCR services run inside the local Docker network. A customer deployment keeps the corpus in customer-controlled infrastructure, with access and network policy agreed for that environment.
Runs on your hardware
The target deployment is hardware the practice owns; a cloud account in its name is planned. The customer controls the account and can end the arrangement without transferring its corpus to Vesh.
Local models and OCR
$ make test-docker-integration
Native PDFs are read locally and scanned pages pass through local OCR. Hybrid retrieval and a local language model produce a review cell that a human accepts, corrects or declines.
Auditable and measurable
Question
Does this contract restrict assignment?
Answer
Present — reviewer must inspect the source-bound passage before accepting.
The application binds a positive finding to indexed source text and records the reviewer decision. The held-out evaluation reports both the metrics that passed and the evidence-overlap and metadata-accuracy gates that did not.
Practice areas
The same runtime underneath, fitted to the document types each practice actually handles. Contract review for legal teams is the current release; the other areas are where the same runtime is headed, in the regulated functions where the file cannot travel.
Law firms and in-house counsel
Privilege is a wall, not a setting. Review runs inside the boundary or not at all.
Primary use case · contract abstraction is in the current private-pilot release; the other uses below are planned
Review runs inside the boundary, against the firm's own index. Privilege is enforced by the absence of a route out, not by a configuration flag.
The letter goes out sounding like the firm that sent it, because the model would be fitted on the firm's own correspondence.
Obligations, dates, caps and liabilities extracted to a schedule where every row points at the clause it came from.
Relevance and privilege ranked with the reasoning shown and logged, so the decisions are reviewable rather than opaque.
Engineering organisations
Ten years of decisions locked in a repository nobody is allowed to paste anywhere.
Application area · not part of the current product release
Ask questions across a codebase that cannot leave the network. Retrieval runs against your own index, on your own hardware, with no source in flight.
Postmortems assembled from logs, tickets and chat inside the perimeter, with each claim pointing back at the artefact it came from.
The design decisions of people who have left, made answerable again — including the reasoning that never made it into a document.
Draft coverage from the specification in your house idiom, for your engineers to review and own.
Accounting and finance functions
Books, packs and filings. The close stops running into the night.
Application area · not part of the current product release
Reconciliation and variance narrative drafted from the ledger and last period's commentary, so the review starts from a draft rather than a blank page.
Working papers assembled and cross-referenced, with a citation behind every figure so the reviewer checks rather than reconstructs.
Statutory and management reporting drafted in the firm's own format, in the register the partners already sign off.
A data room read in hours, with the exceptions listed, sourced and ranked by what would actually change the price.
Operations and procurement
Contracts, certifications, drawings and correspondence, read as one corpus.
Application area · not part of the current product release
Contracts, certifications and correspondence read as a single body of evidence, with contradictions surfaced and sourced.
Tolerances, materials and commercial terms pulled from drawings and datasheets into structured data you can query.
Logistics exceptions explained and routed, with the underlying documents attached to the recommendation.
The story behind the forecast, written from your own history rather than from a template.
Security
Customer-controlled deployment narrows the data path; it does not create compliance by itself. The current MVP proves specific product behaviours and leaves identity, encryption, network policy and operational controls to the pilot design.
Current evidence
Customer-controlled runtime
The application is designed for customer-owned hardware or a customer-owned cloud account; so far it has been demonstrated on a single machine. Each pilot must separately evidence its keys, network and operator access.
No hosted model API
The demonstrated chat, embedding and OCR path runs on the local Docker network. First-time model downloads, telemetry and support access are set out on the architecture page.
Source-bound findings
A positive review cell resolves to indexed source text. The held-out evaluation reports citation validity and names the evidence-overlap and metadata-accuracy gates that remain below target.
Metadata-only record
Destroying a private batch removes its text, chunks, embeddings, cells and decisions. The destruction record keeps file names, hashes, sizes and timestamps.
No certification or production-readiness claim. Vesh AI does not currently claim SOC 2, ISO 27001, HIPAA compliance, an independent penetration test, or enterprise-ready controls.
Illustrative missions
Five places where the same sovereign stack can earn its keep. These are representative applications, not a client list.
Books, packs, filings. The intelligence sits where the numbers already sit, and the close stops running into the night.
The letter goes out sounding like the firm that sent it. Drafted here, on their material, owned by the partner who signs it.
Ten years of decisions, made answerable again — without a line of source leaving the network it lives on.
Contracts, certifications, drawings and correspondence, treated as one body of evidence rather than four filing systems.
A ministry is a data problem too. Same engineering, on infrastructure the authority controls rather than rents.
Start
A briefing is a conversation, not a pitch. Bring the process that costs you your evenings, and we will tell you plainly whether this helps — and if it does not, what would.
Diagnostic brief
Day 14 of 14
Yours to keep — for your board, your IT team or another vendor.