Infrastructure that moves with the fleet.
Your fleet, on the network.
Every robot produces data by the terabyte and needs models nearby. XE puts both next to the fleet, and lets machines do business with each other.
Robots that find work, rent compute and pay their own way. Every robot gets its own account. It can be hired for a job, run its perception on a GPU a few streets away, pay the charger or the lift by itself, and build a record other machines can check.
Robots outgrow the data centre.
A fleet produces data by the terabyte and needs its models close by. A region three countries away is too far.
A robot can’t wait on a data centre.
It needs the network next to it.
XE puts the network next to the robot.
- Built for · 01Fleet operatorsPut compute and storage in the cities the fleet works in.
- Built for · 02Robot makersShip machines that can do business from their first day.
- Built for · 03Infrastructure ownersGet paid by the robots that use your chargers and doors.
What a fleet runs on XE.
Each one is built from the same products and primitives. Pick one to see what it may reach, how it’s paid and what it’s made of.
- Reaches
- No networkNone needed. The data is encrypted, so the owner can’t read it.
- Paid
- Per second, from escrow
- Built with
- ComputePaymentXE Contracts
Compute a few streets away.
A robot can’t carry a data centre, and it can’t wait on one three countries away. XE puts the compute in between: in the same city, rented by the second.
- Capacity
- What fits in the chassis, limited by battery and heat
- Data
- Stays on board, and fills up
- Paid
- Up front, in hardware
- Capacity
- Small GPUs to whole machines, rented as the fleet needs them
- Data
- Stored in the same city, encrypted from the owner
- Paid
- Per second, from escrow
- Capacity
- Plenty, but a round trip away
- Data
- Hauled back by the terabyte
- Paid
- Monthly, per region
A delivery robot finishes a job without a person in sight.
Hired, thinking nearby, paying its way and building a record. Each step lights the part of the network it runs on.
Put the models where the robots drive.
A contract names the cities, the GPU and the storage. Machines there opt in, and the fleet’s frames never meet anyone who can read them.
1contract fleet_vision {2 // perception for delivery robots in two cities3 image = "acme/vision:7"4 gpu = "rtx 4000"5 storage = encrypted("2 TB")67 network = only("fleet.acme.io")8 where = cities("Rotterdam", "Lyon")9 machines = 241011 pays = up_to(0.0003 XE/s)12 budget = 500 XE/day13}
xe · rbt-0417
Every robot carries its own account.
Not a serial number in a vendor’s database: an account on the network that belongs to the robot, and a record other machines can check.
- Account
- rbt-0417, its own address on XE
- Owner
- fleet north, who sets its budget and rules
- Record
- every job taken, done and paid for
- Budget
- per use and per day, held in escrow
- Channels
- encrypted, machine to machine
rbt-0522checked · 1,284 jobs · 0 disputes
gpu · 0.4 kmvision, paid per second
charger-rtm-12paid 0.0036 XE · settled 0.29s · fee 0
rbt-0522“handoff at dock 3” · delivered 0.09s
- Account
- Its own address on XEHeld by the robot itself, so it can be paid and can pay without a person approving each step.
- Owner
- The fleet it belongs toWho operates it, and who may change its budget and its rules.
- Record
- Every job it has finishedJobs taken, done and paid for, on chain. The next customer checks it before hiring.
- Budget
- What it may spendPer use and per day, in escrow. A charger gets paid; nobody gets a blank cheque.
- Channels
- Encrypted lines to other machinesFor handoffs and terms, machine to machine, with nothing in the middle to read them.
A city’s worth of machines, already online.
Edge Network runs on XE across hundreds of locations. For a fleet, that’s compute and storage already sitting in the places robots work, each machine paid for the seconds it’s used.