← 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 works privately on your computer. Connections stay off until you allow them.

Human funnel: Robotics

TARX_OS on Apple silicon you already own.
Product proof. Not atmosphere. TARX_OS on silicon you own.
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.

TARX_OS · Conversation into the runtime · free software
USE CASES

WHAT THIS PAGE IS FOR.

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.

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 PATHS

JOIN THE SUPERCOMPUTER.
OR OWN PRIVATE HARDWARE.

Join the Supercomputer. Or own Private Hardware.

JOIN · TARX_OS

Illustrative still. Apple silicon in a TARX editorial setting.

Join the Supercomputer

Give TARX superpowers.

TARX works privately on your computer. Connect to the Supercomputer when you want TARX to research the web, use more skills, and take on bigger jobs with deeper models. Supercomputer connection is in beta, and capacity is being qualified.

Join beta

OWN · TARX HARDWARE

TARX hardware. Get your own Supercomputer.

Own Private Hardware.

Want more power of your own?

Add TARX hardware for faster local work, dedicated capacity, or a private cluster.

Explore Private Hardware
DEPLOYMENT DESIGN · T-7

OWN YOUR COMPUTE.
DESIGN THE DEPLOYMENT.

TARX software is free. Size the Black Box for the people using it. Watch the math. Submit once.

1 · The cluster

2 · If they stayed on Claude

Typical Claude mix

4 × $20 + 1 × $200 = $280/mo

80% $20 Pro · 20% $200 Max · whole seats. No rate picker.

3 · Contact and the work