Fractals Fleet

Fleet is the operations layer of the Fractals stack. Running one DePIN device is a hobby; running fifty is a business — with hardware to track, costs to reconcile, and hosts to pay. Fleet puts all of that in one dashboard so an operator can see the whole estate at a glance instead of stitching together spreadsheets.

Every device you run — its hardware, uptime, rewards, and the payouts owed to whoever hosts it — lives in a single place, updated from real network data.

Hardware management. A live roster of every device — model, location, status, and uptime — so you always know what's deployed, what's down, and what needs attention.

Accounting. Costs and revenue tracked per device: what the hardware cost, what it earns, and the margin after operations. The unit economics of the fleet, not a guess.

Payouts. Distribute rewards to the hosts and partners running your hardware — the share-of-rewards splits that make host deployments work, handled in one flow.

Operators scaling past a handful of devices — anyone whose deployment grew from a side project into a fleet, where tracking hardware and paying hosts by hand stops working.

Teams running host programs — where someone else supplies the rooftop and you split the rewards. Fleet keeps the hardware, the numbers, and the payouts straight across every host.

Fleet is where a deployment lives once it's running. When you claim a bounty on the /campaigns map and deploy hardware into an open GEODNET superhex, Fleet is the tool that tracks it from day one — uptime, rewards, and the payouts owed.

It sits alongside Nexus (the data layer that decides where to deploy) and Sync (distributions at scale). Nexus finds the opportunity, Fleet runs the hardware, Sync pays everyone out.