Skip to content

Architecture comparison

Private-perimeter intelligence compared with shared-cloud legal AI

A deployment and control comparison for law firms evaluating where sensitive matter data is processed, governed and retained.

Shared cloud legal AI

Conventional shared-cloud platform

  1. 01

    Your documents are processed on the vendor's infrastructure.

  2. 02

    Your firm uses a multi-tenant, vendor-operated cloud service shared with other customers.

  3. 03

    Your security boundary extends to infrastructure operated outside the firm.

  4. 04

    A compromise of the vendor environment can put customer work product in scope.

General assistants

Frontier chat tools

  1. 01

    Not built around privilege, matter scope or the matter as the operating unit.

  2. 02

    Legal source verification and matter provenance are not the default interaction model.

  3. 03

    Data handling depends on the assistant, plan, settings and vendor policy.

  4. 04

    The environment is designed for general assistance rather than governed institutional legal work.

Sanctum Lex

Single-tenant enclave

  1. 01

    Inference runs inside your perimeter, on your hardware.

  2. 02

    One firm per node. Nobody shares your enclave.

  3. 03

    Zero external model egress by architecture.

  4. 04

    If we are breached, your private-perimeter matter documents were never in our vendor environment.

  5. 05

    Matter intelligence, legal research, drafting, review, knowledge and governed workflows remain attached to the same matter context.

  6. 06

    Source-grounded responses return the passage, page and matter reference for lawyer review.

  7. 07

    SSO, SCIM, ethical walls, matter permissions, audit, retention and model policy operate as firm-level controls.

  8. 08

    Institutional knowledge and approved methods remain governed alongside the matter.

  9. 09

    Opposing Counsel and Judicial Review can independently pressure-test the same position without rebuilding context.

  10. 10

    Hearing Room and Witness Room carry the same matter into preparation and rehearsal.

  11. 11

    The firm controls the deployment boundary instead of extending privilege into a vendor-operated AI environment.

Architecture review

Questions the firm should be able to answer.

Where is sensitive matter data processed?

Confirm the physical and logical boundary in which documents, prompts, outputs and model inference are handled.

Who controls the deployment boundary?

Establish whether the firm can govern network egress, identity, matter permissions, retention and approved model routes as institutional controls.

Can every material proposition be reviewed against the record?

Require source passages, page references and matter provenance to remain available to the lawyer throughout analysis, drafting and review.

Keep the matter where your firm controls it.

Bring representative documents and one workflow your lawyers care about. We will show the legal work and the private-perimeter deployment boundary in the same session.