Sovereign AI consultancy
We build AI systems that run on hardware you already own, or in a cloud tenant registered in your name. Local models, tuned on your own material, for firms in technology, finance, law and supply chain. The file never leaves the building.
14-day diagnostic · written brief · risks · deployment price
Runs on
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.
Production-grade AI without the production-grade exposure.
Why Vesh
The data never leaves
Packs, matters, mail and working papers stay in the room they are already in. There is no copy of your corpus anywhere we can reach, because there is nowhere for it to go. The model is brought to the material, and the material holds still.
Your hardware, or your tenant
On machines the practice already owns, on-premise in the office, air-gapped in a secure room, or in a cloud tenant registered in the client's own name. We design and operate it. You hold it, and you can end the arrangement without moving a single file.
Tuned on your own material
$ vesh run finetune --corpus /vault/matters --base qwen2.5-14b --egress deny
Small models fitted to the document types you actually handle, trained in place and never uploaded. The answer arrives in your firm's register and points at the page it came from, so a reviewer can check it in seconds rather than reading it twice.
Auditable and measurable
Question
What indemnity cap applies to the Meridian supply agreement?
Answer
Liability is capped at 125% of fees paid in the preceding twelve months, excluding wilful default.
Request logs, retrieval traces and per-answer citations, all held inside your boundary. You can prove what the system saw, what it said, and who signed it off — which is the difference between a tool a regulated firm can adopt and one it cannot.
Practice areas
The same runtime underneath, fitted to the document types each practice actually handles. We work primarily in technology, and in the regulated functions where the file cannot travel.
Engineering organisations
Ten years of decisions locked in a repository nobody is allowed to paste anywhere.
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.
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.
Law firms and in-house counsel
Privilege is a wall, not a setting. Review runs inside the boundary or not at all.
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 was 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.
Operations and procurement
Contracts, certifications, drawings and correspondence, read as one corpus.
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
Regulated work has a vocabulary, and a deployment that cannot answer to it is not a deployment. Because the system runs inside your perimeter, it inherits the controls you already hold rather than adding a processor for your auditor to assess.
Met by construction
Protected health information
PHI never transits a third party. There is no business associate agreement to negotiate, because there is no vendor in the data path to sign one.
Personal data and residency
Processing stays in the territory you name. No international transfer, no adequacy question, and no sub-processor list to keep current.
Security, availability, confidentiality
Request logs, retrieval traces and access records are produced inside your boundary, in the form your Type II evidence already takes.
Information security management
The runtime slots into the management system you already operate: your asset register, your access reviews, your change control.
Vesh AI does not host your data. The system is installed inside your compliance boundary and operated under your policies, which is why these regimes are met by controls you already hold rather than by a certificate of ours. Where you need evidence of our own practices during an engagement, we put it in writing.
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.