Healthcare · clinical · payer

PHI never leaves the device
or the VPC.

kolm compiles your clinical task into a signed local artifact: model, adapter, recipes, recall index, tests. Runs on a tablet, a laptop, or behind your firewall. kolm serve --mcp exposes it to the agents your clinicians already use. The frontier you bring is the teacher; the artifact is the binary; the data never leaves.

01Why this matters

Cloud AI on PHI is a
permanent egress surface.

Every API call is a BAA-scoped event. Every prompt is potentially discoverable. Every outage is a clinical incident. The risk isn't theoretical, it's an audit row, every minute, on every tenant.

BAA exposure
Every API call

is a HIPAA-scoped event tracked in audit. kolm runs the inference on the device.

Round trip
200-800ms

cloud latency on every chart line. kolm answers locally in 80 ms.

Vendor cycle
14-day notice

for frontier deprecations. kolm pins the model into the artifact for the life of the deployment.

02How it works

You compile in your VPC.
You ship to the device.

The compile bridge runs inside your boundary. Nothing leaves except the artifact. The artifact is a single signed file. The signature is verifiable offline against the manifest hash chain.

·

BAA path on Enterprise.

Signed Business Associate Agreement, default-redacted logs, optional zero-retention compile. The compile pipeline never persists patient data.

·

On-prem compile bridge.

Air-gap-friendly orchestrator that runs inside your network. The frontier teacher you bring is reachable through your existing egress proxy, nothing else.

·

HMAC-chained receipts.

Every output is reproducible. Every layer is content-addressed. Tampering with any layer breaks the chain. Useful at audit, defensible at deposition.

03Use case

Reference deployment:
clinical-note assistant.

A 38 MB artifact running on a clinician's tablet. Indexes the patient's history locally; drafts the encounter note in the institution's voice; defers anything the verifier rejects to a human. Receipts mirror to the institution's audit log. No cloud calls during the visit.

compile-bridge · running on prem · region us-east-vpc

From institutional examples to a signed binary on the tablet.

Compile happens once per quarter against the institution's de-identified gold set. The artifact is signed, K-scored, and pushed to the MDM for distribution. Deployment is a single signed file, not a service.

01 · gather

Examples + evals

De-identified note pairs from the institution's gold set. Held-out evaluation drawn separately and never seen at training.

02 · compile

kolm compile

Verifier synthesized from examples, k-sample teacher, LoRA distill, recipe extract, recall index, sign. K-score gate enforces ship floor.

03 · review

Clinical sign-off

Hold-out evaluation report goes to the clinical informatics committee. K-score breakdown is part of the artifact, defensible at audit.

04 · ship

Push to device

Single signed file deploys via MDM. Runtime is offline. Receipts mirror to your audit log via HL7 or webhook on demand.

04Compliance posture

What's done.
What's in flight.

Honest table. Same one we publish on /security for everyone else.

HIPAA
BAA available · Enterprise

BAA path on Enterprise tier. On-prem compile bridge keeps PHI inside your VPC.

SOC 2
Type II in flight 2026 Q4

Type I evidence available now. Quarterly evidence packets shipped to Pro and Enterprise.

EU AI Act
Conformity assessment 2027 Q2

Designed against high-risk Annex III obligations from day one. Per-artifact technical documentation by construction.

GDPR · UK GDPR
DPA available

EU-resident compile region available on Pro and Enterprise. DPIA template provided. Right to erasure honored within 30 days.

Ship clinical AI
that never leaves the device.

Mail us with a one-line description of the task and the data sensitivity tier. We'll come back with a 30-minute call, a reference artifact, and a path to a signed pilot.