The operating system for hospital compute.

About 90% of hospital servers sit idle while the hospital buys the same compute back from the cloud at a multiple of the price. Clique joins the machines you already own into one computer that runs AI in clinical priority, inside hardware enclaves. Patient data never leaves the building.

  • HIPAA
  • GDPR
  • SOC 2 · in audit
  • DICOM
  • NVIDIA MIG
  • TEE

01 · The problem

Every department bought its own compute, and none of it is shared.

Imaging GPUs on four, a research cluster on two, workstations idle overnight on every floor. Each was bought for its own peak, so the daily work runs in the cloud at a markup.

90%
of hospital servers sit idle
$2.4M
avg. cloud spend per AMC, per year
2-3×
cloud premium vs. on-prem

02 · The join

Sixteen machines. One computer.

Clique inventories every CPU, GPU and volume in hours, then joins them into one fabric with one queue. Hardware you already own starts working as one machine.

clique n. a set of nodes in which every one is connected to every other.

16 nodes · 120 connections · one queue. It's the graph in our name.

03 · The night shift

47 slides scored overnight.

A pathologist uploads whole-slide images at five and goes home. Clique finds twelve idle GPUs across four departments and runs sealed inference through the night.

  1. 17:1247 slides uploaded from the grossing lab
  2. 17:4012 idle GPUs discovered · enclaves attested
  3. 18:05Sealed inference begins · priority: batch
  4. 02:30Last slide scored · artifacts versioned
  5. 06:58Results waiting in PACS · zero workflow change

04 · The scheduler

A stroke outranks a research job.

When a suspected stroke hits the ER at 4 a.m., the emergency lane preempts every batch job in the estate, then resumes them exactly where they left off.

WorkloadPriorityState
Stroke Detection v3CriticalQueued
Path. Slide AnalysisHighRunning
NLP Discharge NotesHighRunning · MIG
Research · Cohort 7BatchQueued

05 · The head node

Everything runs through one head node.

It sits in the basement server room: one install that discovers the hardware, schedules the work, and proves what happened.

  • DiscoveryAuto-inventory of every CPU, GPU and volume in hours, not months.
  • Priority schedulerClinical-priority orchestration with an emergency lane.
  • GPU partitioningNVIDIA MIG splits one A100 into many isolated workloads.
  • DICOM bridgeResults land in PACS. Clinicians keep their tools.
  • Remote attestationEnclave integrity proven cryptographically, every 60 seconds.
  • Confidential computeIntel TDX · AMD SEV-SNP · NVIDIA H100 CC.

06 · Security

Built to be audited.

Every workload is sealed in its own vault, hardware encrypted so even Clique can't see inside. Integrity is proven every sixty seconds; every event lands on an audit chain kept for seven years.

  • SealedIntel TDX · AMD SEV-SNP · NVIDIA H100 confidential computing
  • ProvenIETF RATS remote attestation · Keylime · Veraison
  • LayeredSix isolation layers, from GPU partitions to FIPS 140-3 HSMs
  • LoggedMerkle-tree audit chain · 7-year retention · HIPAA BAA from day one

Models travel. Data doesn't. Vendor models deploy into the enclave, never the other way around.

07 · The health system

Three campuses. One queue. No studies in transit.

Most systems are several hospitals with several server rooms and no shared queue — the flagship buys more GPUs while the community sites sit idle. Clique federates them into one pool. A model improved on pathology at the main campus sharpens the read at the community hospital, because the weights travel and the studies never do.

Each campus keeps its own enclave, its own attestation and its own audit chain. Nothing about joining a system weakens what any one building already proved.

Site-to-site links carry model weights and scheduling signals only. A study acquired at one campus is scored at that campus.

With expertise from

  • ETH Zürich
  • Charité — Universitätsmedizin Berlin
  • The University of Sydney
  • Snowflake
  • ICPC Foundation

The product

Two surfaces run on the same engine.

Control Plane

For IT, CIOs, compliance

Every GPU, workload, enclave and audit event, live in one view. Auditors get their export in one click.

Explore the Control Plane

Studio

For clinicians, researchers

Drop a labeled dataset and pick a task. Clique trains in a sealed container and hands IT a versioned artifact to review.

Explore the Studio

The math

The cost model.

Reference model: 500-bed hospital, 800K imaging studies a year.

$1.80Mmodeled net savings per year
81%cost reduction vs. cloud
~3 mopayback period
70%+utilization, up from 10%
  • GPU inference · 800K studies × $1.35$1.08M
  • LLM inference · notes, summaries, scribes$380K
  • Managed services, MLOps, compliance$340K
  • Training & fine-tuning · 8 runs$280K
  • Egress fees · 1.4 PB × $0.09 / GB$126K
  • Clique platform license · 500 beds$250K
  • Incremental GPU, amortized 5 yr$90K
  • Power, cooling, rack space$70K
  • Cloud burst · peak overflow only$0

These are modeled numbers, and yours will differ; a two-week pilot on your own hardware measures your actual idle capacity and costs.

Questions

What hospital IT asks us.

What happens when a clinician needs a machine Clique is using?

Clinical use always wins. The scheduler checkpoints the batch job, moves it to another node, and hands the machine back in seconds. Nobody in a reading room ever waits on a research workload.

Who can see patient data?

Nobody, including us. Workloads run inside hardware-encrypted enclaves such as Intel TDX, AMD SEV-SNP, and NVIDIA H100 confidential computing, so even Clique can't see what's being processed. Data never leaves the hospital network.

What happens if Clique goes down?

The machines are yours and keep doing their normal jobs. Queued batch work pauses and resumes when the head node comes back. Nothing clinical depends on Clique being up.

How much work is this for our IT team?

One agent install per machine, and the inventory finishes in hours. The system stays read-only until your team approves the scheduling policies. Clinicians keep their existing tools; results land in PACS.

What hardware does it need?

The servers and workstations you already own. Sealed workloads need TEE-capable parts: Intel TDX or AMD SEV-SNP on the CPU side, NVIDIA H100 confidential computing on the GPU.

How does a pilot work?

Two weeks, on your own hardware. It starts with a read-only inventory, so nothing runs until you approve it. At the end you have your measured idle-capacity and cost numbers, and you decide.

The pilot

Request a pilot.

Tell us about your environment and we'll scope a two-week pilot on the hardware you already own. We reply within 24 hours.