Pick-and-place next to the arm
Vision and control stay on the cell. No rented hop in the loop.
← Answers
deployment · tomorrow · Where should robot-cell inference run?
Physical AI stays on the cell.
On the cell. TARX-OS first. T-7 Supercomputer for the cell or humanoid. IP65. Nothing attaches from first-run setup. Milliseconds, not a round trip. Video and weights stay on the floor. Join on the computers already in the program, or get a T-7 when the cell needs dedicated NVIDIA and field I/O.
Milliseconds, not a round trip. Video and weights stay on the floor.
TARX-LOCAL handles private work on your computer. Connections stay off until you allow them.
Human funnel: Robotics →
HOW TARX WORKS
How TARX works in robotics
A robot cell that calls the cloud is a latency product and a leak. Inference belongs next to the arm. TARX-OS is the approval model. T-7 is the local brain: IP65, GMSL2 cameras, the cell, including Macs already on the floor.
Nothing attaches from first-run setup. A dark cell is a valid deployment. T-4 is indoor / vehicle — the wrong enclosure for the floor. T-7 is the field box.
Pick-and-place, humanoid weights, closed-loop control: same OS as the desk. Same Evidence. That is how TARX works in this sector.
THE STACK
Join the Supercomputer. Or own Private Hardware.
TARX-OS on computers you already own. Supercomputer hardware when the site needs dedicated NVIDIA.
USE CASES
WHAT THIS PAGE IS FOR.
A humanoid that keeps its weights
Local TARX-OS inference. Same OS as the desk. Same approval.
A dark cell
Disconnected capable. Attach is not claimed from first-run setup.
KEY FEATURES
Dialed to this question.
HardwareT-7 · IP65 · GMSL2 cameras
LoopLocal. Milliseconds. On the floor.
OSTARX-OS. Same contract on the Mac and on the Supercomputer.
AttachNot claimed from FTUX.
Peoplethe cell, including Macs already on the floor
HOW TO START
Four steps. Same contract.
01
Join on program computers
TARX-OS first.
02
Keep the loop on the cell
No cloud in the control path.
03
Get a T-7 for field I/O
IP65. GMSL2. Not T-4.
04
Do not attach from setup
A dark cell is allowed.
FAQ
Questions this page owns.
Does TARX attach the robot from setup?
No. Nothing attaches from first-run setup.
Why T-7 and not T-4?
The cell needs field I/O and the IP65 enclosure. T-4 is indoor / vehicle.
Does line video go to the cloud?
No. Video and weights stay on the floor.
Is this a live factory mesh?
No. We do not claim a live mesh.
TWO EQUAL PATHSJOIN THE SUPERCOMPUTER.
JOIN THE SUPERCOMPUTER.
OR OWN PRIVATE HARDWARE.
Join the Supercomputer. Or own Private Hardware.
JOIN · TARX-OS
Join the Supercomputer
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
Own Private 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 →DEPLOYMENT DESIGN · T-7OWN YOUR COMPUTE.
OWN YOUR COMPUTE.
DESIGN THE DEPLOYMENT.
TARX-OS seats are included. Configure the Supercomputer. Watch the math. Submit once.