What's new — on-demand ephemeral inference is live in early access Request access →
Docs

Privileged in five minutes.

One DPA, one firewall rule, one CLI command. Everything below ships as engineered defaults — nothing to negotiate, nothing persists.

Quickstart

Run privileged inference in three steps.

$ privileged run --model client-vault:latest
container: eph-a3f2b1c ip: 5.161.239.237 status: ready
stream: token-0 → token-1 → ... → token-n
stream closed — container decommissioned
persistence: none  |  data written to disk: 0 bytes
  1. 01

    Sign the DPA

    One pre-audited Data Processing Agreement — zero retention, no training, hardware-level isolation. Signed in days, not months.

  2. 02

    Whitelist our static IP

    All egress flows through a fixed, high-availability gateway. Add it to your firewall once, and you're done — forever.

  3. 03

    Run your first model

    One command. The container spins up, streams tokens, and is decommissioned the instant the stream closes.

    privileged run --model client-vault:latest
Concepts

Four primitives, one platform.

Every capability is engineered into the runtime — not retrofitted via policy.

Ephemeral containers

Containers spin up, load your model, and vanish the instant the token stream closes. Nothing touches disk.

Static-IP egress

All traffic exits through a fixed, high-availability gateway your firm's firewall can whitelist once, forever.

LoRA hot-swap

Hot-swap LoRA adapters in milliseconds — one base model, infinite firm-specific customizations.

White-label data

Bundle premium case-law, docket, and regulatory feeds under one brand — with revenue-share for data partners.

Security & compliance

The checklist your counsel will read.

Highlights from the Privileged Data Processing Agreement, with the section references your outside counsel can cite.

Control
Implementation
In the DPA
Zero retention
User Data is processed strictly in temporary, volatile memory (RAM). On Session termination, no copy, snapshot, or reconstruction survives.
§3 – §4
No training
User Data is never used to train, fine-tune, evaluate, or develop any model — public or private, for Privileged or any third party.
§5
Encryption
TLS 1.3 in transit; AES-256 at rest with customer-managed keys. Privileged cannot decrypt stored data without the Firm's key release.
§6
Hardware-level isolation
Each Session runs in an isolated compute environment. Memory assigned to a Session is discarded and rendered unrecoverable at termination.
§3.3 · §7
Support

Questions for your counsel?

The full DPA template is available for review by counsel on both sides. Email us and we'll send it over.

Email the team