Loop
Local
A cell that calls the cloud is a latency product.
← Solutions
Robotics
A local brain for the cell.
The decision loop stays on the floor. TARX-OS first. T-7 Supercomputer for the cell or humanoid. Nothing attaches from first-run setup.
Cell and humanoid programs that need a local brain, not a hop to a region.
Hardware
T-7
IP65. GMSL2. field and robotics work.
Attach
Not from FTUX
A dark cell is a valid deployment.
Wrong box
T-4
T-4 is indoor / vehicle. The floor wants T-7.
THE CATEGORY
What they sell. What we ship.
The market
Physical AI is sold as a model in the cloud plus a camera on the arm.
TARX
Inference belongs next to the arm. TARX-OS is the approval model. T-7 is the local brain. Same Evidence as the desk.
Who this page is for
Robotics leadControlsPerceptionCell owner
What this buyer is already hiring for
- On-device robot brain / edge inference
- Humanoid weights that stay on site
- Pick-and-place without a rented hop
HOW TARX WORKS
How TARX works in robotics
01
Runtime beside the cell
TARX-OS is the approval model on computers you already have.
02
T-7 as the brain
IP65, GMSL2, local TARX-OS inference.
03
Keep it dark if you need to
Nothing attaches from first-run setup.
04
Same contract as the desk
Pick-and-place, humanoid weights, closed-loop: Evidence after.
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, 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.
Pick-and-place, humanoid weights, closed-loop control: same OS as the desk. Same Evidence. Join the Supercomputer. Or own Private Hardware.
THE WORK
WHAT ROBOTICS ACTUALLY RUNS.
Pick-and-place next to the arm
Vision and control stay on the cell. No rented hop in the loop.
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.
ECONOMICS
The brain stays on the floor.
| Path | Loop | Enclosure |
|---|---|---|
| Cloud brain | Round trip | Whatever is in the rack far away. |
| T-4 | Local | Indoor / vehicle. Wrong for the cell. |
| T-7 | Local, milliseconds | IP65 field. field and robotics work. |
Attach is not claimed from software FTUX.
THE STACK
Join the Supercomputer. Or own Private Hardware.
Same approval model next to the cell. T-7 as the local brain. field and robotics work. Not claimed from software FTUX.
SPEC · FAQ
Dialed to robotics.
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
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.
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.