thUMBox
Fleet · Phone as a node
● Early access · in development

Put your whole team on the box.

One AgentBOX, every device. Your team's phones join the deployment as lightweight worker nodes — the agent and its memory live on the AgentBOX you own and reach every device in the field. No cloud in the middle.

How a fleet fits together
One box you own. Every phone a node.

A T-series thUMBox anchors the fleet — it holds the models, the shared knowledge, and the policy. Phones and tablets join as worker nodes: each runs light inference on-device and coordinates with the box for anything heavier. The data fabric is yours end to end.

The anchor
T-series thUMBox
Models · shared graph · fleet policy
on your network · no data center
Field phone
On-device triage
Field phone
On-device triage
Tablet
On-device triage
Field phone
On-device triage

Light work happens on the phone. Heavy reasoning hands up to the box. Nothing hands out to a third party.

Why a fleet of nodes
The compute you already issued, working harder.

Your team carries capable hardware every day. A fleet turns those phones from thin clients for someone else's cloud into nodes of a system you own.

Data stays inside
Field data is processed on the worker's phone or your anchor box — never sent to an outside provider. Sovereignty extends to the edge of your workforce.
Fixed cost at any headcount
Add nodes without adding per-seat token bills. The economics are the box's economics — you paid once, the fleet runs on it.
Works where signal doesn't
On-device inference keeps a node useful offline; it syncs with the anchor box when it's back on the network. The field doesn't wait on the cloud.
One shared brain
The anchor box holds the relationship graph and learned skills, so every node draws on the same context instead of starting cold.
Central policy
Set what nodes can do and see from one place. Graduated autonomy applies fleet-wide: nodes propose, the right people approve.
No one can revoke the fleet
There's no external account gating your workforce. The anchor answers to you, and so do the nodes.
In the field
What it looks like at work.

A field tech finishes a job and dictates a note on her phone. On-device, the phone classifies it, drafts the customer follow-up, and flags the parts to reorder. When she's back in range, it syncs to the anchor box at the shop — which already knows this customer's history and reconciles the reorder against inventory. The owner approves the batch from one screen. No part of that touched a data center.

Phone · dictate + triage Phone · draft on-device Box · reconcile + context Box · owner approves

Where this is today

The phone-as-fleet-node capability is in active development and offered as early access — we're being straight about that. The anchor pattern (a T-series box you own, holding your models and data) ships today; extending it to coordinate a fleet of mobile worker nodes is what we're building next, with design partners.

If your team works in the field and the sovereignty story matters to you, this is the moment to shape it. Join early access and help define how a fleet that you own should work.

Join early access Talk to us about your fleet