Skip to content
Arieta Labs
Private Demo

Lex Analytica

On-prem contract intelligence, measured in megabytes

A complete contract-analysis stack — clause extraction, obligation mapping, risk scoring — that deploys entirely inside your perimeter. Proprietary sub-mini BitNet models with ternary weights run the full pipeline on commodity CPUs: no GPU cluster, no API calls, no document ever leaving the building.

The product

It reads like counsel — and never leaves.

Clause-level analysis tied to your playbook, on models that live inside your perimeter. Captured from a private deployment:

lex.internal/matters/aurora-supply-msa
On-prem
Project Aurora — Supplier MSA
Run playbook ▸Export

Execution copy · privileged & confidential

MASTER SERVICES AGREEMENT

between Aurora Systems GmbH (“Customer”) and Meridian Software Ltd. (“Supplier”)

1. Definitions. “Agreement” means this Master Services Agreement together with its Schedules; “Services” means the software development, hosting, and support services described in Schedule 1; “Fees” means the charges set out in Schedule 2, as adjusted under clause 5.3.

7. Confidentiality. Each party shall keep confidential all Confidential Information of the other party and shall not disclose it except to those of its officers, employees, and professional advisers who need to know it for the purposes of this Agreement and who are bound by obligations of confidence no less protective than this clause 7.

8. Term and Termination. 8.1 This Agreement commences on the Effective Date and continues for an initial term of three (3) years. 8.2 Notwithstanding the foregoing, Customer may terminate this Agreement at any time and for any reason upon thirty (30) days’ written notice to Supplier, in which case Supplier shall refund any Fees paid in advance for Services not yet performed.

9. Limitation of Liability. 9.1 Subject to clause 9.3, each party’s total aggregate liability arising out of or in connection with this Agreement shall not exceed the Fees paid or payable by Customer in the twelve (12) months immediately preceding the event giving rise to the claim. 9.2 Neither party shall be liable for loss of profits, loss of business, or any indirect or consequential loss.

11. Data Protection. The parties shall comply with the Data Processing Addendum at Schedule 4. Supplier shall process Customer Personal Data only on documented instructions and shall not transfer such data outside the Customer environment without prior written consent.

12. General Provisions. 12.1 Entire agreement. 12.2 Assignment restricted. 12.3 Notices in writing. 12.4 This Agreement shall automatically renew for successive one (1) year terms unless either party gives written notice of non-renewal at least sixty (60) days before the end of the then-current term. 12.5 This Agreement is governed by the laws of England and Wales, and the parties submit to the exclusive jurisdiction of the courts of England.

— page 4 of 14 —

Analysis complete — 3 findings · 1 high0 B egress

A frontier result from 1.58 bits

Lex Analytica does not call a cloud model. It ships its own — a proprietary ensemble of sub-mini, task-specialised BitNet models whose every weight is −1, 0, or +1. Small enough to live on one machine, sharp enough to read like a lawyer.

1.58bit

per weight — ternary {−1, 0, +1}

700MB

full model ensemble, on disk

0bytes

leave your network — ever

100% CPU

commodity hardware, no GPUs

■ −1□ 0■ +1— every weight, 1.58 bits

Frontier cloud model~10² GB · GPU cluster
Lex Analytica ensemble< 700 MB · one CPU

Ternary weights make matrix multiplication collapse into additions. That is what lets a task-specialised ensemble undercut a frontier model's footprint by two orders of magnitude — and run inside your firewall on hardware you already own.

Sovereign by design

Contracts are the documents least suited to leaving the building — so the model comes to them. Lex Analytica deploys inside your perimeter and stays there: inference, rule engine, and reporting all run on your hardware, and the egress meter reads zero.

  • Your VPC, bare metal, or fully air-gapped enclave
  • CPU-native inference — no GPU procurement, no queue
  • Custom rule engine trained on your playbooks, kept on your side
  • Audit-friendly: every finding traceable to a clause and a rule

Deployment · everything inside the dashed line

Key Features

01Proprietary sub-mini BitNet models — ternary weights, task-specialised
02Fully local deployment: your VPC, bare metal, or air-gapped
03CPU-native inference — no GPUs, no external calls
04Automated clause extraction, classification, and risk scoring
05Custom rule engine tuned to firm-specific playbooks
06Bulk processing via API or dashboard; exports in PDF, DOCX, and JSON

Built For

01

Corporate legal teams managing high volumes of contracts

02

Law firms conducting due diligence

03

Regulated enterprises whose documents cannot leave the perimeter

How It Works

Deploy

Ships as a container image or appliance into your VPC, bare metal, or a fully air-gapped enclave. No outbound dependencies, no licence phone-home.

Analyse

The BitNet ensemble runs the whole pipeline locally — segmentation, clause classification, obligation mapping, risk scoring — on CPUs you already own.

Act

Structured findings land in your dashboard and API: flagged clauses, risk registers, and exportable reports in PDF, DOCX, and JSON.

Interested in Lex Analytica?

See it on your own contracts — the demo deploys in your environment, not ours.