On-premise · Firm-owned hardware
An on-premise legal AI platform, not a tenancy.
No shared infrastructure, no vendor tenancy, no data-processing agreement to negotiate. The platform is installed on a machine the firm bought and controls.
What sits inside your building
Everything. The models, the corpus, the index and the work product.
The models run locally
Inference happens on the firm's GPU. There is no request to a hosted endpoint, so there is no third party in the path to be trusted, audited or breached.
The authority corpus is local
Case law, statutes and rules are held on the machine, which is what makes citation verification possible without a research subscription in the loop.
The index is local
Document embeddings and the matter index are written to the firm's own disk. Deleting a matter deletes it — there is no cache elsewhere to chase.
IT keeps control
Your patching schedule, your backup policy, your physical security. HIGHCOURT specifies a machine; the firm owns and administers it.
What stays true on every matter
These do not change by practice area, firm size, or the question asked.
Have your IT lead on the call.
On-premise questions are IT questions. The briefing covers the architecture, the update path and what the machine actually does at rest.
Request a BriefingQuestions firms ask
The answers below are specific to this page’s subject.
Is this a private cloud or single-tenant hosting?
Neither. Both of those still put the data on someone else's hardware under someone else's administration. On-premise here means the physical machine is in the firm's possession.
How do updates reach an offline machine?
By deliberate, verified delivery rather than an automatic download. An air-gapped workstation cannot silently update itself, which is a security property rather than a limitation.
What happens if we stop paying?
Nothing. It is a one-time purchase, not a licence that expires. The software continues to run on the machine you own.
Does it integrate with our document management system?
It reads from the firm's own storage. Where a DMS exposes a local folder or export, that is the integration surface — deliberately simple, because every integration is another path data could take.
Who administers it day to day?
Your IT function, the same way it administers any other workstation. There is no vendor console with access to your matters.
Related
Other pages covering the same ground from a different angle.
See it run on a real matter.
A briefing walks the whole path — intake, workup, the Adjudicator's pass, and the work product that comes out the other side.
Request a Briefing