We do not claim
Clinical use
Not a medical device. Not diagnosis. Not treatment.
Patient context stays on site. TARX-OS on computers you already secure. T-4 at the department. T-70 in the rack. No clinical claim.
Institutional IT that must keep patient context on site. Not a clinical buyer.

We do not claim
Clinical use
Not a medical device. Not diagnosis. Not treatment.
Context
On the premise
Unless you approve a route. Air-gapped capable.
Department
T-4
Indoor / vehicle work.
Room
T-70
1U in the rack you already lock.
The market
Healthcare AI pages imply clinical use. That is how you get in trouble.
TARX
Patient context stays on site. TARX-OS on computers you already secure. T-4 at the department. T-70 in the rack. Literacy is Memory vs Vault vs writes that wait.
Who this page is for
What this buyer is already hiring for
01
$0 seats. Local inference.
02
No route unless approved. Air-gapped capable.
03
T-4 beside the team. T-70 in 1U.
04
This is private AI capacity. Not a medical device.
Patient context stays on site. TARX-OS on computers you already secure. $0 seats. Local inference. Data stays on the premise unless you approve a route. Air-gapped capable.
T-4 at the department. T-70 in the rack you already lock. Same OS. Same Evidence. No clinical, diagnostic, or treatment claim. This is private AI capacity the institution governs — not a medical device.
Literacy here is the split: Memory is context, Vault is secrets, writes wait. Join the Supercomputer. Or own Private Hardware.
Local inference. Data stays on the premise unless you approve a route.
Macs already on TARX-OS. T-4 when they need dedicated NVIDIA beside the team.
T-70 in 1U. Same OS. Same evidence. Terms in Deployment Design.
| Node | Where | Claim |
|---|---|---|
| TARX-OS | Existing computers | Runtime. $0 seats. Not clinical. |
| T-4 | Department | Indoor / vehicle work. Same OS. |
| T-70 | Locked room | 1U. Same Evidence. |
No clinical, diagnostic, or treatment claim.
TARX-OS on computers already inside the institution. T-4 at the department. T-70 when the room needs rack capacity.
No. No clinical, diagnostic, or treatment claim. It is private AI capacity the institution governs.
It stays on the premise unless you approve a route. Air-gapped capable.
Join the Supercomputer. Or own Private Hardware.
JOIN · TARX-OS

Always-on agents on silicon you own.
TARX is not a chat app. TARX-OS is the always-on governed runtime for AI agents and work. Install it on the Mac you already have. Chat is how you talk to it. The runtime stays on — goals, skills, approval, Evidence.
Join beta →OWN · TARX HARDWARE

When local is not enough, attach a TARX machine.
T-1, T-4, T-7, T-70, T-600. Model numbers. They join the Supercomputer — the mesh — for private cluster, burst, or air-gapped sites. Same OS. Same approval. Same Evidence.
Explore Private Hardware →TARX-OS seats are included. Configure the Supercomputer. Watch the math. Submit once.